If Content Hub and Lift modules are currently installed on your application, follow these instructions to migrate to the newer module.
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 of the Acquia Personalization module, ensure that you:
Select the following checkboxes to enable the modules:
After installing the Acquia Personalization module, use the following steps to connect to your Acquia Subscription:
[site_URL]/admin/config/services/acquia-connector.Click Authenticate with Acquia Cloud.
On the resulting page, enter your API key, secret key, and Account ID credentials.
To find and enter the credentials:
Click Sites > Add New Site.
The page displays the required credentials on the right:
[site_URL]/admin/config/services/acquia-perz/settings.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, letters, and underscores.
Create a new customer site in your Acquia Personalization account.
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.
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 drush acquia:perz-process-queue.
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:
If this content did not answer your questions, try searching or contacting our support team for further assistance.
If Content Hub and Lift modules are currently installed on your application, follow these instructions to migrate to the newer module.
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 of the Acquia Personalization module, ensure that you:
Select the following checkboxes to enable the modules:
After installing the Acquia Personalization module, use the following steps to connect to your Acquia Subscription:
[site_URL]/admin/config/services/acquia-connector.Click Authenticate with Acquia Cloud.
On the resulting page, enter your API key, secret key, and Account ID credentials.
To find and enter the credentials:
Click Sites > Add New Site.
The page displays the required credentials on the right:
[site_URL]/admin/config/services/acquia-perz/settings.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, letters, and underscores.
Create a new customer site in your Acquia Personalization account.
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.
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 drush acquia:perz-process-queue.
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:
If this content did not answer your questions, try searching or contacting our support team for further assistance.