Information for: DEVELOPERS   PARTNERS   SUPPORT

Acquia Personalization module (Limited Availability)

Note

Acquia Support does not support this new version of the Personalization module while in limited availability. Contact your account manager for troubleshooting and to determine if you are eligible to use the module during limited availability.

The Acquia Personalization service decouples the existing Acquia Personalization from Content Hub, and enables customers’ Drupal sites to directly communicate with the Personalization API. To use this service, you must install and configure the Acquia Personalization module and its dependencies.

Installing and configuring the module

  1. Install the Acquia Personalization module and its dependencies from Drupal.org.

  2. Sign in to your website as an administrator.

  3. In the administrative menu, click Extend.

  4. Select the Acquia Connector, Acquia Personalization (Perz), and Acquia Personalization (Perz) Push checkboxes to enable the modules.

    enable-modules

    The system prompts you for two more module dependencies.

  5. Click Continue.

  6. In the Acquia Connector module settings, do the following:

    1. In Enter the email address you use to login to the Acquia Subscription, enter the email address of your Service Cloud or Cloud Platform.
    2. In Enter your Acquia Subscription password, enter the password of your Service Cloud or Cloud Platform.

    acquia-connector

  7. Click Next.

  8. Select your relevant Cloud subscription and click Next.

    product-specific-settings

  9. On the resulting page, enter your API key, secret key, and Account ID credentials.

  10. Open a new window and sign in to Personalization as an administrator.

  11. Navigate to Sites > Add New Site.

    The required credentials are displayed on the right of the screen as shown in the following image:

    site-details

  12. Navigate back to your Drupal site to copy and paste the displayed API key, secret key, and Account ID credentials from Personalization.

  13. Click Save configuration on your Drupal site.

  14. In your Drupal site, navigate to the Acquia Personalization Settings page.

  15. In Acquia Personalization Site ID, enter a site ID for your site.

    The site ID serves as a reference found throughout Personalization.

    Important

    If this is a development site, Acquia recommends appending _dev or any relevant environment name to the site ID. Acquia does not recommend appending _prod to your production sites. For example, when a production site is named phoenix_project, Acquia recommends the name of the development site as phoenix_project_dev.

    The site ID can only contain numbers, lowercase letters, and underscores.

    personalization-settings

  16. In the Personalization interface, click Sites > Add New Site and do the following:

    1. In Name, enter the name of the site.

    2. In Site ID, enter the exact same Site ID that you created in the previous step.

      Important

      If you do not use the exact Site ID from the previous step, Personalization cannot correctly collect data and apply campaigns to the site.

    3. In URL, enter the website URL.

    4. Click Create.

      create-new-site

  17. For each Drupal content type or block type that you want to expose to Personalization, check the settings to make it available for use in the application, and click Save.

    manage-display

    From that point onwards, any creation or update of those types of content is sent to Personalization, and made available for use in campaigns.

  18. To apply this retroactively to all your older content:

    1. Navigate to the Acquia Personalization Settings page of your site.
    2. On the Export tab, click Enqueue content and Process queue.

After these steps, you can start building your campaigns in Acquia Personalization. Content types selection is automatically pushed into Personalization and made available in Experience Builder as you build the personalized experiences for your site.

Known issues and limitations

  • Origin & Tag filters are unavailable in Experience Builder.
  • For content recommendation campaigns, the Most viewed content algorithm is currently unavailable.