CHEQ’s enriches your data by introducing new fields for Threat Type (an indicator for the reason of how CHEQ classified the request – automation tools, VPN, click hijacking, etc.), Threat Group (malicious, bot, suspicious, valid, good bots, etc.), AI Traffic Type (agent, crawler, or none), and other dimensions.
Install the CHEQ Library Tag
To find your tag, log into your account to access your Dashboard. In the top-right of your user interface, click on your [Account Name] > Account Settings:
Copy the Invocation tag to your clipboard.
Now open your Adobe Launch property, navigate to Rules, and click Add Rule.
In the rule creation interface, click the + Add button below Events and add an Event to load on Library Loaded (Page Top).
| Field | Description | Example |
| Extension | Core Extension in Launch. | Core |
| Event Type (Recommended) | Tells Launch when/where the tag should be triggered. | Library Loaded (Page Top) |
| Name (Recommended) | Some name that makes sense. This doesn't impact functionality. | Page Top |
Click Keep Changes in the top-right.
While we recommend loading our tag as the highest priority and Page Top (Library Loaded), we also understand that there could be reasons that this isn't possible. This recommendation mitigates certain race conditions, but is not always required.
Next, click on the + Add button below Actions and add HTML.
| Field | Description | Example |
| Extension | Core Extension in Launch. | Core |
| Event Type | Sets the type of action that will be executed. | Custom Code |
| Name (Recommended) | Some name that makes sense. This doesn't impact functionality. Use all caps if you're really excited. | CHEQ Tag |
Next, click Open Editor and copy/paste the <script> tag.
Click Save, then click Keep Changes in the top-right. Finally, Save the rule. That's it!
What about the <noscript> tag?
Adobe Launch is exclusively a JavaScript-based tag and, as such, does not support <noscript>tags (the tag that detects users with JavaScript disabled). If your business use case requires capturing these users, consider deploying the <noscript> tag immediately after the opening of the <body> tag.
Data Layer Integration
Note: This feature is for CHEQ Analytics customers only.
The Data Layer Connector allows CHEQ Analytics users to quickly and easily plug CHEQ data into Adobe Data Collection Tags (Launch).
Configure the Data Layer
In the CHEQ platform, navigate to Analytics > Settings > Data Layer. Configure the Data Layer Connector to use the data layer structure that is native to your analytics implementation, similar to what's shown below:
Creating Data Elements
Navigate to the Adobe Data Collection Tags property and create a new Data Element to store your variable(s) from the Data Layer Push connector. Create a new Data Element to store your value(s) from the Data Layer connector. Create a Data Element for each Key specified in the Data Layer Connector (see below):
The configuration for each Key should look something like this:
| Field | Description | Example |
| Name | User-defined name of the Data Element. | User | Threat Group |
| Extension | Recommended extension that supports Data Layer Push methodology. | Adobe Client Data Layer |
| Type | Required type of the Data Element. | Data Layer Computed State |
| Path | Represents a Key that was input from the Data Layer Connector interface. | threat_group |
| Storage Duration | Determines how long the value will be stored in the browser. For most cases, leave it as "None". | None |
From here, the Data Element can be used in any Rule in your Web Property.
Detecting Data Layer Updates
An event is assigned in every payload, which will proactively signal that the user’s status has changed (for instance, from Valid to Malicious). This event will trigger every time the status is changed, including the first time it is set. This is especially useful to eliminate race conditions because users can trigger a server call when the status is set instead of relying on the data to be sent with the pageview payload.
Note: Please ensure you have considered implications on hit volume in your analytics tool, as the event currently triggers once per page load. Consider adding a custom condition to load once per session.
The following example is used with the Adobe Client Data Layer Adobe Launch extension:
| Field | Description |
| Name | User-defined name of the Rule’s Event. |
| Extension | Select Adobe Client Data Layer. |
| Event Type | Select Data Pushed. |
| Listen to | Select Specific Event. |
| Time scope | Select All. |
| Event / Key to register for | Whatever the value was set for the Event in your Data Layer connector settings. |
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
| Field | Value |
| Name (Suggested) | CHEQ Threat Group |
| Status | Enabled |
| Allocation | Most Recent (Last) |
| Expire After | Never |
| Enable Merchandising | Disabled |
Variable 2
| Field | Value |
| Name (Suggested) | CHEQ Threat Type |
| Status | Enabled |
| Allocation | Most Recent (Last) |
| Expire After | Never |
| Enable Merchandising | Disabled |
Send CHEQ data with a Supplemental Tag
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.
Create the Rule
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).
| Field | Value |
| Name (Suggested) | CHEQ Response |
| Extension | Core |
| Type | Custom Event |
| Custom Event Type | cheq_response |
| CSS Selector | body |
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.