You can install Personalization on any website, regardless of what
content management service your website uses, by configuring several
environment variables, and including a link to the lift.js
script or
by using metatags.
As you prepare to use Personalization with your website, ensure you plan for the following requirements:
Component | Requirement |
---|---|
Keys | After purchasing Personalization, Acquia will email you a group of keys required to connect to the Personalization service. |
Personalization account | Acquia creates an account for you as part of your subscription. |
The JavaScript code or Metatag information in the following links must
call the page’s <head>
section as soon as possible, enabling
Personalization to make the appropriate calls during the rendering
process.
To use Personalization on your non-Drupal website:
Download the appropriate script for your version of Personalization and use case:
<head>
of
your website, or to Google Tag Manager.ACCOUNT
, site_id
, and PAGE-SPECIFIC
variables
in the code for your customer values, based on the Replacing
variables table.Tracking ID
associated with your anonymous visit.Tracking ID
, and select from the Touches list.
Following the Touches list, the Events view will populate with
your page-specific events.After the code is in place on your website:
The following table lists the variables needing replaced as part of your Personalization installation.
Variable name | Example value | Definition |
---|---|---|
account_id | Your Personalization account id (Required) | |
site_id | Personalization site ID to use for segments and capture data (Required) | |
liftAssetsURL | https://liftasseturl.acquia.com |
Where to load more administrative assets |
liftDecisionAPIURL | https://region.lift.acquia.com |
The base URL of the decision API |
authEndpoint | https://region-oauth2.lift.acquia.com/authorize |
The URL to the OAuth server endpoint |
contentReplacementMode | trusted |
The site-wide setting for content replacement—valid values include
untrusted , trusted , or customized (see content
replacement modes) |
contentOrigin | aaaabbbb-0000-1111-2222-333334444466 |
Limit the content available in the content list to a specific origin website (see content origin) (This variable is only available in Personalization 3) |
profile | { UDFieldName: UDFFieldValue } |
A collection of capture values sent either from the
captureView parameters
list or from the data warehouse UDF
fields, which override any values set in the website’s <meta> tags
(see capturing custom values) |
cdfVersion | 1 or 2 |
Alerts Personalization to which version of Content Hub is in use.
Version 1 = 1 Version 2 = 2 |
context_language | en | The current language of the content on the page. Uses 2-letter ISO
639-1 language codes here. |