DOCS · Getting started

Connect Evarist to your AI assistant

Evarist is a remote MCP connector. Add it to Claude or ChatGPT once, point it at your site, and ask your traffic anything — no dashboards, no exports. Setup takes about two minutes.

1 · Add the connector

Evarist runs as a remote MCP server — there's nothing to install. Pick your assistant:

Open Claude's connector settings

In Claude, go to SettingsConnectors, then choose Add custom connector.

Paste the Evarist server URL

Name it Evarist and enter the remote MCP server URL, then click Add:

https://app.evarist.ai/mcp
Once Evarist is listed in Claude's connector directory, you'll be able to add it in one click — no URL needed.
Custom connectors need a paid ChatGPT plan (Plus, Pro, Business, Enterprise or Edu) and ChatGPT's Developer Mode (beta). Read-only questions work everywhere; actions that write (like creating a site) confirm each time and are lighting up per plan tier.

Turn on Developer Mode

In ChatGPT, go to SettingsApps & ConnectorsAdvanced settings and enable Developer Mode.

Create a custom connector

Go to SettingsConnectorsCreate. Name it Evarist, add a short description, and paste the server URL:

https://app.evarist.ai/mcp

Trust and create

Tick the box to confirm you trust the connector, then click Create. ChatGPT sends you to Evarist to sign in.

Select it in your chat

In a chat, open +MoreDeveloper Mode and pick Evarist — do this once per conversation.

Then — whichever assistant you used

When you connect, your assistant sends you to Evarist. Enter your work email — we send a magic link (no password); click it to sign in. Then read and accept Evarist's Terms and Privacy Policy. Your assistant is now connected to Evarist.

2 · Set up your site

Evarist reads first-party behavioral analytics from your own site. Point it at your domain and add one line of tracking.

Ask Evarist to set you up

In a new chat, say: "Set up Evarist on my website." Your assistant runs the guided setup prompt.

Give your domain

Evarist registers your site and hands you a one-line tracking snippet.

Add the snippet to your site

Drop it in your page <head> or paste it into your tag manager (Google Tag Manager, etc.) — it's a single self-contained tag. Sessions begin flowing within minutes.

Start asking

Once data is flowing, ask Evarist anything about how visitors move through your site.

On Shopify, the Evarist app is coming to the Shopify App Store — once it's live, you'll install it from there and connect your store to Evarist with one click, no snippet to paste. Until then, keep using the tracking snippet above (paste it in your theme, or through your tag manager) — nothing to change yet.
Run the same brand on several domains (e.g. your .com and .fr)? Install this same snippet on every domain, then ask Evarist to "add my other domain" so a visitor who moves between them is recognised as one person.

Headless Shopify storefronts

Running Shopify behind a custom frontend instead of the Online Store (Hydrogen, or your own React/Next.js site)? A theme-embed toggle can't reach those pages, so set up tracking manually with the two steps below — this works today, independent of the Shopify app.

Install the snippet on every page

Paste the same tracking snippet from step 2 above into your storefront's root layout or template — every page, not just one — instead of relying on the theme embed.

If Shopify creates your orders

The common case, even with a custom frontend. Whenever you build or update the cart, set a Shopify cart custom attribute named _evarist to the value of the visitor's _evarist cookie, via the Storefront API's cartAttributesUpdate mutation:

mutation cartAttributesUpdate($cartId: ID!, $attributes: [AttributeInput!]!) {
  cartAttributesUpdate(cartId: $cartId, attributes: $attributes) {
    cart { id }
    userErrors { field message }
  }
}

# variables
{
  "cartId": "YOUR_CART_ID",
  "attributes": [{ "key": "_evarist", "value": "VALUE_OF_THE_EVARIST_COOKIE" }]
}

It rides through to the order, so Evarist attributes the purchase to the right visitor — no matter where checkout renders. This only carries the anonymous visitor id, never anything about the customer.

If checkout is on your own system

Install the snippet as in step 1, then tag your order-confirmation page as a conversion goal the same no-code way described below. Evarist tracks revenue natively from your own domain — no Shopify order required.

3 · What you can ask

Ask in plain language. Evarist does the analysis and answers — down to a single session.

Which pages are converting this week — and which are leaking?
Show me what hesitating visitors do right before they drop off.
Compare mobile vs. desktop conversion over the last 14 days.
What's my best traffic source by conversion rate?
How many people clicked "Add to cart" but never checked out?

