> For the complete documentation index, see [llms.txt](https://userguide.zappost.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://userguide.zappost.com/zap-integrations/zap-post-integrations/dotdigital/events.md). # Events When Dot Digital 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/). ### Submission Creation - Added when the profile is received into ZAP-POST ``` Event Name: ZAP~POST Submission Created ScheduledSendId: The unique identifier for the ZAP~POST Scheduled Send SubmissionId: The unique identifier given to a batch of records submitted to ZAP~POST ScheduledSendDateUTC: The date for the scheduled send e.g. 01/01/2025 CampaignName: The name of the campaign that record was submitted against CampaignId: The unique identifier for the ZAP~POST campaign ``` ### Direct Mail Rejected - Added if the profiles address fails postage address checks ``` Event Name: ZAP~POST Direct Mail Rejected ScheduledSendId: The unique identifier for the ZAP~POST Scheduled Send SubmissionId: The unique identifier given to a batch of records submitted to ZAP~POST ScheduledSendDateUTC: The date for the scheduled send e.g. 01/01/2025 CampaignName: The name of the campaign that record was submitted against CampaignId: The unique identifier for the ZAP~POST campaign RejectedDate(UTC): The date the record was rejected ``` ### Direct Mail Sent - Add when the ZAP has been sent ``` Event Name: ZAP~POST Direct Mail Sent ScheduledSendId: The unique identifier for the ZAP~POST Scheduled Send SubmissionId: The unique identifier given to a batch of records submitted to ZAP~POST ScheduledSendDateUTC: The date for the scheduled send e.g. 01/01/2025 CampaignName: The name of the campaign that record was submitted against CampaignId: The unique identifier for the ZAP~POST campaign ``` ### QR Code Scan - Added if a recipient scans a QR code on the ZAP ``` Event Name: ZAP~POST QR Code Scan ScheduledSendId: The unique identifier for the ZAP~POST Scheduled Send SubmissionId: The unique identifier given to a batch of records submitted to ZAP~POST ScheduledSendDateUTC: The date for the scheduled send e.g. 01/01/2025 CampaignName: The name of the campaign that record was submitted against CampaignId: The unique identifier for the ZAP~POST campaign ScanDate(UTC): The date the QR code was scanned ScanTime(UTC): The time the QR code was scanned DestinationURL: The URL the recipient was directed to ``` ### Direct Mail Returned - Added if the ZAP is returned to sender ``` Event Name: ZAP~POST Direct Mail Returned ScheduledSendId: The unique identifier for the ZAP~POST Scheduled Send SubmissionId: The unique identifier given to a batch of records submitted to ZAP~POST ScheduledSendDateUTC: The date for the scheduled send e.g. 01/01/2025 CampaignName: The name of the campaign that record was submitted against CampaignId: The unique identifier for the ZAP~POST campaign ReturnedDate(UTC): The date the returned Zap was received to sender ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://userguide.zappost.com/zap-integrations/zap-post-integrations/dotdigital/events.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.