Follow up in the mailbox, not the promotions tab

It is addressed mail fired by a signal instead of a calendar. A cart left behind, a customer gone quiet, a lead that stalled: the event reaches Oppizi from your stack, and a personalized piece prints and dispatches inside a four-day SLA. In Canada the audience comes from records you already hold, never from tracking anonymous browsing. Delivery is to a real address, so no blocker, no promotions tab and no bid to win.

Digital retargeting leans on cookies that keep vanishing, pays into an auction that keeps rising, and disappears the instant someone scrolls on. A triggered piece arrives at the household, stays in the home for days, and carries the trust Canadians give physical mail: almost 70% say it is more personal and trustworthy than digital communication. Triggered mail runs off the very signals your email programs already use.

Any signal your connected stack can send, on an event or on a clock: a cart or application left unfinished, a purchase, a loyalty milestone, a dormancy threshold, a lifecycle stage, a custom event out of your CRM or CDP. Trigger rules and filters are yours to set, so only well-matched contacts qualify. Caps prevent over-mailing, and anyone who bought or opted out is dropped before the file goes to print.

No. Oppizi does not offer identity resolution of anonymous website visitors in Canada, and there is no lookalike modelling on Canadian addressed mail. Triggered mail here goes to people whose address you already hold, which keeps the audience yours and the consent trail clean. If you need more reach than your list gives you, widen an addressed campaign with demographic third-party data, B2B records and geographic layering, which target households on attributes rather than on browsing behaviour.

Closed-loop, piece by piece. Each mailer carries a QR code and a promo code bound to the trigger that produced it, and a CRM match links whatever the contact does next to that piece. One signal, one recipient, one campaign means cost per conversion reads at trigger level, so you can compare a cart-abandon flow against a win-back flow in the same dashboard you use for email.

Print and dispatch happen inside a four-day SLA of the trigger, so the piece shows up while intent is still warm instead of three weeks after the cart went cold. Print is arranged near the delivery area, which keeps transit short. There is no weekly batch to wait on either: a trigger produces its own piece the moment it fires.

Braze and Shopify connect natively, and any other CRM, CDP or warehouse can reach Oppizi through the API and webhooks or send an SFTP data feed. Once connected, audience events arrive on their own, so mail runs off the same lifecycle and event triggers as your email programs. Campaign results flow back into your stack, and the headless setup lets an engineering team build a custom flow instead of using ours.

It is built that way. The audience is customer data you gathered and control, not behaviour inferred across the web. Infrastructure is certified to SOC 2 Type II, anyone who has bought or opted out falls out of the file automatically, and caps limit how often one person hears from you. Mail also runs outside cookie tracking, so browser privacy changes leave it untouched.