Personalization

Example settings.php files for Personalization

End-of-sale notice!

Acquia announces the end-of-sale for Acquia Personalization effective July 1, 2024. Customers with active service contracts will continue to receive support. If you are interested in experimentation and optimization, contact Acquia Sales Team to get information about Acquia Convert powered by VWO.

End-of-life notice!

Acquia announces the end-of-life for the acquia_lift module effective December 31, 2025. Acquia recommends you to update your application to the current version of Acquia Personalization. For any assistance related to migration, contact Acquia Support.

When configuring Personalization for multiple environments, your application’s settings.php file can identify what environments are being used, and how they communicate with each other and with other Content Hub websites.

Each of the following configuration files must be modified for your application. These examples for Drupal are the unique values, which shouldn’t be updated in a database migration. In addition, there are other values which can be set and are not listed in either of the code samples.

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.

Acquia Help

Filter by product:

Personalization common questions