Events

When Adestra contacts are processed through ZAP-POST, they are updated with events to keep you informed of any changes. Events are created automatically and require no additional set up. For detailed information on any of the above fields, see our User Guide and API Documentation. These events are populated into Adestra as Transactions on a contact. These can then be used the same as any other Adestra transaction.

Submission Creation - Added when the profile is received into ZAP-POST

Event Name: zap-post_submission_created

scheduled_send_id: The unique identifier for the ZAP~POST Scheduled Send
submission_id: The unique identifier given to a batch of records submitted to ZAP~POST
scheduled_send_date_utc: The date for the scheduled send e.g. 01/01/2025
campaign_name: The name of the campaign that record was submitted against
campaign_id: The unique identifier for the ZAP~POST campaign

Direct Mail Rejected - Added if the profiles address fails postage address checks

Event Name: post_direct_mail_rejected

scheduled_send_id: The unique identifier for the ZAP~POST Scheduled Send
submission_id: The unique identifier given to a batch of records submitted to ZAP~POST
scheduled_send_date_utc: The date for the scheduled send e.g. 01/01/2025
campaign_name: The name of the campaign that record was submitted against
campaign_id: The unique identifier for the ZAP~POST campaign
rejected_date_utc: The date the record was rejected

Direct Mail Sent - Add when the ZAP has been sent

Event Name: post_direct_mail_sent

scheduled_send_id: The unique identifier for the ZAP~POST Scheduled Send
submission_id: The unique identifier given to a batch of records submitted to ZAP~POST
scheduled_send_date_utc: The date for the scheduled send e.g. 01/01/2025
campaign_name: The name of the campaign that record was submitted against
campaign_id: The unique identifier for the ZAP~POST campaign

QR Code Scan - Added if a recipient scans a QR code on the ZAP

Event Name: post_qr_code_scan

scheduled_send_id: The unique identifier for the ZAP~POST Scheduled Send
submission_id: The unique identifier given to a batch of records submitted to ZAP~POST
scheduled_send_date_utc: The date for the scheduled send e.g. 01/01/2025
campaign_name: The name of the campaign that record was submitted against
campaign_id: The unique identifier for the ZAP~POST campaign
scan_date_utc: The date the QR code was scanned
scan_time_utc: The time the QR code was scanned
destination_url: The URL the recipient was directed to

Direct Mail Returned - Added if the ZAP is returned to sender

Event Name: post_direct_mail_returned

scheduled_send_id: The unique identifier for the ZAP~POST Scheduled Send
submission_id: The unique identifier given to a batch of records submitted to ZAP~POST
scheduled_send_date_utc: The date for the scheduled send e.g. 01/01/2025
campaign_name: The name of the campaign that record was submitted against
campaign_id: The unique identifier for the ZAP~POST campaign
returned_date_utc: The date the returned Zap was received to sender