For AJO Practitioners
Root-cause help for the people who run AJO day to day, and training for those learning it.
The problems I fix before they become incidents.
If you've spent hours in Experience League threads or waiting on a support ticket, you know what it costs to be stuck.
Your journey is live. No one's entering.
The entry condition looks right. The audience evaluated. The trigger fired. But the journey entry count is sitting at zero — and you can't tell if it's the segment, the entry rule, or something upstream in the data layer.
Sends look wrong and nothing explains why.
The campaign ran. The numbers don't add up. Capping rules, frequency constraints, suppression lists — something is silently blocking delivery and the execution logs aren't giving you a clear answer.
Personalization broke in a live send.
Dataset lookup returned null. A profile attribute didn't resolve. Or worse — a fallback value went out to your entire list because the XDM field wasn't mapped correctly and nobody caught it in QA.
You don't know which use cases to build next.
The platform can do far more than you're using, and nobody has ranked what's worth the effort.
These aren't edge cases. They're the most common AJO production failures.
Pay after approval. Fit check in 24h. Full refund if I can't deliver.
Not sure what you need? Take the free 30-minute intro call (one per email) and work out whether the audit fits.
The AJO Pre-Launch QA Checklist
26 checks across schema, audience evaluation, identity, capping, and personalization: a practical pre-launch checklist for AJO journeys.
- Schema & Data Layer
- Audience & Entry Logic
- Identity & Profile Resolution
- + 6 more categories