- Introduction
-
Getting Started
- Creating an Account in Hevo
- Subscribing to Hevo via AWS Marketplace
- Subscribing to Hevo via Snowflake Marketplace
- Connection Options
- Familiarizing with the UI
- Creating your First Pipeline
- Data Loss Prevention and Recovery
- Upgrading Pipeline from Standard to Edge
-
Data Ingestion
- Types of Data Synchronization
- Ingestion Modes and Query Modes for Database Sources
- Ingestion and Loading Frequency
- Data Ingestion Statuses
- Deferred Data Ingestion
- Handling of Primary Keys
- Handling of Updates
- Handling of Deletes
- Hevo-generated Metadata
- Best Practices to Avoid Reaching Source API Rate Limits
-
Edge
- Data Ingestion
- Core Concepts
-
Pipelines
- Familiarizing with the Pipelines UI
- Creating an Edge Pipeline
- Working with Edge Pipelines
- Pipeline Job History
- Pipeline Overview
- Needs Attention
- Object and Schema Management
- Activity Log
-
Sources
- Connect AI
- PostgreSQL
- Oracle
- MySQL
- SQL Server
- Troubleshooting Database Sources
- CockroachDB
- MongoDB
- SharePoint
- Salesforce Bulk API V2
- Ordergroove
- BambooHR
- Stripe
- NetSuite SuiteAnalytics
- Shopify
- Slack
- ClickUp
- Monday.com
- Pipedrive
- Workable
- Fathom
- HubSpot
- Salesforce Marketing Cloud
- Google Analytics 4
- Google Ads
- Facebook Ads
- Microsoft Ads
- LinkedIn Ads
- Xero
- Instagram Business
- Amazon Selling Partner
- TikTok Ads
- StackAdapt
- Amazon Ads
- Pinterest Organic
- Zendesk Support
- Snapchat Ads
- TikTok Organic
- Google Search Console
- Klaviyo v2
- Braintree Payments
- Facebook Pages
- Tempo
- PayPal
- Auth0
- Pinterest Ads
- Apple Search Ads
- Permit.io
- Amplitude Analytics
- Customer.io
- Paddle
- Jira Cloud
- Fullstory
- GitHub
- WorkOS
- ActiveCampaign
- Campaign Monitor
- Infobip
- Mailgun Send
- Metaplane
- Notion
- Recharge
- sevdesk
- Statuspage
- Teamwork.com
- Workday RaaS
- Yotpo
- TikTok Shop Partner Center
- Linear
- Microsoft Dynamics 365 Business Central
- Checkout.com
- Pylon
- Increase
- Microsoft Teams
- Rollbar
- Toggl Track
- QuickBooks Online
- Zoho Desk
- Livestorm
- Attentive
- SendGrid
- Bitly
- Shortcut
- Buzzsprout
- Persona
- Mailjet
- Open Exchange Rates
- PagerDuty
- CircleCI
- SonarQube
- Chargebee
- Freshdesk
- Bing Webmaster Tools
- Rundeck
- Cal.com
- Mixpanel
- Matomo
- Walmart Marketplace
- Xray
- Reddit Ads
- Postmark
- Zoho Recruit
- HiBob
- Freshchat
- Zoho Books
- Marketo
- LaunchDarkly
- Outreach
- Airtable
- Attio
- Okta
- Zendesk Chat
- Bigin by Zoho CRM
- Brevo
- Naming Conventions for Source Data Entities
- Destinations
- Transformations
- Alerts
- Activate
- Custom Connectors
-
Data Loading
- Loading Data in a Database Destination
- Loading Data to a Data Warehouse
- Optimizing Data Loading for a Destination Warehouse
- Deduplicating Data in a Data Warehouse Destination
- Manually Triggering the Loading of Events
- Scheduling Data Load for a Destination
- Loading Events in Batches
- Data Loading Statuses
- Data Spike Alerts
- Name Sanitization
- Table and Column Name Compression
- Parsing Nested JSON Fields in Events
-
Pipelines
- Data Flow in a Pipeline
- Familiarizing with the Pipelines UI
- Working with Pipelines
- Managing Objects in Pipelines
- Pipeline Jobs
-
Transformations
-
Python Code-Based Transformations
- Supported Python Modules and Functions
-
Transformation Methods in the Event Class
- Create an Event
- Retrieve the Event Name
- Rename an Event
- Retrieve the Properties of an Event
- Modify the Properties for an Event
- Fetch the Primary Keys of an Event
- Modify the Primary Keys of an Event
- Fetch the Data Type of a Field
- Check if the Field is a String
- Check if the Field is a Number
- Check if the Field is Boolean
- Check if the Field is a Date
- Check if the Field is a Time Value
- Check if the Field is a Timestamp
-
TimeUtils
- Convert Date String to Required Format
- Convert Date to Required Format
- Convert Datetime String to Required Format
- Convert Epoch Time to a Date
- Convert Epoch Time to a Datetime
- Convert Epoch to Required Format
- Convert Epoch to a Time
- Get Time Difference
- Parse Date String to Date
- Parse Date String to Datetime Format
- Parse Date String to Time
- Utils
- Examples of Python Code-based Transformations
-
Drag and Drop Transformations
- Special Keywords
-
Transformation Blocks and Properties
- Add a Field
- Change Datetime Field Values
- Change Field Values
- Drop Events
- Drop Fields
- Find & Replace
- Flatten JSON
- Format Date to String
- Format Number to String
- Hash Fields
- If-Else
- Mask Fields
- Modify Text Casing
- Parse Date from String
- Parse JSON from String
- Parse Number from String
- Rename Events
- Rename Fields
- Round-off Decimal Fields
- Split Fields
- Examples of Drag and Drop Transformations
- Effect of Transformations on the Destination Table Structure
- Transformation Reference
- Transformation FAQs
-
Python Code-Based Transformations
-
Schema Mapper
- Using Schema Mapper
- Mapping Statuses
- Auto Mapping Event Types
- Manually Mapping Event Types
- Modifying Schema Mapping for Event Types
- Schema Mapper Actions
- Fixing Unmapped Fields
- Resolving Incompatible Schema Mappings
- Resizing String Columns in the Destination
- Changing the Data Type of a Destination Table Column
- Schema Mapper Compatibility Table
- Limits on the Number of Destination Columns
- File Log
- Troubleshooting Failed Events in a Pipeline
- Mismatch in Events Count in Source and Destination
- Audit Tables
- Activity Log
-
Pipeline FAQs
- Can multiple Sources connect to one Destination?
- What happens if I re-create a deleted Pipeline?
- Why is there a delay in my Pipeline?
- Can I change the Destination post-Pipeline creation?
- Why is my billable Events high with Delta Timestamp mode?
- Can I drop multiple Destination tables in a Pipeline at once?
- How does Run Now affect scheduled ingestion frequency?
- Will pausing some objects increase the ingestion speed?
- Can I see the historical load progress?
- Why is my Historical Load Progress still at 0%?
- Why is historical data not getting ingested?
- How do I set a field as a primary key?
- How do I ensure that records are loaded only once?
- Why can't I see my Pipelines after logging in?
- Events Usage
-
Sources
- Free Sources
-
Databases and File Systems
- Data Warehouses
-
Databases
- Connecting to a Local Database
- Amazon DocumentDB
- Amazon DynamoDB
- Elasticsearch
-
MongoDB
- Generic MongoDB
- MongoDB Atlas
- Support for Multiple Data Types for the _id Field
- Example - Merge Collections Feature
-
Troubleshooting MongoDB
-
Errors During Pipeline Creation
- Error 1001 - Incorrect credentials
- Error 1005 - Connection timeout
- Error 1006 - Invalid database hostname
- Error 1007 - SSH connection failed
- Error 1008 - Database unreachable
- Error 1011 - Insufficient access
- Error 1028 - Primary/Master host needed for OpLog
- Error 1029 - Version not supported for Change Streams
- SSL 1009 - SSL Connection Failure
- Troubleshooting MongoDB Change Streams Connection
- Troubleshooting MongoDB OpLog Connection
-
Errors During Pipeline Creation
- SQL Server
-
MySQL
- Amazon Aurora MySQL
- Amazon RDS MySQL
- Azure MySQL
- Generic MySQL
- Google Cloud MySQL
- MariaDB MySQL
-
Troubleshooting MySQL
-
Errors During Pipeline Creation
- Error 1003 - Connection to host failed
- Error 1006 - Connection to host failed
- Error 1007 - SSH connection failed
- Error 1011 - Access denied
- Error 1012 - Replication access denied
- Error 1017 - Connection to host failed
- Error 1026 - Failed to connect to database
- Error 1027 - Unsupported BinLog format
- Failed to determine binlog filename/position
- Schema 'xyz' is not tracked via bin logs
- Errors Post-Pipeline Creation
-
Errors During Pipeline Creation
- MySQL FAQs
- Oracle
-
PostgreSQL
- Amazon Aurora PostgreSQL
- Amazon RDS PostgreSQL
- Azure PostgreSQL
- Generic PostgreSQL
- Google Cloud PostgreSQL
- Heroku PostgreSQL
- Upgrading Pipelines with PostgreSQL Sources to Use the pgoutput Plugin
-
Troubleshooting PostgreSQL
-
Errors during Pipeline creation
- Error 1003 - Authentication failure
- Error 1006 - Connection settings errors
- Error 1011 - Access role issue for logical replication
- Error 1012 - Access role issue for logical replication
- Error 1014 - Database does not exist
- Error 1017 - Connection settings errors
- Error 1023 - No pg_hba.conf entry
- Error 1024 - Number of requested standby connections
- Errors Post-Pipeline Creation
-
Errors during Pipeline creation
-
PostgreSQL FAQs
- Can I track updates to existing records in PostgreSQL?
- How can I migrate a Pipeline created with one PostgreSQL Source variant to another variant?
- How can I prevent data loss when migrating or upgrading my PostgreSQL database?
- Why do FLOAT4 and FLOAT8 values in PostgreSQL show additional decimal places when loaded to BigQuery?
- Why is data not being ingested from PostgreSQL Source objects?
- Troubleshooting Database Sources
- Database Source FAQs
- File Storage
- Engineering Analytics
- Finance & Accounting Analytics
-
Marketing Analytics
- ActiveCampaign
- AdRoll
- Amazon Ads
- Apple Search Ads
- AppsFlyer
- CleverTap
- Criteo
- Drip
- Facebook Ads
- Facebook Page Insights
- Firebase Analytics
- Freshsales
- Google Ads
- Google Analytics 4
- Google Analytics 360
- Google Play Console
- Google Search Console
- HubSpot
- Instagram Business
- Klaviyo v2
- Lemlist
- LinkedIn Ads
- Mailchimp
- Mailshake
- Marketo
- Microsoft Ads
- Onfleet
- Outbrain
- Pardot
- Pinterest Ads
- Pipedrive
- Recharge
- Segment
- SendGrid Webhook
- SendGrid
- Salesforce Marketing Cloud
- Snapchat Ads
- SurveyMonkey
- Taboola
- TikTok Ads
- Twitter Ads
- Typeform
- YouTube Analytics
- Product Analytics
- Sales & Support Analytics
- Source FAQs
-
Destinations
- Familiarizing with the Destinations UI
- Cloud Storage-Based
- Databases
-
Data Warehouses
- Amazon Redshift
- Amazon Redshift Serverless
- Azure Synapse Analytics
- Databricks
-
Google BigQuery
- Clustering in BigQuery
- Partitioning in BigQuery
- Structure of Data in the Google BigQuery Data Warehouse
- Loading Data to a Google BigQuery Data Warehouse
- Near Real-time Data Loading using Streaming
- Modifying BigQuery Destinations to Use Service Account Authentication
- Troubleshooting Google BigQuery
- Google BigQuery FAQs
- Hevo Managed Google BigQuery
- Snowflake
- Troubleshooting Data Warehouse Destinations
-
Destination FAQs
- Can I change the primary key in my Destination table?
- Can I change the Destination table name after creating the Pipeline?
- How can I change or delete the Destination table prefix?
- Why does my Destination have deleted Source records?
- How do I filter deleted Events from the Destination?
- Does a data load regenerate deleted Hevo metadata columns?
- How do I filter out specific fields before loading data?
- Transform
- Alerts
- Account Management
- Activate
- Glossary
-
Releases-
2026 Releases
- Release 2.53 (August 24 – September 21, 2026)
- Release 2.52 (July 27 – August 24, 2026)
- Release 2.51 (Jun 29 – July 27 , 2026)
- Release 2.50 (Jun 01–29, 2026)
- Release 2.49 (May 04-Jun 01, 2026)
- Release 2.48 (Apr 06-May 04, 2026)
- Release 2.47 (Mar 09-Apr 06, 2026)
- Release 2.46 (Feb 09-Mar 09, 2026)
- Release 2.45 (Jan 12-Feb 09, 2026)
-
2025 Releases
- Release 2.44 (Dec 01, 2025-Jan 12, 2026)
- Release 2.43 (Nov 03-Dec 01, 2025)
- Release 2.42 (Oct 06-Nov 03, 2025)
- Release 2.41 (Sep 08-Oct 06, 2025)
- Release 2.40 (Aug 11-Sep 08, 2025)
- Release 2.39 (Jul 07-Aug 11, 2025)
- Release 2.38 (Jun 09-Jul 07, 2025)
- Release 2.37 (May 12-Jun 09, 2025)
- Release 2.36 (Apr 14-May 12, 2025)
- Release 2.35 (Mar 17-Apr 14, 2025)
- Release 2.34 (Feb 17-Mar 17, 2025)
- Release 2.33 (Jan 20-Feb 17, 2025)
-
2024 Releases
- Release 2.32 (Dec 16 2024-Jan 20, 2025)
- Release 2.31 (Nov 18-Dec 16, 2024)
- Release 2.30 (Oct 21-Nov 18, 2024)
- Release 2.29 (Sep 30-Oct 22, 2024)
- Release 2.28 (Sep 02-30, 2024)
- Release 2.27 (Aug 05-Sep 02, 2024)
- Release 2.26 (Jul 08-Aug 05, 2024)
- Release 2.25 (Jun 10-Jul 08, 2024)
- Release 2.24 (May 06-Jun 10, 2024)
- Release 2.23 (Apr 08-May 06, 2024)
- Release 2.22 (Mar 11-Apr 08, 2024)
- Release 2.21 (Feb 12-Mar 11, 2024)
- Release 2.20 (Jan 15-Feb 12, 2024)
-
2023 Releases
- Release 2.19 (Dec 04, 2023-Jan 15, 2024)
- Release Version 2.18
- Release Version 2.17
- Release Version 2.16 (with breaking changes)
- Release Version 2.15 (with breaking changes)
- Release Version 2.14
- Release Version 2.13
- Release Version 2.12
- Release Version 2.11
- Release Version 2.10
- Release Version 2.09
- Release Version 2.08
- Release Version 2.07
- Release Version 2.06
-
2022 Releases
- Release Version 2.05
- Release Version 2.04
- Release Version 2.03
- Release Version 2.02
- Release Version 2.01
- Release Version 2.00
- Release Version 1.99
- Release Version 1.98
- Release Version 1.97
- Release Version 1.96
- Release Version 1.95
- Release Version 1.93 & 1.94
- Release Version 1.92
- Release Version 1.91
- Release Version 1.90
- Release Version 1.89
- Release Version 1.88
- Release Version 1.87
- Release Version 1.86
- Release Version 1.84 & 1.85
- Release Version 1.83
- Release Version 1.82
- Release Version 1.81
- Release Version 1.80 (Jan-24-2022)
- Release Version 1.79 (Jan-03-2022)
-
2021 Releases
- Release Version 1.78 (Dec-20-2021)
- Release Version 1.77 (Dec-06-2021)
- Release Version 1.76 (Nov-22-2021)
- Release Version 1.75 (Nov-09-2021)
- Release Version 1.74 (Oct-25-2021)
- Release Version 1.73 (Oct-04-2021)
- Release Version 1.72 (Sep-20-2021)
- Release Version 1.71 (Sep-09-2021)
- Release Version 1.70 (Aug-23-2021)
- Release Version 1.69 (Aug-09-2021)
- Release Version 1.68 (Jul-26-2021)
- Release Version 1.67 (Jul-12-2021)
- Release Version 1.66 (Jun-28-2021)
- Release Version 1.65 (Jun-14-2021)
- Release Version 1.64 (Jun-01-2021)
- Release Version 1.63 (May-19-2021)
- Release Version 1.62 (May-05-2021)
- Release Version 1.61 (Apr-20-2021)
- Release Version 1.60 (Apr-06-2021)
- Release Version 1.59 (Mar-23-2021)
- Release Version 1.58 (Mar-09-2021)
- Release Version 1.57 (Feb-22-2021)
- Release Version 1.56 (Feb-09-2021)
- Release Version 1.55 (Jan-25-2021)
- Release Version 1.54 (Jan-12-2021)
-
2020 Releases
- Release Version 1.53 (Dec-22-2020)
- Release Version 1.52 (Dec-03-2020)
- Release Version 1.51 (Nov-10-2020)
- Release Version 1.50 (Oct-19-2020)
- Release Version 1.49 (Sep-28-2020)
- Release Version 1.48 (Sep-01-2020)
- Release Version 1.47 (Aug-06-2020)
- Release Version 1.46 (Jul-21-2020)
- Release Version 1.45 (Jul-02-2020)
- Release Version 1.44 (Jun-11-2020)
- Release Version 1.43 (May-15-2020)
- Release Version 1.42 (Apr-30-2020)
- Release Version 1.41 (Apr-2020)
- Release Version 1.40 (Mar-2020)
- Release Version 1.39 (Feb-2020)
- Release Version 1.38 (Jan-2020)
-
2026 Releases
- Early Access New
Postmark (Edge)
Postmark is an email delivery service that businesses use to send and receive transactional and broadcast emails through an API or SMTP. It provides tools to manage servers, sending domains, templates, and message streams, and to track the delivery, opens, clicks, and bounces of emails.
Hevo uses the Postmark API to replicate the servers, domains, sender signatures, templates, message streams, outbound and inbound messages, bounces, suppressions, and email statistics of your Postmark account to the Destination of your choice. To ingest data, you must provide Hevo with an Account API token. Hevo uses this token to list the servers in your account and reads the data of each server with that server’s own API token, which Postmark returns with the server details. Hevo does not store the server API tokens.
Supported Features
| Feature Name | Supported |
|---|---|
| Capture deletes | Yes, for the Server, Domain, Sender Signature, Template, Message Stream, and Outbound Statistics objects |
| History mode | No |
| Custom data (user-configured tables & fields) | No |
| Data blocking (skip objects and fields) | Yes |
| Resync (objects and Pipelines) | Yes |
| API configurable | Yes |
Prerequisites
-
An active Postmark account exists from which data is to be ingested.
-
You are an Account Owner or Account Admin in Postmark, as only these users can access the Account API tokens.
-
An Account API token is available to provide Hevo access to your Postmark account data.
-
Open tracking and link tracking are enabled on your servers or messages, if you want to ingest the open and click events of your outbound messages. Read How does open tracking work?.
Obtain the Account API Token
Postmark provides two types of API tokens: Account API tokens, which give access to account-level data such as servers, domains, and sender signatures, and Server API tokens, which give access to the data of one server. Hevo needs only an Account API token. Hevo uses it to get the Server API token of each server in your account. Read API overview.
Perform the following steps to obtain the Account API token:
-
Log in to your Postmark account as an Account Owner or Account Admin.
-
In the top navigation bar, click Account, and then click the API Tokens tab.

