Add the mailbox to your Iterable journeys.

Postie becomes a destination channel your Iterable journeys can activate — using the same events, segments, and suppression logic already running in your lifecycle programs.

 

Three ways to wire Postie into Iterable.

 

Option 1: Direct journey triggers Use Iterable events and segmentation logic to fire a mail send at the right journey step, via webhooks. Postie receives the trigger and executes — no parallel workflow to manage.

 

Option 2: Scheduled audience sync Send audiences via S3 or SFTP on a schedule — daily or weekly. Postie always has the latest segments ready. Best starting point for teams with complex data models.

 

Option 3: Add the Postie pixel Drop the pixel into your tag manager for site behavior retargeting and attribution assist. Adds a behavior signal layer that Iterable events may not capture directly.

 

What Iterable teams run with Postie

 

Six lifecycle moments where direct mail shows up when email doesn’t.

1. Winback with escalating touches “No purchase in 60 or 90 days” triggers mail as part of an escalating winback sequence. Mail is the step that breaks through when email has gone quiet.
2. High-intent retargeting Mail customers showing repeat product views, category obsession, or high-AOV browsing captured via Iterable events. Behavior-driven, not assumed.
3. VIP and loyalty programs Trigger mail on tier changes, loyalty perks, or early access offers. A physical piece lands differently than another push notification for your best customers.
4. Post-purchase replenishment and cross-sell Time mail to arrive at the natural replenishment point, or cross-sell based on purchase history already in Iterable.
5. Subscription risk and churn prevention Trigger mail on churn signals, failed payments, or cancel intent. A physical touchpoint at the moment of highest risk.
6. Event follow-up Segment by attendance outcome — attended, registered, no-show — and trigger a relevant offer via mail within the same journey sequence.

How to connect.
Iterable stays in charge. Postie just adds a channel.

 

Journey triggers via webhooks Iterable fires the trigger. Postie executes the mail send. Your journey logic, suppression rules, and eligibility criteria stay exactly where they are — Postie doesn’t create a parallel system.

 

Scheduled audience sync via S3 or SFTP For teams who want to start clean before layering in real-time triggers. Send audience files on a schedule and Postie builds from there.

 

Postie pixel Drop it into your tag manager for retargeting and attribution signals that complement your Iterable event data.