Iterable Agency
BMO Media is an Iterable email marketing agency for apps and consumer brands. We build on Iterable to run cross-channel journeys in which email, push, SMS, in-app and embedded messages pull live product and content data from Catalog. The first step is a free audit of your journeys, catalog and deliverability, yours to keep.
What we do
Why an Iterable specialist, not a generalist
Iterable rewards structure. Journeys branch on any event or user field you send, and Catalog lets a template look up current product, price, stock or content data at the moment of send. Done well, a browse abandonment email shows the item at today's price, the push deep links to the same item, and the embedded slot in your app shows it again when the user returns. Done badly, it is an expensive email tool.
The platform has the scale for that work: more than 1 trillion customer interactions across 1,200+ brands (Iterable via Business Wire, December 2025). The accounts we audit rarely use the depth. Catalog collections go stale or never reach a template. Users sit in three journeys at once with no rule for which one wins. Promotions override lifecycle sends. Email carries everything because push and SMS were never wired into the branches.
A generalist fills the campaign calendar. An Iterable specialist sets journey priority, connects Catalog to the templates that earn most and measures every journey against a holdout. The method is the same on every platform we run: for James Michelle, on Klaviyo, flow-driven email revenue grew 202% year over year.
What's included
What we do inside Iterable
Account audit: the full journey map and where journeys overlap, Catalog health, feed freshness and templates that never touch Catalog, deliverability by sending domain, and revenue per recipient by journey and channel.
Catalog built for templates: product, content or class collections with the fields your templates actually use kept current, so price, stock and imagery are right when the message sends.
Iterable email journeys first: welcome, browse and cart abandonment, post-purchase, replenishment and win-back, each with Catalog-driven blocks and a holdout group.
Channel branching inside each journey: push when the user is opted in, SMS where there is consent, email as the default, so a step sends one message, not three.
Journey priority and exit rules: which journey wins when a user qualifies for several, and an exit the moment someone converts, so onboarding never competes with a sale email.
Deliverability inside our email marketing service: authenticated sending domains, warm-up, engagement-based sending and sunset rules, the method in our email deliverability guide.
Embedded messages in your app or site, fed by the same journey logic, so the home screen reflects what email and push already said.
A campaign calendar by segment that sits beside your Iterable marketing automation, with send caps so a promotion never interrupts onboarding.
Iterable features we lean on
Journeys: multi-step flows that enter on events, branch on user fields and wait on behavior. We build fewer, deeper journeys with channel branches instead of one journey per channel.
Catalog: collections of product or content data that templates query at send time. It turns a generic email into a personal one, and it is the feature we most often find unconnected.
Embedded messaging: personalized content in app and web placements you control. Embedded campaigns on Iterable rose 294% year over year over Black Friday 2025 (Iterable Black Friday Insights, December 2025).
Push, SMS and in-app as branches of the same journeys. Over Black Friday 2025, SMS on Iterable rose nearly 60% and triggered campaigns 10% year over year (Iterable Black Friday Insights, December 2025).
Campaigns: blast and triggered sends for launches and promotions, kept outside lifecycle logic and capped so they never stack mid-journey.
Nova Agent: Iterable's conversational AI agent, which drafts and reviews templates, journeys and experiments and answers performance questions. We use it to speed up builds and analysis; every suggestion ships as a test.
Connect Catalog to your three highest-revenue templates first. It is the fastest gain in most Iterable accounts we audit, and every journey built after it inherits the data.
When Iterable is the right platform
Iterable wins when one journey has to span several channels and pull live catalog data, which is not every brand.
Platform | Best fit | Where it falls short |
|---|---|---|
Iterable | Email-led brands with an app or several product surfaces, where catalog data and journey branching drive personalization | Needs a clean user feed and Catalog upkeep; for app-first products where in-app is the main surface, Braze is the closer fit |
Braze | Mobile-first apps at scale, with real-time events driving push, in-app and Content Cards | Heavier implementation and quote-only pricing; more platform than an email-led brand usually needs |
Customer.io | Event-driven lifecycle for subscription apps and telehealth, run by teams with developers | Built around product events more than product catalogs, so merchandising inside messages takes more setup |
Klaviyo | Shopify ecommerce with email and SMS, order and catalog data native | Built around the store; less suited when an app and several channels carry the journey |
If you sell on Shopify and email and SMS carry the revenue, Klaviyo is the simpler choice. If your journeys span an app, a site and several channels and need live catalog data, Iterable is where we would build. For app-first products, compare our Braze agency and Customer.io agency pages.
Results
Results from our cross-channel programs
Every figure below is published on the linked case study and was read from the live page on 23 October 2026. James Michelle runs on Klaviyo and Centr on Braze.
James Michelle, email and SMS on Klaviyo: flow-driven email revenue up 202% and campaign email revenue up 126% year over year. SMS flow revenue rose 235%, and SMS campaign revenue rose 111% while campaign volume fell 3%.
Centr, fitness app and membership, on Braze: email, push and in-app messaging aligned into one lifecycle, with $1.9M+ in CRM-attributed revenue during the BFCM season alone, engagement 2.5x higher year over year in key sale periods, and a 20% lift in trial-to-paid conversions from improved onboarding flows.
The common thread: triggered, cross-channel messages carry more of the revenue, and sending more is not what gets you there.
Process
How we work in an Iterable account
Audit, week one: read-only access is enough. We map every journey and where they overlap, check which templates use Catalog and how fresh each collection is, read deliverability by sending domain and rank revenue per recipient by journey. You get the three biggest leaks with what each costs, and you keep the audit.
Scope: email journeys only, or email plus push, SMS and embedded. We list the user fields and catalog feeds each journey needs, flag the ones your team must add or clean, and you approve the order and the number before we change anything.
Build in revenue order: welcome and abandonment first, live in the first month, then post-purchase, replenishment and win-back, each tested against the version it replaced. Channel branches go in once email is earning, and every journey launches with a holdout group.
Report monthly: revenue per recipient by journey and channel, lift against holdout, deliverability signals, catalog freshness and sends per user per week, with the attribution window held constant, plus the next three changes we plan.
Who it's for
Who our Iterable agency works best with
Consumer brands with an app and a store, or several product lines, where email leads and push, SMS and in-app fill in around it. Teams already on Iterable who suspect they use a fraction of it, and brands moving onto Iterable who want Catalog and journey structure right from the first send. Global app installs rose 10% and sessions 7% in 2025 (Adjust Mobile App Trends 2026, February 2026), so more of the brands we talk to run app and email side by side.
We are a poor fit for single-channel senders and for brands with no product or content feed to personalize from. Request an Iterable audit to see where yours leak.
Frequently asked questions