Quickstart
Four steps. Two of them are a single toggle each. The setup wizard in your Shopify admin walks the same path — this page is the version you can read ahead of time, or fall back to when a step does not behave.
Install the app
Install Click Context from the Shopify App Store. It opens inside your Shopify admin under Apps. The Free plan needs no card and covers 5,000 sessions a month, which is enough to see whether the data tells you anything useful.
Turn on storefront tracking
Click Context collects behaviour through a theme app embed. It is one toggle in the theme editor — no code, no theme file changes.
The wizard gives you a button that opens your published theme with Click Context Tracker already switched on. Review the preview and press Save. To do it by hand:
- Shopify admin, Online Store → Themes.
- Press Customize on your published theme — the one customers see.
- Open the App embeds tab in the left sidebar (the puzzle-piece icon).
- Switch on Click Context Tracker.
- Press Save.
Running a theme A/B test?
Enable the embed in both themes. A test theme without it records no sessions at all, which reads as a traffic drop rather than a tracking gap.
Connect your AI assistant
Three different mechanisms, so pick the page that matches your tool:
- Claude — web or desktop. Paste a URL into Add custom connector, then enter a six-digit code.
- ChatGPT — developer mode, a different URL, then the same six-digit code. Needs a paid ChatGPT plan.
- Cursor, Claude Code, VS Code, Windsurf — an API key in an
mcp.json-style config.
Ask your first question
Do not start with a tool name. Start with the question you actually have:
Give me a CRO audit of the last 30 days.Where is my single biggest leak, and what does it cost per day?Is one device silently broken?A good answer names a number in your reporting currency, shows the arithmetic, states its confidence, and tells you which selector or page to change. If you get a tidy list of observations with no money attached, see Getting good answers.
When you will have data worth reading
Events start arriving within seconds of the embed going live. Useful analysis takes longer, because most of it is rate comparisons and rates need a denominator.
- Immediately— page views, clicks, DOM snapshots, JavaScript errors. Enough to answer “what is on this page and what do people click”.
- Next morning — the first nightly rollup runs at roughly 00:00 UTC. Funnels, anomalies, session scores, correlations and opportunity sizing only exist after it has run.
- Two to four weeks — enough sessions for conversion-rate comparisons to clear the sample gates. Below roughly 200 sessions and 10 conversions per arm, the server tells your assistant to present a difference as a signal to watch rather than a finding.
An empty answer on day one is normal
Funnel analysis over today returns zeros, because the rollup has not run yet. That is not broken tracking — see Data freshness for the two watermarks and how to read them.
Checking the connection actually works
The only real proof is a request arriving from your assistant. The wizard's final step watches for one while you are on it, and the dashboard shows when your assistant last reached the store. A stored credential is not proof — a key can exist and never be used.
If your assistant reports that it cannot see the server, work through Troubleshooting. The most common cause is the wrong URL for the client: Claude and everything else use different endpoints.