Skip to content

Part 3 · Operate

Website analytics setup

Put the script on your site, decide what it may keep, and choose what goes back to your ad platforms.

01What it is

The setup screen for website analytics, one section at a time: install, consent, capture pages, server events, scoring, activation, your own Stripe, ad platforms, retention, privacy requests, joined visitors and the raw event list. Where conversion accuracy is available, Conversions and Test a conversion join them. It appears once website analytics is switched on for the venture.

02Why it exists

Analytics is only as good as its install and only as safe as its rules. A script that a content blocker stops counts nobody, and a script that keeps an id without consent is a liability on every page it runs on. So the install comes first and offers the path through your own domain, consent comes second, and everything that sends data anywhere else waits behind both.

Ad platforms optimise for whatever you tell them happened. Told about clicks, they find more people who click. Told when a visit became a qualified conversation or a won deal, they find more people who buy. That is the only reason sends exist, and they carry only what a person agreed to: a marketing yes from their own browser, never with Global Privacy Control, identifiers hashed before they leave.

A person can ask what you hold about them, or ask you to delete it. Both are one field and one button here, and the delete leaves an audit entry that records it happened without saying who.

03How to use it

  1. 01Open Install, add your domain, and choose how the script is installed. Through your own site is the one content blockers miss. Paste the steps shown, then check the last five minutes.
  2. 02Open Consent and choose when the script may keep an id. Use Ask first wherever visitors must opt in.
  3. 03Open Ad platforms, pick the deal stages to send, switch a platform on, and fill in its ids. A blocked platform lists exactly what it still needs.
  4. 04Open Privacy requests to export or delete one person by email or anonymous id. Delete asks you to type a word first.
  5. 05Open Events to see every stored event, newest first, filtered by name, page, person or date.
  6. 06With conversion accuracy available, open Conversions to turn it on and define each conversion once, then Test a conversion to follow one from your site to each platform (see Conversion accuracy).

04What good looks like

You give it
A deal moves to Qualified for a person whose browser said yes to marketing cookies on your site, with Meta switched on and its dataset id filled in.
You get
Meta receives one conversion for that deal and stage, with the email hashed, and Recent sends shows Sent. Moving the deal back and forward again sends nothing new.
Why
Each send carries the deal and the stage as its id, which Meta de-duplicates on, and the log refuses to send a stage it already sent.

Derived from the rules in the code

05What weak looks like, and what it costs

You give it
A deal reaches Won for a person who never visited your site with the script on.
You get
Nothing is sent to any platform. Recent sends shows No consent for each one you switched on.
Why
Without a marketing yes recorded from the person’s own browser, no identifier leaves. A platform that never hears about the deal is the correct outcome.

Derived from the rules in the code

06Read next