Information for: DEVELOPERS   PARTNERS

Using Experience Builder with a non-Drupal website

Installing Experience Builder

You can install Experience Builder 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.

Requirements

As you prepare to use Experience Builder with your website, ensure you plan for the following requirements:

Component Requirement
Keys After purchasing Acquia Lift, Acquia will email you a group of keys required to connect to the Experience Builder service.
Acquia Lift Profile Manager account Acquia will provide you an account as part of your purchase.

Installing Acquia Lift

The JavaScript code or Metatag information in the following links must call the page’s <head> section as soon as possible, enabling Acquia Lift to make the appropriate calls during the rendering process. After the 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:

  1. Download the lift.js or the lift-metatags file.
  2. In Profile Manager:
    1. Create a new customer site for each website you plan to install Acquia Lift on.
    2. Retrieve your customer details, which contain the account properties needed to install Acquia Lift.
  3. On your website:
    1. Copy the code for JavaScript or Metatags to the HTML <head> of your website, or to Google Tag Manager.
    2. Update the ACCOUNT, site_id, and PAGE-SPECIFIC variables in the code for your customer values, based on the Replacing variables table.
  4. Test your configuration:
    1. Open your website as an anonymous user, or in an incognito window.
    2. In your original window, view the People tab in Profile Manager. You will see a Tracking ID associated with your anonymous visit.
    3. Click the Tracking ID, and select from the Touches list. Following the Touches list, the Events view will populate with your page-specific events.

Replacing variables

The following table lists the variables needing replaced as part of your Acquia Lift installation.

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 more 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 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)
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)