Contextual Data/Triggering is a feature introduced alongside the new API endpoint, which allows you to 'achieve' Events via API, and send along Contextual Data simultaneously. This could be part of a Transactional Email Execution, where you send the data along which is to be merged into the order confirmation email. The data will only exists in the context of the execution, and is therefore not stored in the system afterwards.
The 'magic' of 'Contextual Parameters and Triggering' happens behind the scenes and therefore has a few necessary configurations to be made, before you dive into configuring the actual email.
This type of email execution differs in the way it contains dynamic data fields, which are populated with data contained in the API-Call also used to trigger the Agillic Event and Flow.
If you want to use this data for target groups and conditions, consider importing it to the Agillic Data model with a file import later on.
In summary, you will have to define the data fields to be used for storing the Contextual data. These are not created in User Interface, but rather as part of a JSON-formatted file uploaded to the WebDAV server.
Read more about the Contextual Trigger API-Call.
Read more about the Contextual Data configuration.
Configuring an Email to use Contextual Data
Contextual Data field are accessed through the familiar Content Block type selector, in combination with the Personalise panel, used for inserting Person Data, Unique-Lookups etc.
Configuring a One-to-Many (OTM) content block to utilise data from a Contextual Data OTM