# Events When mail is processed through ZAP-POST, your HubSpot contacts will be updated with timeline events to keep you informed of any progress.\ Below is a list of a key events and the data you can expect to see in HubSpot when these events occur.\ 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/). {% hint style="success" %} In order to see your ZAP\~POST events in the HubSpot UI you will need to enable them in your activity filters. \ This can be done on the Contact or Company activity tab.
![](/files/JW21pQAVwL3pIfT9kkQV)
{% endhint %} ### 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. Jul 28, 2025 CampaignName: The name of the campaign that record was submitted against CampaignId: The unique identifier for the ZAP~POST campaign ``` ### Address Updated - Added if the profiles' address is updated due to postage address checks ``` Event Name: ZAP~POST Address Updated 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. Jul 28, 2025 CampaignName: The name of the campaign that record was submitted against CampaignId: The unique identifier for the ZAP~POST campaign OriginalAddress: The original address details received from Klaviyo UpdatedAddress: The updated address received due postage address checks ``` ### 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. Jul 28, 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. Jul 28, 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. Jul 28, 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. Jul 28, 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: 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/hubspot/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.