Agent traces need to join behavioral analysis without changing what an event means.
Product managers need one customer journey, while the compute layer must preserve trustworthy event semantics.
Who you’d be doing this for
“My onboarding funnel stops right where the agent takes over, and leadership keeps asking what happened next.”
Selorm Boateng · Product Manager
Owns adoption and retention decisions for an AI-assisted product flow tracked in behavioral analytics.
What is at stake
Product managers cannot see agent-led steps in the same funnel as customer actions. You have to weigh a useful first surface against durable query semantics and reliable results.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- one customer journey vs stable event semantics
- flexible trace data vs durable contracts
- new analysis depth vs Nova query latency
- fast product access vs shared-layer correctness
Why Amplitude
Nova and the compute API sit beneath the funnels and retention views where product managers expect AI-agent activity to appear alongside product behavior.
Written with these in mind
Not your kind of problem? 18 more at Amplitude, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.