Acquia CDP
Using the Conversion Optimization by VWO connector
This page provides information about how to use the Conversion Optimization by VWO connector feature for the following scenario:
Marketers and data analysts aim to efficiently create, manage, and synchronize audiences through Customer Data Platform (CDP) for Conversion Optimization by VWO connector to transform manual processes and enhance campaign efficiency.
Before you configure segment fetching, you must:
Install the VWO Smartcode on your website.
Deploy CDP WebTag 2.0, as legacy WebTag does not support segment fetching.
An active Acquia Conversion Optimization subscription.
You must use WebTag 2.0 to perform this configuration because the legacy WebTag does not support this parameter. To configure CDP Global Tag:
Locate the CDP Global Tag.
Ensure the segments parameter is set to true. This setting loads the window.AcquiaCdpSegments API necessary to configure the Conversion Optimization fetching tag.
If the parameter is not present, manually update the Global Tag with the Segments parameter.
<script>
var $A1Config = {
webtagId: "your-webtag-id", // Paste your webtagId value provided by Acquia.
tenantId: 999, // Example set the static tenant ID.
host: "//url.endpoint.com", // Set the service endpoint URL according to your hosted environment and cloud region.
segments: true // Set the service endpoint to True if you have an Acquia Convert Optimization subscription with us for VWO access.
};
</script>
<script src="https://scripts.agilone.com/latest/acquia-cdp-webtag.js"></script>You must add the tag that retrieves segments based on the visitor identity defined in the configuration for CDP visitor tag. To configure the fetching tag:
Create a new tag configuration.
Set the Tag Type to Custom HTML.
Copy the following code into the HTML editor:
<script>
if (window.AcquiaCdpSegments && window.AcquiaCdpSegments.fetchSegments) {
window.AcquiaCdpSegments.fetchSegments({'key': 'value'}); // Fetch segments the visitor identity from data layer based on your CDP visitor object.
}
</script>The parameters in fetchSegments() must exactly match the key and value structure defined in the Customer Data Platform (CDP) visitor WebTag.
Before you implement segment fetching, you must understand three key decisions:
Identify which attribute identifies visitors, such as a default attribute or custom attribute.
Determine if this attribute must be visible in CDP UI, as custom attributes require specific configuration.
Determine if the data must be encrypted in transit, which requires the use of the email key.
| Component | Description | Fetching tag |
|---|---|---|
| Key | The parameter name in the fetching script. |
|
| Value | The actual visitor identifier for the person. |
|
To encrypt data in transit, the fetching script must use the email key regardless of the attribute selected in the campaign.
Encryption in transit is active: The fetching script recognizes email as a special key that triggers automatic encryption to meet security requirements for Personally Identifiable Information (PII) protection.
window.AcquiaCdpSegments.fetchSegments({
'email': '[email protected]' // PII Encrypted
});
window.AcquiaCdpSegments.fetchSegments({
'email': '[email protected]' // PII Encrypted
});Encryption in transit is not active: If you use any other key name, even for email data, the system sends data unencrypted.
window.AcquiaCdpSegments.fetchSegments({
'CUSTOMERSUMMARY_EMAIL': '[email protected]' // PII Unencrypted
});
window.AcquiaCdpSegments.fetchSegments({
'CUSTOMERSUMMARY_EMAIL': '[email protected]' // PII Unencrypted
});Hashed data: You can pass a CDP compatible SHA-256 hashed value.
window.AcquiaCdpSegments.fetchSegments({
'CUSTOMERSUMMARY_EMAILHASH': 'aSc34Erv' // SHA-256
});
window.AcquiaCdpSegments.fetchSegments({
'CUSTOMERSUMMARY_EMAILHASH': 'aSc34Erv' // SHA-256
});Non-PII custom attributes: The value remains unencrypted when you use a CDP Studio custom attribute or any key other than the default.
window.AcquiaCdpSegments.fetchSegments({
'CUSTOMER_C_CUSTOMERSTRINGATTRIBUTE30': 'ABC123' // Exact Value eg. VWO_UUID
});This section provides instructions for manually configuring the conversion optimization fetching tag. Add the following scripts to the <head> section of your website:
CDP Global Tag: This script enables the segment fetching features.
Segment Fetching Script: This script retrieves segments for the visitor.
Add or modify this script as early as possible in the <head> section of your pages:
<script>
var $A1Config = {
webtagId: "your-webtag-id", // Paste the webtagId value provided by Acquia.
tenantId: 999, // Set the static tenant ID.
host: "//url.endpoint.com", // Set the service endpoint URL for your hosted environment and cloud region.
segments: true // Set to true for Acquia Convert Optimization subscription with VWO access.
};
</script>
<script src="https://scripts.agilone.com/latest/acquia-cdp-webtag.js"></script>| Parameters | Description |
|---|---|
webtagId, tenantId, host | Follow the instructions here. |
segments | If the parameter exists in the global script, set the value to true. If the parameter is missing, update the global tag to include the default parameter segments. |
This setting loads the window.AcquiaCdpSegments API required to configure the conversion optimization fetching tag. Without segments: true, the segment fetching script cannot work.
To retrieve segments based on the visitor identity defined in the CDP visitor tag, add the following tag:
<script>
if (window.AcquiaCdpSegments && window.AcquiaCdpSegments.fetchSegments) {
window.AcquiaCdpSegments.fetchSegments({'key': 'value'}); // Fetch segments the visitor identity from data layer based on your CDP visitor object.
}
</script>Before you implement segment fetching, you must understand these three key decisions:
Identify the attribute to identify visitors, such as a default attribute or custom attribute.
Determine if this attribute must be visible in the CDP User Interface (UI), as custom attributes require specific configuration.
Determine if the data must be encrypted in transit, which requires the use of the email key.
| Component | Description | Fetching tag |
|---|---|---|
| Key | The parameter name in the fetching script. |
|
| Value | The actual visitor identifier for the person. |
|
To encrypt data in transit, the fetching script must use the email key regardless of the attribute selected in the campaign.
Encryption in transit is active: The fetching script recognizes email as a special key that triggers automatic encryption to meet security requirements for Personally Identifiable Information (PII) protection.
window.AcquiaCdpSegments.fetchSegments({
'email': '[email protected]' // PII Encrypted
});window.AcquiaCdpSegments.fetchSegments({
'email': '[email protected]' // PII Encrypted
});
Encryption in transit is not active: If you use any other key name, even for email data, Customer Data Platform (CDP) sends data unencrypted.
window.AcquiaCdpSegments.fetchSegments({
'CUSTOMERSUMMARY_EMAIL': '[email protected]' // PII Unencrypted
});window.AcquiaCdpSegments.fetchSegments({
'CUSTOMERSUMMARY_EMAIL': '[email protected]' // PII Unencrypted
});
Hashed data: You can pass a CDP-compatible SHA-256 hashed value.
window.AcquiaCdpSegments.fetchSegments({
'CUSTOMERSUMMARY_EMAILHASH': 'aSc34Erv' // SHA-256
});window.AcquiaCdpSegments.fetchSegments({
'CUSTOMERSUMMARY_EMAILHASH': 'aSc34Erv' // SHA-256
});
Non-PII custom attributes: The value remains unencrypted when you use a CDP Studio custom attribute or any key other than the default.
window.AcquiaCdpSegments.fetchSegments({
'CUSTOMER_C_CUSTOMERSTRINGATTRIBUTE30': 'ABC123' // Exact Value eg. VWO_UUID
});The fetchSegments method accepts only one visitor value type per call. Your team and Acquia must agree on the identifier type.
To create an event in the Convert account:
Navigate to Data 360 and go to the Events section.
Click +Create to create an event.
Enter the event name as cdpSegmentsEvent.
The event name is case-sensitive. You must not change the event name or enter a different name to ensure that CDP segments function correctly.
Click Create to finalize the event setup.
To create a trigger:
Navigate Data 360 and go to the Triggers section.
Click +Create to create a trigger.
Enter the trigger name as cdpSegmentsTrigger.
Click Create to finalize the trigger setup.
Create a CDP campaign and name it as Acquia Conversion optimization - CategoryBrowsed Follow Up.
Add the Performed an event rule for CategoryBrowsed within the last 30 minutes.
Add the Email Status rule as V-verified or U-unknown.
Select the in operator and set the values to V for verified and U for unknown.
In Exclude customers, select the Add group icon and do the following:
Add the Performed an event rule for checkout within the last 15 minutes.
Add the Place a transaction rule.
Select the between operator and set the range to 1-2 days.
After you create a VWO campaign, you can use CDP segments through the following methods:
Explore Personalized and select Create segment.
Rename the segment as CDP/conversion optimization Segment Category: Browse.
Explore Targets and move through to Custom Segment.
Select the list and choose Cookie value.
Set the value to _vwo_segments -> my-aqconvert-seg-cabrowse.
Consult with Acquia Professional Services or a Support team representative to perform these actions:
Ensure proper implementation and configuration.
Address specific integration requirements.
Troubleshoot potential issues.
Optimize performance and use according to best practices.
If segments do not load, perform these steps:
Check the browser console for warning messages.
Ensure that the visitor is properly defined before the script executes.
Ensure that CDP library loads on the page.
Contact an Acquia representative to validate the configuration.
Click Next.
In Content Attributes, select the Add icon to search for and add Email Address - SHA256 Hash.
Ensure that the Professional Services team finalizes the custom attributes so that they are visible in the Child Customer Details tables. To add customer attributes:
In the Content section, click Add.
Search the Child Customer Details tables.
Search for and select the new attributes.
Click Apply.
Select Add new content.
Search for the content Echo.
In the Echo content section, perform the following actions:
In the Header name field, enter the value segmentname.
In the Value name field, enter the value my-aqconvert-seg-cabrowse.
Click Next.
In Destination, select the connector Acquia Conversion Optimization by VWO.
Click Send Now.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Click Next.
In Content Attributes, select the Add icon to search for and add Email Address - SHA256 Hash.
Ensure that the Professional Services team finalizes the custom attributes so that they are visible in the Child Customer Details tables. To add customer attributes:
In the Content section, click Add.
Search the Child Customer Details tables.
Search for and select the new attributes.
Click Apply.
Select Add new content.
Search for the content Echo.
In the Echo content section, perform the following actions:
In the Header name field, enter the value segmentname.
In the Value name field, enter the value my-aqconvert-seg-cabrowse.
Click Next.
In Destination, select the connector Acquia Conversion Optimization by VWO.
Click Send Now.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Acquia CDP