Personalization allows you to integrate Demandbase data for personalization.
Creating a custom event
Sign in to your tag manager. If you are using Google Tag Manager, see the Overview page for more information.
Go to the Trigger Configuration page of your tag manager.
Create Custom Event Trigger type for Demandbase to finish loading. For example, the trigger can fire on a particular Event like Demandbase_Loaded.
You must configure Personalization as the tag to reference the preceding trigger.
Mapping Demandbase attributes to Personalization
For each Demandbase attribute you want to send to Personalization, you must configure a separate variable in the tag manager.
Note
Ensure the data layer variable matches the attribute returned from Demandbase.
Sign in to your tag manager.
From the Variable Configuration page in your tag manager, create a Data Layer Variable type for your Demandbase audience and set as the Default Value.
You must configure Personalization as the tag to reference the preceding variable.
Configuring the Personalization script
You must configure the following Personalization script in your tag manager to trigger from the Demandbase_loaded event created in Creating a custom event:
/*
** THIS VERSION OF LIFT.JS IS FOR ACQUIA LIFT VERSION 3
*/
<script type="text/javascript">
window.AcquiaLift = {
/*
** ACCOUNT PROPERTIES | MANDATORY | Should be the same across all sites in the same account
** Content values need to be the same as what's Lift Profile Manager, Admin > Customer Sites > Customer Details
** The following values are examples. Update all variables for your own installation of Acquia Lift
*/
account_id: "LIFTUNIVERSITY",
liftAssetsURL: "https://lift3assets.lift.acquia.com/stable",
liftDecisionAPIURL: "https://us-east-1-demo-decisionapi.lift.acquia.com",
authEndpoint: "https://us-east-1-demo-oauth2.lift.acquia.com/authorize",
contentReplacementMode: "trusted",
/*
** SITE ID | MANDATORY | Should be different for each site and environment in the same account
** Content value needs to be created and match what's in Lift Profile Manager
** Admin > Manage Configuration Data > Customer Sites
*/
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://lift3assets.lift.acquia.com/stable/lift.js"></script>
By configuring the Personalization script to trigger from the Demandbase event, you ensure you send all Demandbase data to your website before running Personalization.
Mapping Demandbase attributes to UDF fields in Personalization
Within your Personalization script, you can map the Demandbase attributes, created as variables, to UDF fields in Personalization.
UDF fields can be person, touch, or event fields. The person data field uses Demandbase data.
Click the Add new column meta data link, and enter values in the fields. For more information about column meta data field values, see Adding a column name in Using column meta data.
After adding new column meta data, you’ll receive the data to be sent to Personalization from the preceding script you configured in Configuring the Personalization script.
If you want to use this data for segmentation, ensure you check the Segmentable box and enter corresponding values in the form fields as shown in the following screenshot:
Your website can now pull Demandbase data into Personalization.
Demandbase for Personalization
Personalization allows you to integrate Demandbase data for personalization.
Creating a custom event
Sign in to your tag manager. If you are using Google Tag Manager, see the Overview page for more information.
Go to the Trigger Configuration page of your tag manager.
Create Custom Event Trigger type for Demandbase to finish loading. For example, the trigger can fire on a particular Event like Demandbase_Loaded.
You must configure Personalization as the tag to reference the preceding trigger.
Mapping Demandbase attributes to Personalization
For each Demandbase attribute you want to send to Personalization, you must configure a separate variable in the tag manager.
Note
Ensure the data layer variable matches the attribute returned from Demandbase.
Sign in to your tag manager.
From the Variable Configuration page in your tag manager, create a Data Layer Variable type for your Demandbase audience and set as the Default Value.
You must configure Personalization as the tag to reference the preceding variable.
Configuring the Personalization script
You must configure the following Personalization script in your tag manager to trigger from the Demandbase_loaded event created in Creating a custom event:
/*
** THIS VERSION OF LIFT.JS IS FOR ACQUIA LIFT VERSION 3
*/
<script type="text/javascript">
window.AcquiaLift = {
/*
** ACCOUNT PROPERTIES | MANDATORY | Should be the same across all sites in the same account
** Content values need to be the same as what's Lift Profile Manager, Admin > Customer Sites > Customer Details
** The following values are examples. Update all variables for your own installation of Acquia Lift
*/
account_id: "LIFTUNIVERSITY",
liftAssetsURL: "https://lift3assets.lift.acquia.com/stable",
liftDecisionAPIURL: "https://us-east-1-demo-decisionapi.lift.acquia.com",
authEndpoint: "https://us-east-1-demo-oauth2.lift.acquia.com/authorize",
contentReplacementMode: "trusted",
/*
** SITE ID | MANDATORY | Should be different for each site and environment in the same account
** Content value needs to be created and match what's in Lift Profile Manager
** Admin > Manage Configuration Data > Customer Sites
*/
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://lift3assets.lift.acquia.com/stable/lift.js"></script>
By configuring the Personalization script to trigger from the Demandbase event, you ensure you send all Demandbase data to your website before running Personalization.
Mapping Demandbase attributes to UDF fields in Personalization
Within your Personalization script, you can map the Demandbase attributes, created as variables, to UDF fields in Personalization.
UDF fields can be person, touch, or event fields. The person data field uses Demandbase data.
Click the Add new column meta data link, and enter values in the fields. For more information about column meta data field values, see Adding a column name in Using column meta data.
After adding new column meta data, you’ll receive the data to be sent to Personalization from the preceding script you configured in Configuring the Personalization script.
If you want to use this data for segmentation, ensure you check the Segmentable box and enter corresponding values in the form fields as shown in the following screenshot:
Your website can now pull Demandbase data into Personalization.
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.
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.
Personalization