Collecting CHEQ Data

Create Variables in Adobe Analytics

To see CHEQ data in Adobe Analytics, you must first create variables to store the data. Typically, we recommend storing this data as an eVar; but please leverage whatever methodology is preferred by your organization. With that said, we recommend using the following eVar configuration (you do not have to use the same eVar slots used in this example):

Variable 1

Adobe Tags (Launch)

To send CHEQ data to Adobe Analytics, please ensure you've first followed the implementation steps from the Adobe Launch instructions. Once you've created your Data Elements, you're able to create Rules and input the values into Adobe Analytics tags.

Data is most frequently sent via one of 2 Extensions in Adobe Launch: the Adobe Analytics Extension or the Web SDK Extension (both shown below).

You will likely use 1 of these 2 methods to send data to Adobe Analytics.

Send CHEQ data with the Pageview Tag

The first place to attempt to capture the variable is in the Pageview. This is important because CHEQ may be able to classify the traffic faster than Adobe Analytics (or Launch) is able to initialize. Therefore, a Supplemental Tag might not trigger. This is more common with an inline CHEQ tag implementation, but is still possible.

Adobe Analytics Extension

Find where your Variables are set for your pageview tag. Typically, this is in the same Rule as your Send Beacon action. 

Scroll down to the Set Variables Action and open it. 

Select the variables you created to store the CHEQ data in Adobe Analytics. Click on the Database icons next to the input fields and select the Data Elements you created in the Implementation step that correspond with the variables.

Click Keep Changes. Save the Rule to your working library.

Web SDK Extension

There are a number of ways to send data via Web SDK. One of the most common methodologies is by creating a "global" XDM Data Element that serves as the base tag for any payload that is sent to AEP. The easiest way to ensure CHEQ data is sent in the pageview (or any available opportunity) is to add it to your global XDM Data Element.

Select the variables you created to store the CHEQ data in Adobe Analytics. Click on the Database icons next to the input fields and select the Data Elements you created in the Implementation step that correspond with the variables.:

Save the Data Element to your working library.

Send CHEQ data with a Supplemental Tag

To ensure complete coverage, we recommend adding a supplemental tag in case a CHEQ verdict isn't returned before a Pageview triggers. To do this, first create a new Rule by going to Rules and clicking Add Rule.

Under Events, click + Add. If you're using Local Storage and triggering an Event, you'll fill out the Event interface similar to what's below (replace cheq_response with whatever name you put into the Event Name box). 

If you're using the Data Layer Push connector, please trigger the rule via your data layer extension and the Event Name you specified in the CHEQ interface.

Adobe Analytics Extension

If you're using the Adobe Analytics extension, your rule might be set up like this. Set Variables and Send Beacon are required Actions. 

First, add an action by clicking + Add. Select the Adobe Analytics Extension and Set Variables as the Action Type and set your eVars, similar to how you did it in the Pageview step.

Click Keep Changes.

Finally, click + Add to add another Action. Again, select the Adobe Analytics Extension and choose the Send Beacon Action Type. and name it whatever makes the most sense in your Adobe Analytics dataset:

Click Keep Changes. Save the Rule to your working library.

Web SDK Extension

If you're using the Web SDK extension, your rule might be set up like this. Update Variable and Send Event are your likely Actions, where Send Event would be required. Keep in mind that everyone's implementation is different, so please consult with your CHEQ representative or internal analytics implementation specialist if you're unsure. 

First, add an action by clicking + Add. Select the AEP Web SDK Extension and Update Variable as the Action Type and set your web.webInteraction.linkClicks.id value as whatever Custom Link name you would normally set for Adobe Analytics.

Click Keep Changes.

Finally, add another action by clicking + Add. Select the AEP Web SDK Extension and Send Event Action Type. For the Type field, you'll likely use Web Webinteraction Link Clicks. For XDM, you'll likely use a Data Element you created to merge the Global XDM object with your XDM Variable Data Element.

Click Keep Changes. Save the Rule to your working library.