Outbound Wiki

Article

Dataset query examples | Adobe Journey Optimizer

experienceleague.adobe.com

Open at publisher

Quoted on this wiki

Every place a page here uses this source, in the order the words come in it.

  1. NOTE “A successful custom action HTTP call confirms only that the call completed.” If a query returns “Table not provisioned for dataset” table-not-provisioned

    In Suppression list synchronization

  2. NOTE “It does not confirm that the external system delivered a message.” If a query returns “Table not provisioned for dataset” table-not-provisioned

    In Suppression list synchronization

  3. NOTE “To confirm downstream delivery, check the external system’s logs or reporting.” If a query returns “Table not provisioned for dataset” table-not-provisioned

    In Suppression list synchronization

  4. To check message-delivery feedback for native Journey Optimizer channel actions (such as sent or bounce statuses), use the Message Feedback Event Dataset. “To check email interaction events such as opens and clicks, use the Email Tracking Experience Event Dataset.” To verify that Journey Optimizer executed a custom action, and to inspect its execution status, latency, and error details, use the Journey Step Event dataset.

    In Outbound email analytics

  5. The related schema is AJO Email Tracking Experience Event Schema. “This query shows the counts of different email interactions (opens, clicks) for a given message:” This query shows the breakdown of counts of different email interactions (opens, clicks) by message for a given journey:

    In Outbound email analytics

  6. This query groups message feedback records by test-execution indicator and delivery-feedback status. The result preserves null or missing isTestExecution values so that records without a recorded test-execution value can be reviewed separately. “This query shows the counts of different email feedback status (sent, bounce, etc) for a given message:” This query shows the breakdown of counts of different email feedback status (sent, bounce, etc) by message for a given journey:

    In Outbound email analytics

  7. NOTE “Therefore, to accurately track or attribute events at the individual send level, combine the journeyVersionID, journeyActionID, and batchInstanceID (for batch journeys) or identityMap fields for more precise uniqueness.” Identify quarantined addresses after an ISP outage isp-outage-query

    In Outbound source and campaign tracking

Quotes are verbatim and belong to their publishers. Where a quote has been translated, the original wording is kept below it.