This feature allows you to write a function to validate events in your Assurance session. The function should expect an array of Assurance events and should return:
A boolean (true or false) OR
An object that contains a status property with an optional array of event UUIDs
Universally unique identifier for the event.
Timestamp from the device when the event was sent from the SDK.
Used to order when the event was sent. This key is useful when events have the same timestamp.
Vendor identification string in the reverse domain name format (for example, com.adobe.griffon).
Used to denote the type of event.
Defines the data for the event and contains unique and common properties. Some common properties include ACPExtensionEventSource and ACPExtensionEventType.
An array of annotation objects.
Universally unique identifier for the annotation.
Used to denote the type of annotation and is usually the name of the plugin (for example, analytics).
Defines the data that should supplement the event. For Adobe Analytics, this is where the post-processed hit data is contained.
Returning Validation Results
To execute the code in the code editor, click Validate. The function should return a boolean (true or false) or an object that contains a status property and optionally an array of event UUIDs.
Indicates whether the events being evaluated are valid (true) or invalid (false).
(Optional) An array of event UUIDs. If provided with an invalid status, an event list displays the relevant events.
When the view is first loaded, it provides an empty function with JSDoc comments that define how the function accepts the events parameter with the expected return output. Currently, the view allows you to manage several validation scripts by leveraging the browser's cache.
You can create a new validation script by editing the existing script’s name in the drop-down list. To save or delete the script, click Save or Delete.