Browser and Server Purchases Counted Once
The same purchase reached Meta from the server and from the browser. Meta marked the browser copy as Deduplicated, so each sale counts once.
- Server purchase processed
- Browser copy marked Deduplicated
Conversion tracking that counts each lead and purchase once. Your website sends every lead or purchase event through Google Tag Manager to Google Ads, Meta and other platforms, so you can check the numbers against your CRM or store.
The call is free. I explain my terms before you pay anything.
Without tracking, your ads spend money and nobody can see which clicks became leads, sales or purchases.
Google and Meta learn from the events you send them. No event signal means guessing.
See which ad, keyword or audience brought each lead, sale or purchase.
Find the searches that cost money but never create a lead, sale or purchase.
Each platform counts an event once, using one event plan.
Every click costs money from the first day. If events are not tracked from the start, the first weeks of spend teach the platform less, and that early data is hard to recover later.
Map every form, call, add to cart and purchase on your site. Find broken or duplicate events already in place.
Send each event with its full data: value, currency, items and order ID. Check every event in GTM Preview before it goes live.
Match test orders and leads with your CRM, booking or store data. Turn the ads on only after the numbers agree.
event: "purchase"
transaction_id: "ORD-10482"
value: 95.88
currency: "USD"
items: [
{
item_id: "SKU-1001",
item_name: "Example Product",
price: 95.88,
quantity: 1
}
]Sample data. Every purchase carries value, currency, items and an order ID, so the platform can match it to the ad.
Free 30-minute call: I will check which of these events work on your site right now.
Book a free 30-minute callPlatforms cannot see inside your business. They only see the events your tracking sends back, and they use them to find more people like the ones who took the action.
The click carries an ID such as gclid for Google or fbclid for Meta, so the platform knows which ad was clicked.
Check: the click ID stays in the landing page URL.
A lead, sale or purchase fires an event, and Tag Manager sends it to each platform.
Check: each event has its own name, value and currency.
The platform matches the click ID to the event, so it knows which keyword or audience produced it.
Check: the click ID is saved in the form or cart, so it reaches the event.
Smart bidding raises bids where events come in and lowers them where they do not. Clean signals make this faster.
Check: platform counts match your CRM or store, so bids follow real sales.
Real setups from client work. Each screenshot is cropped to show the proof, and personal and client details are hidden.
A visitor fills in your form. Here is where that event goes in each setup.
Tag Manager sits between your website and every marketing platform. One container holds all the tags, so a change does not need a developer each time.
A visitor submits a form, clicks a phone number, adds an item to cart or makes a purchase. The site pushes that action into the data layer.
Triggers decide which events matter. A form submit and a purchase each fire their own tag.
Tag Manager sends each event to your Stape server first. You decide which data leaves, and more real events reach the platforms.
The event goes on to Google Ads, Meta, TikTok, Snapchat, Pinterest and LinkedIn, each with its own conversion ID.
Google Ads, Meta, TikTok, Snapchat, Pinterest, LinkedIn and ChatGPT Ads each count leads and sales differently. I set up every platform from one event plan, so each lead and sale is counted once.
Leads, sales and purchases for search and Performance Max, plus offline events.
Events and funnels that track each step from visit to sale.
Leads and purchases sent with the Conversions API.
Lead, sign-up and purchase events sent with the Events API.
Sign-up and purchase events sent with the Conversions API.
Lead, sign-up and checkout events, sent from the browser and server.
Lead and purchase conversions for B2B, sent from the Insight Tag or Conversions API.
Conversion-optimised campaigns, with the OpenAI Pixel or Conversions API.
Many leads close on a phone call, in a showroom or in a CRM days later. Offline conversion tracking sends those final results back to Google Ads and Meta, so the ads learn from real sales, not just form fills.
Or send it through a GTM Server to the platforms.
Example arithmetic, not a client result. Assume each lead costs $20, so 100 leads cost $2,000.
80 leads never buy. At $20 each, that is $1,600 of the $2,000 spend, and the platform still sees it as success.
The platform now sees which keywords and audiences produce sales, so budget moves away from the 80 that did not buy.
Every step is tested before the next one starts, so each lead and sale is counted before your budget grows.
I list every action that matters: form submits, phone clicks, bookings, sign-ups, add to cart and purchases.
I set up the data layer, tags and events in Google Tag Manager, then send them to Google Ads, Meta and other platforms.
I send test events, confirm each one counts once, and check the value and match quality.
I compare platform numbers with your CRM, booking or store records, and fix the gaps I find.
Google Ads, Meta, TikTok, Snapchat, Pinterest, LinkedIn, ChatGPT Ads and GA4, plus your CRM or store. The method is the same on each.
Sometimes. A developer may help with the website side. I tell you what is needed on the call.
Yes. Phone clicks, form submits, bookings and purchases are all events, and each one can be sent to the right platforms.
Yes. Add to cart, checkout, purchase and order value are tracked the same way as leads, and the purchase value is sent to each platform.
No. Tracking shows what works, and ad platforms can only optimise on the events they receive. It makes every other change measurable.
Book a free 30-minute call. I will check which events each platform can see right now.
Four ways to reach me. Choose the one that fits what you need right now.