-
In the Account API tokens section, copy the token. If your account has no Account API token, click Generate another token to create one, and then copy it.

Use this token when configuring your Postmark Source in Hevo. The token remains available on the API Tokens tab, so you can copy it again later. If you delete the Account API token configured in the Pipeline, Hevo cannot authenticate with Postmark, and all active jobs of the Pipeline fail. To resume data replication, modify the Source configuration in the Pipeline with a valid Account API token. Once the updated token is saved, Hevo re-authenticates the Source, and data ingestion resumes from the last saved position.
Configure Postmark as a Source in your Pipeline
Perform the following steps to configure your Postmark Source:
-
Click Pipelines in the Navigation Bar.
-
Click + Create Pipeline in the Pipelines List View.
-
On the Select Source Type page, select Postmark.
-
On the Select Destination Type page, select the type of Destination you want to use.
-
In the Configure Source screen, specify the following:

-
Source Name: A unique name for your Source, not exceeding 255 characters. For example, Postmark Source.
-
In the Connect to your Postmark account section:
- Account API Token: The Account API token that you obtained from your Postmark account.
-
-
Click Test & Continue to test the connection to your Postmark Source. Once the test is successful, you can proceed to set up your Destination.
When you click this button, Hevo performs the following validations:
-
The Account API token is valid. Hevo checks this by listing the servers in your Postmark account.
-
Hevo can read the data of the first server in your account with its Server API token.
-
Data Replication
Hevo replicates data for all the objects selected on the Configure Objects page during Pipeline creation. By default, all supported objects and their available fields are selected. However, you can modify this selection while creating or editing the Pipeline. To ingest a child object, you must also select its parent object. For example, to ingest the Message Outbound To object, you must also select the Message Outbound object. The Data Model lists the child objects of each parent object.
Hevo reads the data of every server in your Postmark account. In the first run of the Pipeline, Hevo ingests data as follows:
-
Bounce, Message Inbound, and Message Outbound objects: The data of the last 45 days. Postmark keeps messages for 45 days unless you increase the retention period of your account.
-
Bounce Count, Browser Usage, Browser Usage Platform, Click Location, Email Client Usage, Platform Usage, and Outbound Statistics objects: The statistics of the last 365 days.
-
All other objects: All the data available in Postmark.
In the subsequent runs, as per the sync frequency, Hevo ingests data as follows:
| Ingestion | Parent Objects |
|---|---|
| New records, based on the time each bounce occurred | Bounce |
| New records, based on the time Postmark received each message | Message Inbound and Message Outbound |
| New records, based on the time each suppression was created | Suppression |
| New open and click events. Hevo reads all the events that Postmark lists and loads only the events received after the previous run | Message Outbound Click and Message Outbound Open |
| The statistics of each day, from the last ingested day to the current day | Bounce Count, Browser Usage, Browser Usage Platform, Click Location, Email Client Usage, and Platform Usage |
| All the records, in each run | Domain, Message Stream, Outbound Statistics, Sender Signature, Server, and Template |
In each run, Hevo also reads the messages and bounces received during the three hours before the previous run, so that records added while the previous run was in progress are not missed. Once a day, Hevo also reads the messages, bounces, and daily statistics of the last seven days again, to capture any changes to them.
Hevo makes up to 40 API requests per second to Postmark. If Postmark returns a rate limit error, Hevo waits for the time that Postmark specifies and retries the request.
Note: You can create a Pipeline with this Source only using the Merge load mode. The Append mode is not supported for this Source.
Schema and Primary Keys
Hevo uses the following schema to upload the records in the Destination. For a detailed view of the objects, fields, and relationships, click the ERD.
Data Model
The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:
| Object | Description |
|---|---|
| Bounce | Contains the bounces recorded for each server, including the bounce type, the email address and message that bounced, the time of the bounce, a description of the reason, and whether the address is inactive. |
| Bounce Count | Contains the number of bounces of each type, such as hard, soft, and transient, for each server and day. |
| Browser Usage | Contains the number of link clicks for each server and day, grouped by the browser family used, such as Chrome, Safari, Firefox, and Edge. |
| Browser Usage Platform | Contains the number of link clicks for each server and day, grouped by platform: desktop, mobile, and unknown. |
| Click Location | Contains the number of link clicks for each server and day, split by whether the link was clicked in the HTML or the text version of the email. |
| Domain | Contains the sending domains of your account, including their DKIM, SPF, and Return-Path verification details. |
| Email Client Usage | Contains the number of email opens for each server and day, grouped by the email client used, such as Apple Mail, Gmail, Outlook, and Yahoo. |
| Message Inbound | Contains the processed inbound messages received by each server, including the sender, subject, bodies, mailbox hash, status, and the reason if a message was blocked. It includes the child objects, Message Inbound Attachment, Message Inbound Cc, Message Inbound Header, and Message Inbound To. |
| Message Inbound Attachment | Contains the attachments of each inbound message, including the name, content type, and content length. |
| Message Inbound Cc | Contains the Cc recipients of each inbound message. |
| Message Inbound Header | Contains the email headers of each inbound message. |
| Message Inbound To | Contains the To recipients of each inbound message. |
| Message Outbound | Contains the outbound messages sent from each server, including the subject, status, bodies, link and open tracking settings, and the time Postmark received each message. It includes the child objects, Message Outbound Attachment, Message Outbound Bcc, Message Outbound Cc, Message Outbound Event, Message Outbound Recipient, and Message Outbound To. |
| Message Outbound Attachment | Contains the attachments of each outbound message. |
| Message Outbound Bcc | Contains the Bcc recipients of each outbound message. |
| Message Outbound Cc | Contains the Cc recipients of each outbound message. |
| Message Outbound Click | Contains the link click events of outbound messages, including the recipient, the clicked link, the click location, the email client, operating system, and platform used, and the geographic location. |
| Message Outbound Event | Contains the delivery events of each outbound message, such as the event type, recipient, receiving server and IP address, and a summary of the event. |
| Message Outbound Open | Contains the open events of outbound messages, including the recipient, the email client, operating system, and platform used, the geographic location, and the read time. |
| Message Outbound Recipient | Contains all the recipients of each outbound message. |
| Message Outbound To | Contains the To recipients of each outbound message. |
| Message Stream | Contains the message streams of each server, including archived streams, with the name, type, description, archive status, and unsubscribe handling settings of each stream. |
| Outbound Statistics | Contains the overall outbound email statistics of each server for the last 365 days, such as the number of emails sent, bounced, opened, and clicked, spam complaints, and the corresponding rates. |
| Platform Usage | Contains the number of email opens for each server and day, grouped by platform: desktop, mobile, webmail, and unknown. |
| Sender Signature | Contains the sender signatures of your account, including the email address, name, confirmation status, and the DKIM and Return-Path verification details of each signature. |
| Server | Contains the servers of your Postmark account, including the name, color, delivery type, inbound address, webhook URLs, and open and link tracking settings of each server. |
| Suppression | Contains the email addresses suppressed on each message stream of a server, along with the reason and origin of each suppression. |
| Template | Contains the email templates of each server, including the name, alias, type, subject, layout, and HTML and text bodies of each template. |
Additional Information
Read the detailed Hevo documentation for the following related topics:
Handling of Deletes
Hevo ingests all the records of the Domain, Message Stream, Outbound Statistics, Sender Signature, Server, and Template objects in each run. When a record is no longer in Postmark, Hevo sets the value of the metadata column _hevo_marked_deleted to True for the record in the Destination.
Hevo does not capture deletes for the other objects. Postmark does not let you delete messages, bounces, or events, and the messages that Postmark removes after the retention period remain in the Destination. If you remove a suppression in Postmark, the record remains in the Destination.
Source Considerations
-
Postmark keeps outbound and inbound messages, and their events, only for the retention period of your account, 45 days by default. Hevo cannot ingest messages that are older than this period. Read How long are Inbound and Outbound messages stored in activity?.
-
Postmark returns at most 10,000 open or click events for each message stream in a query. If a message stream has more events, Hevo reads them by platform. Any events that remain out of reach are not ingested, and Hevo shows a warning for the object.
-
Hevo ingests only the inbound messages that Postmark has processed. Inbound messages that are blocked, scheduled for retry, or failed are not ingested.
-
If Hevo cannot read the data of a server with its Server API token, Hevo skips that server and continues with the other servers.
Revision History
Refer to the following table for the list of key updates made to this page:
| Date | Release | Description of Change |
|---|---|---|
| Nov-11-2026 | 2.54 | New document. |