SAMA's tracking looks live — tags load, the pixel is present, conversions are configured. But the revenue behind them is wrong or missing at every step that matters. We ran the audit on the live site: a real configured ring in the cart, a real sale in GA4, the real booking flow opened. Six issues, and one of them feeds most of the others.
/ Prepared by Amplio Data for SAMA · via 94N Digital · 8 Jul 2026 · use → to advance
/ 01 — How we checked
Built an 18K setting with a lab diamond and captured the exact dataLayer push GTM receives at add to cart.
Pulled the Transactions and Purchase Journey reports against a genuine Stripe order to see what revenue actually landed.
GA4 DebugView, Tag Assistant and Meta Pixel Helper, plus the raw network beacons leaving the browser.
Clicked through to the consultation scheduler and inspected the page it actually loads.
Confirmed live · GTM-KCZWKSZJ · GA4 G-M5NL92X1C9 · Google Ads AW-17580057414 · Meta Pixel 803724729439271
/ 02 — What we found
| Issue | Severity | What it breaks | Owner |
|---|---|---|---|
| Cart value excludes the diamond | Critical | Every revenue number downstream | Developer |
| Purchase revenue never set | Critical | GA4 revenue · Ads value bidding · ProfitMetrics | Developer |
| Product name hard set to "Ring Product" | High | Dynamic remarketing · product reporting | Developer |
| Meta pixel fires outside GTM | High | Event trust · duplication risk | Amplio + Dev |
| Booking conversion can't fire | High | Every appointment conversion | Amplio + Dev |
| Consent Mode not wired | Medium | All Google & Meta signal in the EU/UK | Amplio |
/ 03 — The root cause
/ 04 — Why it matters
In the last 28 days GA4 recorded one purchase — a genuine Stripe order — at $0.00 revenue, while $225 of item revenue floats separately with no order to attach it to. The top level value field the platforms read is never populated.
GA4 sees the order but no order value, so revenue reporting shows nothing on a real sale.
Value based bidding has no reliable revenue to steer by, so it spends against a signal that isn't there.
SAMA's chosen profit tool reads the same broken value. Its profit and ROAS inherit the error.
The Ads and ProfitMetrics value tags still read the old Universal Analytics path — so even a correct sale wouldn't reach them.
/ 05 — Meta pixel
First find the hardcoded fbq call in the site, map what already fires, then migrate into GTM and remove the manual code
/ 06 — Consultation bookings
The "Book Consultation" trigger listens for a click on a button on the SAMA page. But when we opened the real flow, the calendar is a HubSpot Meetings scheduler loaded inside an iframe from meetings.hubspot.com. We confirmed it live: that button isn't in SAMA's page at all — it lives inside the iframe, and the browser blocks the page from ever seeing clicks in there.
A separate iframe is sealed off by the browser by design, so the Google Ads appointment conversion and the Meta cta_click event almost certainly never fire from a genuine booking.
The current tier exposes no completion webhook or redirect, so a generic button selector was the only workaround available — and it reaches nothing.
HubSpot's embed emits a meetingBookedSuccessfully message. A postMessage listener on the page can catch it and push a real conversion — no paid upgrade required.
/ 07 — Consent signal
Google Ads beacons are leaving the browser flagged non personalised — ad consent treated as denied. The four Consent Mode v2 signals are registered in the container but carry no default and no update, so the handshake Google expects isn't actually happening, and the HubSpot cookie banner isn't connected to it.
/ 08 — The funnel
| Step | Users | Step rate | Read |
|---|---|---|---|
| Session start | 37,093 | — | Top of funnel is healthy |
| View product | 7,810 | 21% | Normal for a considered, high value category |
| Add to basket | 190 | 2.4% | The cliff — and the exact step firing broken data |
| Begin checkout | 93 | 49% | Healthy once they commit |
| Purchase | 1 | — | Recorded at $0.00 revenue |
The view to cart drop is partly real and partly lost events · Microsoft Clarity is already installed, so we can watch these sessions and separate genuine hesitation from tracking gaps
/ 09 — The fix
Real style name, the full configured price in both item price and event value, standard GA4 schema on the order page.
Move the Google Ads and ProfitMetrics value tags onto the new schema, so real revenue reaches bidding and profit.
One pixel in the container. Remove the hardcoded script, retire the second pixel ID — trusted events, never doubled.
A postMessage listener for HubSpot's meetingBookedSuccessfully event pushes a real conversion — no paid tier needed.
A proper default then update handshake, connected to the consent banner — a clean signal to Google and Meta in the EU and UK.
/ Next step
We wire Consent Mode and repoint the value tags on our side straight away. The cart and purchase dataLayer and the booking listener go to SAMA's developers as one specific brief — with the exact schema and the postMessage snippet, ready to drop in. Then every number in this deck starts telling the truth.