Using Experience Builder with a non-Drupal website¶
The Experience Builder can be added to any website, regardless of what
content management service it uses, by configuring several environment
variables, and including a link to the lift.js script or by using metatags.
Requirements¶
As you are preparing to use Experience Builder with your website, be sure to plan for the following requirements:
| Component | Requirement |
|---|---|
| Keys | After you purchase Acquia Lift, Acquia will email you a set of keys which are required to connect to the Experience Builder service. |
| Acquia Lift Profile Manager account | An account will be provided to you as part of your purchase |
Installing Acquia Lift¶
The JavaScript code or Metatag information in the following links should be
called as early in the page’s <head> section as possible, enabling
Acquia Lift to make the appropriate calls during the rendering
process. After this code is in place on your website, you can use the
Acquia Lift bookmark tool to help
you get started with adding more content to
your website.
To use Acquia Lift on your non-Drupal website:
- Download the
lift.jsor thelift-metatagsfile. - In Profile Manager:
- Create a new customer site for each website you plan to install Acquia Lift on.
- Obtain your customer details, which contain the account properties needed to install Acquia Lift.
- 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, andPAGE-SPECIFICvariables in the code for your customer values, based on the Replacing variables table.
- Copy the code for JavaScript or Metatags to the HTML
- Test your configuration:
- Open your website as an anonymous user, or in an incognito window.
- In your original window, view the People tab in Profile Manager. You should see a
Tracking IDassociated with your anonymous visit. - Click the
Tracking ID, and select an item in the Touches list. The Events view below it will populate with your page-specific events.
Replacing variables¶
This table lists the variables that may need to be replaced as part of your installation of Acquia Lift.
| Variable name | Example value | Definition |
|---|---|---|
| account_id | Your Acquia Lift account id (Required) | |
| site_id | Acquia Lift site ID to use for segments and capture data (Required) | |
| liftAssetsURL | https://liftasseturl.acquia.com |
Where to load additional administrative assets |
| liftDecisionAPIURL | https://region.lift.acquia.com |
The base url for 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 are
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) |
| profile | { UDFieldName: UDFFieldValue } |
A collection of capture values to be sent either from the
captureView parameters list or the
data warehouse UDF fields, which override any values
set in the website’s <meta> tags (see capturing
custom values) |
Still need assistance? 