4 · Track your own events and goals

Beyond pages and built-in conversions, you can turn any click into a named, tracked event — a button, a link, an add-to-cart — just by asking, or mark one as a goal to track a key outcome with optional revenue. You can also name key pages — your checkout, cart, or a product template — as funnel steps your assistant can analyze, or ask Evarist to watch section attention — how long visitors spend on a section like reviews, FAQ, or sizing — the same way. No code; page events work over your full pageview history from day one.

Tell Evarist what matters

Say "Track clicks on my Add to cart button." Evarist lists the buttons and links it can see on your site.

Preview before you commit

Evarist shows you exactly what the new event would match — live — so nothing goes in blind.

Confirm, and it's live

Approve it and tracking starts immediately. From then on you can ask about that event like any other signal.

Manage every event you've defined — rename, pause, or remove — from your site's page under Websites.
Evarist also watches your tags for you — if one stops firing (a button moves, a page changes), you'll see it flagged on your site's page under Websites and get an email alert.

Goals — tracked outcomes

A goal is a tagged event marked as an outcome — it fires a conversion whenever its click or URL trigger matches, and can carry an optional fixed revenue value. Goals show up in your data as conversions, distinct from behavioural signals. Ask Evarist to set one up ("Make my newsletter signup a goal" or "Create a goal for /thank-you page visits, worth €49"), or promote an existing event from your site's page under Websites. Keep one primary conversion — the outcome your headline numbers (conversion rate, "which traffic converts") count. The first goal you set becomes it automatically; change it anytime from your site's page or by asking. Tag the steps leading to that conversion (a "Book a demo" click, a pricing-page visit) as ordinary signals, not goals — so one conversion is counted once, not several times.

Dynamic per-order revenue (e.g. Shopify custom storefronts) — for cases where the revenue amount varies per conversion and isn't set at rule-creation time, call the tracker directly from your own code: evarist('goal', 'purchase', { value: 49.90 }). The value is in major units (e.g. 49.90 = €49.90). This fires the same CONVERSION event and respects the per-session dedup.

5 · The tools

Evarist exposes a small, read-first set of tools. Seven ever write — create_site sets up a new site, setup_shopify points you at the native Shopify app (App Store listing coming soon), confirm_event_tag saves an event you've approved, set_event_goal promotes or demotes an event as a conversion goal, set_identity_capture switches form-email capture on or off, add_domain adds one of your domains to a website for cross-domain visitor recognition, and remove_domain removes one. Everything else is read-only.

list_sitesReadThe sites connected to your account.
describe_dataReadExplains what your traffic data covers, so answers stay accurate.
execute_queryReadAnswers questions about your traffic.
list_taggable_eventsReadThe buttons, links, and key pages on your site you can turn into tracked signals or goals.
propose_event_tagReadPreviews what a new event or goal would match, live, before you create it.
confirm_event_tagWriteSaves an event you've approved; tracking starts immediately.
set_event_goalWritePromotes a tagged event to a conversion goal (or demotes it back to a signal), with optional fixed revenue.
list_productsReadLists your Shopify store's products with live stock; filter by in-stock or product type.
revenue_summaryReadYour real, refund-corrected revenue by channel — the accurate counterpart to the pixel numbers.
campaign_performanceReadWhich campaigns actually earned their spend — ad cost matched against your own first-party revenue.
create_siteWriteSets Evarist up on a new website and issues the tracking snippet.
setup_shopifyWritePoints you at the native Evarist Shopify app for a site — installable from the Shopify App Store once it's live; until then, tells you to keep using your existing snippet or tag manager.
add_domainWriteAdds one of your domains to a website so a visitor who moves between them is recognised as one person. Current domains show up in list_sites.
remove_domainWriteRemoves a domain from a website — the one write that takes a domain away rather than adding.
set_identity_captureWriteSwitches on (or off) capturing the email a visitor submits on one of your forms, so their submissions tie to their behaviour. Off by default.
manage_teamReadPoints you to your team and access settings.

6 · Your data

Evarist reads behavioral analytics only — pages, clicks, and conversions. It never reads names, emails, or phone numbers; that data lives in a separate system Evarist can't see.

Need a hand?

Email us at support@evarist.ai and we'll help you get connected.