Please ensure all prerequisite steps mentioned here have been completed before proceeding with the configuration below.
Create Schema Fields
In your web schema, create a field (or multiple fields) for Threat Group and Threat Type. Every AEP implementation has a different schema. In the screenshot below, dimensions were created within Adobe’s Bot Detection Information field group. We recommend adding and naming the dimensions whatever makes the most sense for your business.
Field 1
| Field | Value |
| Field Name (Suggested) | threat_group |
| Display Name (Suggested) | Threat Group |
| Type | String |
Field 2
| Field | Value |
| Field Name (Suggested) | threat_type |
| Display Name (Suggested) | Threat Type |
| Type | String |
Adobe Tags (Launch)
With the fields defined, the next step is to send the data into AEP. To do this, you will use Adobe Data Collection Tags (Launch).
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 AEP (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.
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.
Find the Fields you created to store the CHEQ data. 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 Fields.:
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):
Event Configuration
| Field | Value |
| Name (Suggested) | CHEQ Response |
| Extension | Core |
| Type | Custom Event |
| Custom Event Type | cheq_response |
| CSS Selector | body |
Click Keep Changes.
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.
Next, scroll down to the Actions section and click + Add. Populate the configuration with the information below with the (Global or Merged) XDM Object Data Element:
Action Configuration
| Field | Value |
| Extension | AEP Web SDK |
| Type | Send Event |
Click Keep Changes. Save the Rule to your working library.