Ensure that you have created a Support ticket to track 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 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 and select the relevant site that you are working with.
The page displays the required credentials on the right:
[site_URL]/admin/config/services/acquia-perz/settings
.Click Save Configuration.
While you are preparing for the migration, ensure that you keep the Content Hub and Acquia Lift modules enabled until Support confirms that the migration is complete. While the older Acquia Lift modules are enabled, the system displays the Switch over anonymous traffic to be personalized by the new Acquia Personalization module checkbox on Configuration > Web services > Acquia Personalization Settings page. Ensure that you leave this checkbox clear until Support instructs you to enable it.
Use the following steps to manually configure the entity types:
Scroll to the Acquia Personalization section and select the Available to Personalization checkbox.
After successfully connecting to the new Personalization service, use the following steps to export your existing content to the new Personalization service:
Click the Export tab.
In the Export Queue section, click Enqueue Content.
The Enqueue Content process scans your Drupal site for entities that can be used in Personalization. After the scan, the content is stored in the Drupal queue.
Alternatively, you can run the drush acquia:perz-enqueue-content
command.
After the Enqueue Content process is complete, click Process Queue.
The system exports all content from the queue to Personalization.
Alternatively, you can run the drush acquia:perz-process-queue
command.
After completing all the tasks mentioned in the preceding sections, you must inform the Support team so that they can review your account and coordinate with you for the next step to complete the migration.
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.
Thu Dec 19 2024 11:22:32 GMT+0000 (Coordinated Universal Time)
Acquia announces the end-of-life for the acquia_lift module effective December 31, 2024. Acquia recommends you to update your application to the current version of Acquia Personalization. For any assistance related to migration, contact Acquia Support.
Acquia Personalization is sunsetting. We remain committed to supporting our customers on Personalization until at least December 31, 2025. If your contract extends beyond this date, there are multiple options that we can discuss with you. If you choose to adopt our new product, Acquia will provide free onboarding services, which you can discuss with your account team. We look forward to sharing more specific product information with you.