Verifying your install

Installed means one thing here: a real click reached us from your site.

A tag can be on the page and still fail. An ad blocker can stop it. It can carry the wrong id. It can sit on a domain we refuse. A page scanner calls all three "installed", and your first real sale goes untracked. A click that arrives proves the whole loop, so a click is what we wait for.

The live verifier

On Getting started, the tag step listens for a click:

If someone else runs your site

Plenty of founders don't touch their site's code.

1. Under the tag, type your developer's email address.
2. Press Email it.
3. They get one email with the tag and where it goes. Replies come to you.

We send nothing else to that address. You don't need anything back from them. Once the tag is live, come back and click your own partner link. The verifier works the same whoever pasted the tag.

To send it again, open Settings, Connections. The same box sits beside the tag, with room for a note.

Or let your coding agent do it

Is your site's code open in Claude Code, Cursor, VS Code or Codex? Your agent can add the tag.

1. Connect it over MCP.
2. It reads get_install_instructions for your exact tag and where it goes.
3. It writes the tag into your code.
4. It checks the live page with check_install.

You still click your own partner link at the end. That real visit finishes the step.

How the verifier decides

It checks every two seconds for two minutes. It turns green the moment the click lands.

Green stays green. The checklist, the dashboard's empty states and the verifier all read the same fact, and it never flips back.

Some clicks never count: the ones the install check makes, and anything in the sample data. Only a click from a real page view turns it green.

When nothing arrives

After two minutes the verifier stops and tells you what it can see.

This browser blocked our script. The verifier asks for the script from the browser you're testing with, and an ad blocker or privacy shield can cancel that request. Then your own test click never fired. It's the commonest reason a working install looks broken to the person who set it up.

• Pause the blocker while you test, or use your phone.
• Visitors without a blocker are tracked either way.
• A tracker domain of your own gets past ad blockers for everyone.

A click came from the wrong address. The script only reports from your registered website and its subdomains. We refuse a click from a local preview or an unrelated staging domain before we write anything, and the verifier shows you the refused address so you can see the mismatch.

• Test from a page on your real site.
• Or, if your website has moved, change it under Settings, Program.

Nothing reached us. Usually the tag isn't on the page. The install check on the same card settles it. It fetches your page and looks for the tag with your program id. Then it spells out the fix beside whatever it finds.

Your website address goes to a sign-in page. The check follows the address on your program, so if that address lands on a login screen, a login screen is what we read. No tag can live there, and a partner link pointing at it drops your visitors on a sign-in box instead of your product. This catches people out most with a private workspace address from a builder like Firebase Studio or Replit: you can open it because you're signed in, and nobody else can.

• Publish your site, then change the website to that public address under Settings, Program.
• Run the check again.
• Not launched yet? Leave it. The tag is the only step that needs a live site.

If you install through a tag manager

Google Tag Manager, Segment and Tealium add the tag after the page loads. So the check can't see it in your page. It looks at your real traffic instead.

1. Publish the container, with our tag as a custom HTML tag on every page.
2. Open your site through your own partner link.
3. Run the check again. The tag line reads yes, from your traffic.

The same works when your site's bot protection blocks our check. One case never passes: a tag carrying another program's id. Fix the id and check again.

The support question this answers

"Why wasn't my sale tracked?" usually means the click before the sale never got recorded.

A green verifier rules out that whole half. The script loads, it reports to us, and we accept clicks from your site. What's left is attribution and your payment processor. That's what Attribution health is for.