Send shoppers to Iterable

Included on the Growth plan and above.

What you're charged

Before we charge, we check whether the shopper is already in your Iterable. New shoppers cost 2 credits, once; shoppers already there cost 1 credit, are never duplicated, and get a WhoLayer Returning Shopper event instead.

What Iterable supports

• Checks your list first: yes.
• Refunds bounces: yes, bounces and spam complaints within 30 days.
• Deliverability Guard: a fixed cap of 50 new contacts a day (or your own setting, if lower), because we can't read your rates.
• Holdout report: yes, from your orders.

Connect it

1. In Iterable, open Integrations → API keys and create a Server-side key in the project your store uses.
2. In WhoLayer, open Destinations, choose Iterable, paste the key, and pick the data center (US or EU) your project is in.
3. Click Send test, then look for the user "avery.sample@example.com".
4. Build a journey triggered by the WhoLayer Shopper Identified or WhoLayer Returning Shopper custom event. Iterable adds new users in the background, so in some projects the very first event can arrive before the user exists; the user also gets a wl_shopper_identified_at field you can trigger on as a backup.

Good to know

• Iterable has no account-wide 7-day bounce and complaint counts, so the Deliverability Guard uses a fixed daily cap.
• Opted-out people are never sent, and opt-outs take effect immediately.
• We encrypt your key when you save it and only ever show its last characters.