# Events When Ometria 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](https://userguide.zappost.com/) and [API Documentation](https://apidocumentation.zappost.com/).\ These events can then be used in your Ometria Campaign flows. ### 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 ``` [^1]: --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://userguide.zappost.com/zap-integrations/zap-post-integrations/ometria/events.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.