Get started
For agents
How an AI agent sets nextanalytica up for its user, what only the user can do and the rules it follows.
Updated
This page is written for an AI agent setting nextanalytica up for its user. If you're a person, you don't need to read on: paste the prompt below into your agent, and it stops to ask you whenever a step is yours.
The prompt
Set up nextanalytica for my website. Follow https://nextanalytica.app/setup.md: ask me what you need first, then connect, add the site, add the tag, check it works, and tell me what you changed.What can only the user do?
Only the user can do these. Tell them how in one line, then wait:
- Sign in, and make the account by signing in the first time.
- Add the project in the dashboard, if it isn't there.
- Approve every change to the site's code before it's committed or deployed.
- Paste API keys and sign in to sources. Never ask for a key, a password or a card number in the chat.
- Agree to a memory you want to save, and to which events count as conversions.
What does the agent do?
- Ask, in one message, which site, where its data is kept, whether it asks visitors for consent and whether people sign in.
- Connect to
https://mcp.nextanalytica.app/mcpif the nextanalytica tools aren't there yet. - Call
list_projects; if the site is missing, the user adds it, then call it again. - Call
get_tagand put the line in the site's shared layout. Show the change and ask before committing. - After the deploy, ask the user to open the site once, then call
get_tagagain: the domain turns live within about a minute. - Report what changed and the next three things worth doing.
The full playbook, step by step, is setup.md.
What rules does the agent follow?
If you only remember one: never invent a number.
- Always call
get_contextfor a project before answering about it, anddescribe_databefore asking for numbers. - Always take the tag line from
get_tag. Never write one from memory: it carries the project's own key. - Never invent a number. When the data can't answer, say so and say what would.
- Never change a website through nextanalytica: its tools don't. Change code only in the user's repository, with their approval, or through a connector the team added.
- Read the Changelog before saying something can't be done.
Check your work
list_projectsshows the site.get_tagsays the domain is live.get_liveshows the user's own visit after they open the site.