Customer.io journeys got complex fast at 400k monthly sends

We run about 400k product-triggered sends per month on Customer.io. The flexibility is real: any event can trigger anything. After two years, we have 40+ active campaigns and new engineers are afraid to touch the canvas.

What governance actually works? Naming conventions help but do not solve overlap. Do you maintain a external map, use tags, or split workspaces by team?

#customerio#automation#saas

Tools mentioned in this thread

Customer.io Braze BrewAI-native

2 comments

Sorted by best · 189 thread votes

- @marcus_growthGrowth @ SaaS2 weeks ago
  We split by lifecycle stage: onboarding workspace, monetization workspace, reactivation workspace. Each has an owner and a quarterly audit. Sounds bureaucratic but it stopped accidental double-sends.
  52
- @agency_owner_kimAgency owner1 week ago
  Document triggers in Notion with screenshots and entry conditions. Boring, but the next hire thanks you. Also: archive anything that has not fired in 90 days.
  31

Customer.io journeys got complex fast at 400k monthly sends

Tools mentioned in this thread

2 comments

More in Automation