One agent at scale: the setup, step by step
For the marketplace or retailer with millions of profiles: the events to bring in, the identity rule, the order in which journeys and messages move, and the volumes to watch.
- What to prepare before day one
- What goes live, in order
- What to measure in week one and week four
Open the setup checklist
Enter your work email and the checklist opens on this page. We also send you the link, so you can come back to it.
Thanks. The checklist is open below.
We use your email to know who reads our research. Privacy policy
What to prepare
An inventory of events and sources
Every event type from the site tag, the app SDK and your own systems by API. The marketplace in the use case sends hundreds of its own event types.
The identity rule
How an anonymous visitor joins the profile when they sign in on another device, and which identifiers count. Write it down before the first event arrives.
Consent and channels per country
Who may receive email, push, SMS, Viber or WhatsApp, in each market. Sending domains and sender names per country and language.
The migration order
Profiles first, then journeys from the highest-volume down, then messages, then on-site decisions. One cycle of each old and new side by side.
What goes live, in order
Bring the events in
Site tag, app SDK and API in parallel. Compare events per day with the old tools for a week before anything depends on them.
Join the profiles
Anonymous visitors included, joined on sign-in. Check duplicates: one person on web and app must be one profile.
Import subscribers and consent
Per channel and per country, with the opt-in date. Nothing is sent before this is checked.
Move journeys one by one
Start with the largest. Run old and new for one cycle, compare entries and deliveries, then switch the old one off. Never both for longer.
Send from the same profile
Email, push, SMS, Viber and WhatsApp chosen per person toward the goal you set, with frequency caps across channels.
Move on-site decisions last
Recommendations and banners from the same profile, with a holdout from day one.
What to look at, and when
| When | What to look at | What good looks like |
|---|---|---|
| Week 1 | Events per day against the old tools, profiles created, matches on sign-in, duplicate profiles | Event counts match within the agreed tolerance; one profile per shopper on web and app |
| Week 4 | Journeys entered per day, messages delivered per channel and country, bounces and unsubscribes | Volumes in line with the use case's order of magnitude for your base; no double sends from old and new tools |
| Month 3 | The goal metric per journey against its holdout, and the number of tools still holding a copy of the shopper | One copy of each shopper, and a measured lift per journey |
Common mistakes
Migrating every journey at once. One journey per cycle keeps the comparison honest and the inbox calm.
Keeping the old tool sending after the switch. Two tools, two messages, one angry shopper. Switch the old journey off the day the new one is confirmed.
No frequency caps across channels. At millions of profiles a missing cap is millions of extra messages in a day.
Treating anonymous events as noise. Most of a marketplace's intent is anonymous; it joins the profile at sign-in only if it was kept.
See which of last week's visitors you missed
Thirty minutes, with your store and ad accounts open. Then 30 days free. A holdout group decides: if the agent doesn't add orders in 30 days, you don't pay.
Book 30 minutes
You'll talk to one of us.