Depending on your needs, Personalization allows you to configure how the Drupal modules and the JavaScript tracking code interact with Personalization.

To modify your capture settings:

• Sign in to Personalization, and then click the Configure tab.
• From the left menu, click the Data Collection link.
• Under JavaScript Data Collection, in the Activity Level list, select the amount of information that you want to store in Personalization about your visitors from the following options:
  • NONE: Does not collect or store any visitor information
  • CAPTUREONLY: Collects visitor information, but does not calculate segments or enable containers
  • FULL: Collects visitor information, calculates segments, and enables containers
• To control how long cookies (both first- and third-party cookies) used by the tracking code persist in visitors’ browsers, enter values for the following fields:
  • Tracking Time: Positive integer for the amount of time to keep the tracking cookie (default value: 2)
  • Time Unit list: Select from the following values:
    • years (default)
    • months
    • weeks
    • days
    • minutes
• In the Maximum Size for Queue Cookie (Bytes) field, enter 4096. If, after you have configured this field, your website experiences performance problems, the queue cookie’s maximum size may be too large. The recommended range for optimal website performance is between 4096 and 1024 bytes.
• Sometimes your website’s visitors will use a shared resource to access your website: for example, an office that shares a single internet-connected computer. To allow Personalization to identify specific visitors to your website in these situations, in the Shared Machine Identifier list, click the standard or custom identity type that you want to use for your visitor identifier. When website visitors use a shared computer or resource, Personalization will assign a tracking ID to the visitor that’s based on both the identifier provided by the visitor, and a unique identifier value.

• You can control the domain used for tracking visitors by enabling Use Base Domain to Create Personalization First-Party Cookie. If the checkbox is selected, the tracking cookie will be placed under your website’s base domain.

  For example, if your domain is www.example.com, the cookie will use the example.com domain.

  For a www.example.co.uk domain, the cookie will use the example.co.uk domain.

  Note

  If you don’t select Use Base Domain to Create Personalization First-Party Cookie, Personalization will track visitors on your domain’s websites using the full website domain.

  For example, if your domain is www.example.com, the cookie will use www.example.com domain.

  For a www.example.co.uk domain, the cookie will use www.example.co.uk domain.

• If you want to track visitors across different domains, select the Third-Party Cookie Enabled checkbox. Personalization will attempt to create third-party cookies that are associated with an Acquia server domain.

  Note

  Not all browsers enable third-party cookies, and some visitors may install software to block third-party cookies.

  If you do not select this checkbox, Personalization will track visitors on your domain’s websites by selecting Use Base Domain to Create Personalization First-Party Cookie.

• After you have made all of the required modifications, click Update.

Managing your visitor capture settings

For example, if you disable base domain tracking and have two sub websites such as projects.example.com and products.example.com, the same person visiting both sub websites will be tracked as two different visitors in Personalization. There will be one tracking cookie for projects.example.com and another tracking cookie for products.example.com.

For example, if you disable base domain tracking and have two sub websites such as projects.example.com and products.example.com, the same person visiting both sub websites will be tracked as two different visitors in Personalization. There will be one tracking cookie for projects.example.com and another tracking cookie for products.example.com.