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:
Pick the appropriate script for your use case:
JavaScript format:
<!-- ACCOUNT PROPERTIES | MANDATORY | Should be the same across all sites in the same account --> <!-- Update account_id value below to match what's displayed in the sidebar of all your sites in the "Sites" section of Profile Manager --> <meta itemprop="acquia_lift:account_id" content="LIFTUNIVERSITY" /> <meta itemprop="acquia_lift:liftAssetsURL" content="https://builder.lift.acquia.com" /> <meta itemprop="acquia_lift:liftDecisionAPIURL" content="https://us.perz-api.cloudservices.acquia.io" /> <meta itemprop="acquia_lift:contentReplacementMode" content="trusted" /> <meta itemprop="acquia_lift:apiVersion" content="v3"> <!-- SITE ID | MANDATORY | Should be different for each site and environment in the same account --> <!-- Update site_id to match the value found in the sidebar of your site in the "Sites" section of Profile Manager --> <meta itemprop="acquia_lift:site_id" content="liftu_site_id" /> <!-- PAGE-SPECIFIC PROPERTIES | OPTIONAL | Content values can be different from page to page --> <meta itemprop="acquia_lift:content_title" content="Homepage" /> <meta itemprop="acquia_lift:content_type" content="page" /> <meta itemprop="acquia_lift:page_type" content="content page" /> <meta itemprop="acquia_lift:content_section" content="Home" /> <meta itemprop="acquia_lift:content_keywords" content="LiftU" /> <meta itemprop="acquia_lift:post_id" content="123" /> <meta itemprop="acquia_lift:published_date" content="1507914363" /> <meta itemprop="acquia_lift:persona" content="Student" /> <meta itemprop="acquia_lift:engagement_score" content="1" /> <meta itemprop="acquia_lift:author" content="Acquia" /> <!-- CUSTOM COLUMN META DATA | OPTIONAL | Content values can be different from page to page --> <!-- The itemprops need to be created from Lift Profile Manager, Admin > Manage Configuration Data > Custom Column Meta Data. Will always be the format below of {table}_udf{accessor_number} --> <meta itemprop="acquia_lift:person_udf4" content="Custom Value" /> <!-- LIFT JS script | MANDATORY --> <script src="https://builder.lift.acquia.com/lift.js"></script>
HTML format:
<script type="text/javascript"> window.AcquiaLift = { /* ** ACCOUNT PROPERTIES | MANDATORY | Should be the same across all sites in the same account ** Update account_id value below to match what's displayed in the sidebar of all your sites in the "Sites" section of Profile Manager */ account_id: "LIFTUNIVERSITY", liftAssetsURL: "https://builder.lift.acquia.com", liftDecisionAPIURL: "https://us.perz-api.cloudservices.acquia.io", contentReplacementMode: "trusted", apiVersion: "v3", /* ** SITE ID | MANDATORY | Should be different for each site and environment in the same account ** Update site_id to match the value found in the sidebar of your site in the "Sites" section of Profile Manager */ site_id: "liftu_site_id", /** PAGE-SPECIFIC PROPERTIES | OPTIONAL | Content values can be different from page to page **/ profile: { 'author':"Acquia", 'engagement_score':'1', 'page_type':"content page", 'post_id':"123", 'published_date':"1507914363", 'content_title':"Homepage", 'content_type':"page", 'content_section':"Home", 'content_keywords':"LiftU", 'persona':"Student", /* CUSTOM COLUMN META DATA | OPTIONAL | Content values can be different from page to page ** The itemprops need to be created from Lift Profile Manager ** Admin > Manage Configuration Data > Custom Column Meta Data. ** Will always be the format below of {table}_udf{accessor_number} --> **/ 'person_udf4':"Custom Value" } }; </script> <!-- LIFT JS script | MANDATORY --> <script type="text/javascript" src="https://builder.lift.acquia.com/lift.js"></script>
In Personalization:
Create a new customer site for each website you plan to install Personalization on.
Retrieve your customer details, which contain the account properties needed to install Personalization.
On your website:
Copy the code for JavaScript or Metatags to the HTML <head>
of
your website, or to Google Tag Manager.
Update the ACCOUNT
, site_id
, and PAGE-SPECIFIC
variables
in the code for your customer values, based on the Replacing
variables table.
Test your configuration:
Open your website as an anonymous user, or in an incognito window.
In your original window, view the People tab in Personalization. You will see
a Tracking ID
associated with your anonymous visit.
Click the 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, you can get started with building experiences and creating campaigns. Personalization 4 uses the Manual Slot method of embedding slots on your non-Drupal website. For more information, see creating slots.
The following table lists the variables you need to replace 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 |
|
Where to load more administrative assets |
liftDecisionAPIURL |
|
The base URL of the decision API |
profile |
|
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 |
language |
en |
The current language of the content on the page. Uses 2-letter |