01 · Setup
It reads your site before you install anything.
You type the address of your website. Tagbreeze opens its public pages and works out what it is looking at: the platform (WordPress, WooCommerce, Shopify, Wix, Webflow and others, or a custom build), the pixels already installed, the forms, the cart, the phone and WhatsApp links, and whether a consent banner is present.
From that it writes a tracking plan: the list of things worth measuring on this particular site. You can untick anything, and add a rule for a conversion the tag cannot guess, such as "anyone who reaches /thank-you is a lead".
Nothing is changed on your site at this stage. The analysis takes a few seconds.
02 · Install
One tag, four ways to place it.
There is one tag for the whole site. It recognises the platform it runs on and listens for the events of your plan.
| Your site | What you do |
|---|---|
| WordPress or WooCommerce | Upload one plugin and activate it. It already carries your site's key, and sends exact order values. |
| Shopify | Paste one line in the theme, and one custom pixel for the checkout. |
| A site with Google Tag Manager | Sign in with Google and pick the container. Tagbreeze adds its tag and publishes it, after you confirm. |
| Anything else | Paste one line in the <head>. |
If someone else looks after the website, the Install screen gives you a ready message to forward, with the exact steps.
Some sites carry a strict security policy that blocks every outside script. On WordPress, the plugin can serve the tag from the site's own domain, which that policy already allows. Elsewhere, Tagbreeze detects the block and writes the note for the person who manages the server. The article A Content-Security-Policy can block your tag explains what is going on.
03 · Measure
What it records.
| Event | When it fires |
|---|---|
page_view | Every page load, and every navigation inside a single-page app. |
view_item | A product page, read from the page's own product data. |
add_to_cart | Cart requests and add-to-cart buttons. |
begin_checkout | The checkout page, with the cart's value and items where the platform provides them. |
purchase | The order confirmation, with order number, value and currency. The same order is never counted twice. |
generate_lead | A contact, quote or booking form that was sent successfully. |
contact | A click on a phone number, an e-mail address or a WhatsApp link. |
sign_up, search | Account creation forms and site searches. |
The Overview screen shows events as they arrive, a few seconds after they happen. If a site stops sending events for a day, its owner gets an e-mail with the usual causes.
04 · Deliver
Each conversion is sent twice, counted once.
You connect your ad accounts in one click: sign in, pick the dataset or the property, done. No account yet? Each connection comes with a guide, and Tagbreeze can create a Google Analytics property, a Tag Manager container or a Meta dataset for you, in your own account, after you confirm.
From then on each conversion leaves by two roads:
- From the browser, to Meta, Google Analytics 4, Google Ads and TikTok, the way their own pixels would.
- From our servers, to Meta (Conversions API) and TikTok (Events API), with the same event ID, so the platform keeps one copy.
The second road does not depend on the visitor’s browser. It exists for Meta and TikTok; Google Analytics 4 and Google Ads receive their events from the browser. What is server-side tracking? explains what it recovers and what it does not.
E-mail addresses and phone numbers typed at checkout are hashed on the visitor's device before anything is sent. Tagbreeze never receives the readable value.
05 · Consent
It waits when the law says wait.
In the European Economic Area, the United Kingdom and Switzerland, the tag waits for the visitor's choice before it sets an identifier or loads an advertising pixel. It reads that choice from Google Consent Mode, from the IAB TCF signal, or from the common consent tools. If your site has no banner, it can show a simple one of its own.
Before consent, or when it is refused, only cookieless counts reach Tagbreeze, and nothing is forwarded to an ad platform. Server-side delivery follows the same rule: the server does not go around a refusal.
You can switch the waiting off. You are then responsible for collecting consent another way where the law requires it. More in Consent and conversion tracking.
06 · Attribute
Which campaign each sale came from.
With consent, the tag remembers how each visitor arrived: the campaign parameters of the link, whether they clicked a Meta, Google, TikTok or Bing ad, or the website that referred them. It keeps the first visit and the latest one. Every purchase and every lead is stored with both.
You then choose the ad account that pays for the site's ads. Tagbreeze reads, per day and per ad, the spend and the conversions the platform itself reports. It is read-only: no campaign is changed.
The Ads screen puts the two side by side:
- purchases, leads and revenue the tag recorded, per channel, campaign and ad;
- spend, return on ad spend (ROAS) and cost per result;
- what the platform claims for the same days, in its own column, never mixed with the rest;
- credit to the first touch or to the last one, at the press of a button.
A sale lands on its campaign when the ad's link carries the campaign ID. The screen gives the exact parameters to paste once in Meta, Google Ads and TikTok. Without them, the sale is still credited to the right channel. See UTM parameters that map to campaigns and First touch or last touch.
Reading ad spend works today with Meta. For Google Ads it is built and waiting for Google's review of that use.
07 · Customers
What a customer is worth, by where they came from.
Tagbreeze links the purchases of the same customer, using a one-way reference made from their browser or their hashed e-mail address. It then groups customers by what first brought them and by the month they arrived.
For each group you see the number of customers, their orders, their revenue, the value per customer and the share who bought again. That is how you learn that a channel which looks expensive on the first order pays back on the third. Customer lifetime value by channel shows how to read it.
Orders from visitors who did not consent are counted in revenue and left out of this view, and the screen says how many.
08 · Agencies
Ten sites on one screen.
The home screen lists every site of the account with its health, its events, its purchases and leads, its revenue, its ad spend and its ROAS, over 7, 30 or 90 days.
Each site has a share link: a read-only report you send to a client. It opens without an account, shows that one site's results, and nothing else. A new link replaces the old one, and you can withdraw it at any time.
09 · Connect
An API, and a door for assistants.
A key created in the console gives read access to your reports from your own tools: sites, attribution report, customer value and latest conversions. The API documentation lists the four endpoints.
The same data is served to assistants through a Model Context Protocol (MCP) server. Connect it to Claude and ask in plain words which campaign had the best return last month. Both are read-only: a key cannot change anything.
10 · Limits
What it does not do.
Better to say it here than to let you find out later.
- It does not track phone calls, and it does not send SMS or e-mail campaigns.
- It does not link a person across devices by fingerprinting. A customer is recognised by their browser or by the e-mail address they type, with consent.
- It does not create, edit or pause your campaigns. It reads their numbers.
- It does not sync with a CRM yet.
- It cannot bring back a conversion a visitor refused to share.
Go deeper, one subject at a time.
Questions
Before you ask.
Do I need a developer?
No for WordPress, WooCommerce, Shopify and sites with Google Tag Manager. On other sites one line has to be pasted in the page head; the Install screen writes the message for whoever does it.
Does Tagbreeze replace my pixels?
It can load them for you, or work beside pixels already on the site. When it finds an existing pixel with the same ID it leaves the browser side to it, so nothing is counted twice.
Does server-side delivery ignore consent?
No. When a visitor refuses, nothing is forwarded to an ad platform, from the browser or from the server.
Can I see which ad brought a sale?
Yes, when the link of the ad carries the campaign and ad identifiers. The Ads screen gives the parameters to paste once per platform.
Know what your ads really bring in.
It takes a few minutes. Nothing is changed on your site until you install the tag.
Add your site