If Content Hub and Lift modules are currently installed on your application, create a Support ticket to manage your migration.
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.
For proper installation and configuration the Acquia Personalization module, ensure that:
Your Drupal website runs on Drupal 9.2 or later.
You have administrative access to your Drupal website.
You have an active Acquia Personalization subscription with Profile Manager credentials provided by your Acquia Account Manager.
Install the Acquia Personalization module and its dependencies from Drupal.org.
Sign in to your website as an administrator.
In the administrative menu, click Extend.
Select the following checkboxes to enable the modules:
Acquia Personalization (Perz)
Acquia Personalization (Perz) Push
If the system prompts you for two more module dependencies, click Continue.
After installing the Acquia Personalization module, we will connect to your Acquia Subscription.
Sign in to your website as an administrator.
Go to the Acquia Connector module settings by using
Click Authenticate with Acquia Cloud.
On the next page, enter your email address and password to login to Acquia Cloud.
On the next page, select the application from the dropdown and click Set Application.
On the resulting page, enter your API key, secret key, and Account ID credentials.
To find and enter the credentials:
Open a new window and sign in to Personalization as an administrator.
Click Sites > Add New Site.
The page displays the required credentials on the right:
Copy the displayed API key, secret key, and Account ID credentials from Personalization, and paste them to your Drupal site.
Select your region from the dropdown.
Click Save configuration.
In your Drupal site, navigate to the Acquia Personalization Settings page
In Acquia Personalization Site ID , enter a site ID for your site and click Save Configuration.
The site ID serves as a reference throughout Personalization.
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.
After creating the new site, ensure to enter the Site ID that you created in the previous step into the corresponding Site ID field.
If you do not use the exact Site ID from the previous step, Personalization cannot correctly collect data and apply campaigns to the site.
If you have both the Lift module and the Personalization module enabled, you see the Switch over anonymous traffic to be personalized by the new Acquia Personalization module toggle bar on Configuration > Web services > Acquia Personalization Settings. To leverage the Personalization module instead of the preceding Lift module, ensure that this toggle bar is on.
If you have migrated from the Acquia Lift module, follow the instructions in Initializing content for campaigns to migrate your content to Personalization.
For each Drupal entity type you want to leverage with Personalization, go to the Manage display setting and select the display mode that you want to use in the application.
Scroll to the Acquia Personalization section and select the Available to Personalization checkbox.
If an export error occurs for entities that are set to be available in Personalization,
the entity causing the error is kept in a queue. After the error is resolved, you can
export it again through the Export feature in Acquia Personalization Settings of the
Drupal module at /admin/config/services/acquia-perz/export, or with the Drush command
From this point onwards, any creation or modification to these entities is sent to Personalization and made available for use in your campaigns.
You can now start building your campaigns in Personalization. Entities are automatically pushed into Personalization and made available in Experience Builder.
If you encounter any issues during the installation or configuration of the Acquia Personalization module, do the following:
Verify module installation: Ensure that you have installed the Acquia Personalization module and its dependencies correctly. To do this, navigate to the Extend page (admin/modules) and ensure that the Acquia Connector, Acquia Personalization (Perz), and Acquia Personalization (Perz) Push checkboxes are selected.
Check Acquia Connector configuration: Ensure that you have correctly authenticated with Acquia Cloud and entered the API key, secret key, Account ID, and region. To check this, navigate to the Acquia Connector module settings page (admin/config/services/acquia-connector) and verify that the correct credentials are entered.
Check Site ID configuration: Verify that you have correctly configured the Site ID in both Drupal and Personalization. Ensure that the Site ID in Drupal matches the Site ID in Personalization.
Check content configuration: Ensure that you have correctly configured the content types, block types, taxonomies, and applicable entities for Personalization. To do this, navigate to the Manage display settings page for each Drupal entity that you want to expose to Personalization, select the Display mode that you want to make available, and ensure that the Available to Personalization checkbox is selected.
Clear cache: If you have made any changes to the configuration, clear the Drupal cache to ensure that the changes took effect. To do this, navigate to the Performance page (admin/config/development/performance) and click Clear all caches.
Check for error messages: If you encounter any error messages during the installation or configuration process, take note of them and try to identify the cause. The error messages may provide valuable information that can help you troubleshoot the issue.
Disable conflicting modules: If you have installed other modules that may conflict with the Acquia Personalization module, try disabling them temporarily and see if the issue persists. You can also try disabling the Acquia Personalization module and its dependencies and then re-enabling them.
Check for updates: Ensure that you are using the latest version of the Acquia Personalization module and its dependencies. Check for any available updates and apply them if necessary.
Seek assistance: If you are still unable to resolve the issue, contact Acquia Support. Provide as much detail as possible regarding the issue and the steps you have taken to troubleshoot it. This will help others to better understand the issue and provide more targeted assistance.