Limiting data collection and excluding Drupal entities

Supported display modes

Acquia Personalization supports all Drupal content entities that have at least one display mode or view mode.

Excluding pages from collecting data

Not all pages should collect data on your website or show personalized content. For example, personalizations have no rationale appearing on an admin page.

To prevent Personalization from collecting data on specific pages:

  1. Sign in to your website as an administrator.
  2. Click Configuration from the admin menu and select Acquia Personalization settings (admin/config/services/acquia-perz/settings).
  3. In the Data collections settings section, select the Visibility tab.
  4. In the Path Patterns field, add the URL of each page on which you want to prevent data collection.

    You can use a wildcard to exclude all URLs of a specific pattern.

  5. Click Save configuration.

Managing render roles

Render role is a feature for managing content access control and rendering when exporting entities to Personalization. With this feature, you can ensure that only the appropriate content is exported and the access to that content is properly controlled.

To use the Render role feature:

  1. Navigate to the Manage Display tab of the bundle.

  2. Select the Available to Personalization Service checkbox.
  3. In the Render role dropdown, select the role that Personalization must use while showing the personalized content of this bundle.
  4. Click Save.

Acquia designates the Anonymous role as the default Render role for entities being exported to Personalization. This means only content that is viewable by the Anonymous role in Drupal will be exported.


In some situations, a role might not be able to render an entity properly. As a result, the search interface of Personalization appends (no content) after the content label. In such a situation, you might need to switch to another render role. For example, blocks do not operate like regular entities and require Administrator as render role.

When accessing the Render role feature, you see a list of user roles that are defined by your Drupal website. Each role has a set of permissions. These permissions determine the proper access to content and whether the Drupal configuration can allow updates.

Specifying entities for export

When you set a content type or bundle to export to Personalization, the system exports all its entities. Export of all entities may not be ideal if only a few entities are relevant to Personalization. Therefore, you can configure your site so that the entity form displays a checkbox to select specific entities to export.
To configure this feature for your site:

  1. Navigate to Structure > Content types.
  2. Choose the required content type and click Manage fields.
  3. Click Create a new field.
    The system displays the Add field page.
  4. In the Add a new field drop-down, select Boolean to create a boolean field.
  5. In the Label field, enter a label name.
    For example, Export this node to Acquia Personalization.
  6. Click Save and continue.
  7. On the Export to Personalisation page, click Save field settings.
    The system displays the Manage fields page.
  8. Locate the boolean field label that you created, click Edit.
  9. In the "On" label field, set the value to True.
  10. In the "Off" label field, set the value to False.
  11. Select the Set default value checkbox.
  12. In the Default value section, select the boolean field checkbox to export the default value.
  13. Click Save settings.
  14. Click the Manage display tab. 
  15. Click the Acquia Personalization section.
  16. Select the Make article available to the Acquia Personalization Service checkbox.
  17. In the Only export specific entities drop-down, select the boolean field.
  18. Click Save.

    When you create or edit content, you can choose whether to export it to Personalization.


You must resave all the relevant entities to set the right value for this field, and re-export your content at /admin/config/services/acquia-perz/export.