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.
Prerequisites
For proper installation and configuration of the Acquia Personalization module, ensure that you:
Click Sites and select the relevant site that you are working with.
The page displays the required credentials on the right:
Note the value in the Site ID field.
Copy the values in the Region, API Key, Secret Key, and Account ID fields from Personalization, and paste them to your Drupal site.
Click Save configuration.
Configuring your site ID
In your Drupal site, go to the Acquia Personalization Settings page by using [site_URL]/admin/config/services/acquia-perz/settings.
In Acquia Personalization Site ID, enter the same site ID that you noted from the Site Details page.
Click Save Configuration.
Configuring content for Personalization
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.
To automatically configure the new module to export the same entity types as the old module, click Migrate configuration.
To verify that the configuration is migrated successfully, click Entity configuration at the end of the Acquia Personalization Settings form.
Use the following steps to manually configure the entity types:
Go to the Manage display page of each Drupal entity type that you want to use with Personalization.
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.
Click Save.
Re-exporting content for Personalization
After successfully connecting to the new Personalization service, use the following steps to export your existing content to the new Personalization service:
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.
Contacting Support to complete the migration
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.
Troubleshooting tips
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 correctly installed the Acquia Personalization module and its dependencies. 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 check 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 helps the Support team to better understand the issue and provide more targeted assistance.
Migrating the Acquia Personalization module
Important
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.
Prerequisites
For proper installation and configuration of the Acquia Personalization module, ensure that you:
Click Sites and select the relevant site that you are working with.
The page displays the required credentials on the right:
Note the value in the Site ID field.
Copy the values in the Region, API Key, Secret Key, and Account ID fields from Personalization, and paste them to your Drupal site.
Click Save configuration.
Configuring your site ID
In your Drupal site, go to the Acquia Personalization Settings page by using [site_URL]/admin/config/services/acquia-perz/settings.
In Acquia Personalization Site ID, enter the same site ID that you noted from the Site Details page.
Click Save Configuration.
Configuring content for Personalization
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.
To automatically configure the new module to export the same entity types as the old module, click Migrate configuration.
To verify that the configuration is migrated successfully, click Entity configuration at the end of the Acquia Personalization Settings form.
Use the following steps to manually configure the entity types:
Go to the Manage display page of each Drupal entity type that you want to use with Personalization.
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.
Click Save.
Re-exporting content for Personalization
After successfully connecting to the new Personalization service, use the following steps to export your existing content to the new Personalization service:
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.
Contacting Support to complete the migration
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.
Troubleshooting tips
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 correctly installed the Acquia Personalization module and its dependencies. 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 check 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 helps the Support team to better understand the issue and provide more targeted assistance.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Personalization