For AI agents: a documentation index is available at /docs/llms.txt. Append .md to any page URL for markdown, or send Accept: text/markdown.
Data Assistant user solutions
Data Assistant reviews your taxonomy and fixes many issues for you. A few problems sit outside what it can do. It can't spot them, and it can't apply the fix. These guides cover those cases. They're written for people who want to solve a problem, not read about a product.
Every guide starts with the part you can do yourself, without code. You confirm the problem is real and capture the exact facts. From there, the path splits. Some problems are yours to finish. Others come down to how your product sends data, so the fix belongs to an engineer. Each guide is clear about which situation you're in. When code is the answer, you get a short message you can copy and send to whoever owns your tracking, plus a path to follow if you have no engineering help at all.
When another Amplitude product or a higher plan solves the problem more easily, the guide says so. Reach for these guides when you already suspect an issue, or when you run a scheduled data-quality review. For problems Data Assistant already surfaces, use Data Assistant instead.
Some solutions require engineering access
You may need engineering resources as some of these solutions require changes to your backend code. Always start with confirming the problem. If you don't need engineering changes, the confirmation page also carries the no-code solution. If the solution does require code changes, move on to the engineering solution page.
Choose a user solution
| Use case | Confirm the problem | Code fix |
|---|---|---|
| Missing User IDs after sign-in | Confirm the problem | Engineering solution |
| User IDs set too early | Confirm the problem | Engineering solution |
| Anonymous activity lost at login | Confirm the problem | Engineering solution |
| One person with many User IDs | Confirm the problem | Engineering solution |
| Profiles that don't join across devices | Confirm the problem | Engineering solution |
| Planned events that never arrived | Confirm the problem | Remove the plan entry |
| Failures you can't see | Confirm the problem | Engineering solution |
| No activation event | Choose an activation event | Often none. Instrument it only if no event fits |
| Missing or mistimed experiment exposure | Confirm the problem | Engineering solution |
| No account-level analysis | Decide whether you need groups | Only if you need groups. Set them up |
| Missing shared context | Confirm the problem | Engineering solution |
| Event vs user property confusion | Confirm the problem | Engineering solution |
Missing insert_id or session_id | Confirm the problem | Engineering solution |
Was this helpful?