Growth Base

Iterable

Iterable data journeys: a practical setup guide

By Dinesh Varma / / 9 min read

Iterable is a powerful cross channel platform, but most accounts use a fraction of it. A welcome email, a cart reminder and a weekly newsletter is common. The journeys that really move revenue, the ones triggered by behaviour and personalised by product, depend on data that was never set up properly.

This guide covers the data base to build first, then the journeys to put on top of it.

1. Get identity right

Iterable identifies users by email, by a user ID, or both, depending on how your project is configured. Decide this up front, because changing it later is painful.

  • Apps and logged in products usually key on a stable user ID, with email as an attribute.
  • Ecommerce often keys on email, with care for guest checkouts and people who change address.
  • Plan for anonymous activity. Browse behaviour before sign in is valuable. Decide how it will be merged once the person is known.

2. Design an event taxonomy before you send a single event

Journeys trigger on events. A short, consistent list beats a long, messy one. Start with:

EventKey fieldsUsed for
Product viewedproduct ID, category, priceBrowse abandonment, interests
Cart updateditems, cart valueCart abandonment
Purchaseorder ID, items, total, discountPost purchase, revenue reporting
Subscription changedplan, status, renewal dateUpgrade, save and win back
Signed up / logged insource, methodOnboarding, activation

Use the same names across web, app and backend, and send purchases from the server where you can, so they are never lost to a closed browser tab.

3. Connect the catalog

Iterable's catalog holds product or content data that messages can reference. With the catalog connected, an event only needs a product ID, and the message pulls in the name, image, price and stock. Keep it fresh from your store or product feed, and include the fields you will filter on, such as category, margin band and in stock.

4. Bring in the data that lives elsewhere

Lifetime value, predicted churn, loyalty tier and B2B account data often live in a data warehouse or another system. Sync the fields journeys need into Iterable user profiles on a schedule, through a warehouse connector or reverse ETL tool, rather than trying to recompute them inside Iterable.

5. The six journeys to build first

  1. Welcome and onboarding. Triggered on sign up. Personalised to what the person browsed or signed up for.
  2. Browse abandonment. Triggered on product viewed with no cart. Short, helpful, catalog driven.
  3. Cart abandonment. Triggered on cart updated with no purchase. Push or email first, SMS for high value carts.
  4. Post purchase. Order confirmation, usage tips, review request and a timed cross sell.
  5. Replenishment or renewal. Timed to when the product runs out or the plan renews.
  6. Win back. Triggered on inactivity or churn risk, with an offer only for customers worth saving.

Build each journey with exit rules. A customer who buys should leave the cart journey straight away, on every channel.

6. Choose channels per person, not per campaign

Iterable can send email, SMS, push, in app and web messages from one journey. Use branching so app users get push first, high value carts get SMS, and everyone respects frequency limits. Over sending is the fastest way to lose a channel.

7. Feed the ad platforms from the same data

Sync Iterable segments to Google Ads and Meta: suppress recent buyers from acquisition, retarget high intent browsers, and build lookalikes from your highest value customers. Paid media and journeys then work from the same customer truth, instead of fighting each other. See how we connect Iterable to Google Ads and Meta.

8. Measure with holdouts

Open and click rates tell you about the message, not the money. Keep a small control group on your key journeys and compare revenue per user between those who received the journey and those who did not. That is the number to report, and the number that tells you where to invest next.

A simple 30 day plan

  • Week 1: identity decision, event taxonomy and tracking plan.
  • Week 2: events and catalog live, tested against real orders.
  • Week 3: welcome, cart and post purchase journeys live, with holdouts.
  • Week 4: browse, replenishment and win back, plus ad audience sync.

If you are on Iterable already and want to know what is missing, our free audit reviews your data, events and journeys. Learn more about our work as an Iterable agency.

Want us to check your setup?

Free 30 minute audit. We review your data, integrations and journeys, and show you the fastest revenue win.

Contact us now