Although you can use Personalization to personalize content for different website visitors after you install and enable it, there are additional settings to control the duration of certain types of personalizations. The Personalization Connector module enables you to configure the method that it uses to retrieve identity information and to organize how visitor data is stored.
Creating mappings
To set up identity and field mappings, complete the following steps:
- As an administrator, navigate to Configuration > Personalization.
- Under Data collection settings, configure the six sub-tabs as needed for your website.
- Click Save configuration when you are finished.
Settings
- Identity section The Identity tab configuration determines how Personalization captures the user’s identification.
Identity parameter: Enter the query string parameter for specific visitor information, such as an email address or social media username, which is sent to the Personalization service — for example,
[email protected]. If this parameter is provided in a page URL, then it will be passed to Personalization as the identity of the visitor. This can be useful, for example, for capturing the identity of a visitor when they click on a link from an email.If there is a value in this field, the Identity type parameter field, which represents the method used to identify the visitor in Personalization; for example, entering
identityTyperesults in?identity=jdoe01&identityType=email. If you do not enter a value in this field, the Identity type parameter field is hidden.- Default identity type: The identity type category to use by default—entering a blank value defaults to
email; for example, enteringaccountresults in?identity=jdoe01&identityType=account, while blank is the same as?identity=jdoe01&identityType=emailFor more information about identifier types, including creating custom identifier types, see Updating your customer details.
- Field Mappings sectionThe Personalization Profiles tab allows you to map the content section, content keywords, and persona fields to different visitor contexts. Visitor context is the method that Personalization uses to export and organize data relating to the current webpage the visitor is viewing. It provides data to the Personalization service, and can be tracked.
Note
More information about field mappings can be found in the Data Warehouse documentation.
- Content Section: Click the category or section that the content belongs to, and to which the content section field will be mapped.
- Content Keywords: Click the set of catchwords that the article contains, and to which the content keywords field will be mapped.
- Persona: Click the description of the type of user, based on their viewing a particular webpage, to which the persona field will be mapped.
User Defined Field Mappings section
For each user-defined field available, you can map a visitor context whose value will be sent as the value for that user-defined field. For more information about user-defined fields, see Using column meta data. After your website is connected to the Personalization service, in addition to the preceding fields, Personalization Drupal displays the following fields:
- Person Mappings: The visitor context that applies to the visitor as a whole (across all visits and webpage views)
- Touch Mappings: The visitor context that applies to the visitor’s current visit to the website
- Event Mappings: The visitor context that applies to each individual action the visitor performs on the website