Sample report. A real audit of an Indian D2C skincare store, run on 28 September 2026, with its name, products and tag ids replaced. Nothing else is changed.
Signal audit of skincare-store.example · 28 Sept 2026
Flying blind
7 serious gaps are hiding sales from your ad platforms.
Ad sales Meta and Google likely never see
13% to 42%
A range from the 4 gaps we saw, with sourced assumptions. How we got it
Fix these first
HighClick survival
In Safari, the Meta click is forgotten after 24 hours
Cookiebees sets the click id from your own domain's server, on your store's network, so Safari keeps it as long as it is meant to last.
Cookiebees fixes this
HighPixel health
1 event arrives without the value, currency or products
Cookiebees builds every event from the product and cart data itself, so value, currency and product ids are always present.
Cookiebees fixes this
HighCheckout visibility
Your checkout runs on GoKwik, and nothing reports the sale from a server
Cookiebees stitches GoKwik orders back to the visitor who clicked, then sends Purchase from our server with the click id attached.
Cookiebees fixes this
Cookiebees fixes 12 of the 13 problems we found, once your store is connected.
Fix them with CookiebeesSix checks, and everything we found
Open any line to see why it matters, what we saw on your store and the fix.
Click survival
14/100
3 problems
Pixel health
0/100
4 problems
Checkout visibility
66/100
1 problem
Consent and privacy
66/100
3 problems
Match quality
82/100
1 problem
Speed
66/100
1 problem
Click survival 14
Does the ad click that brought the shopper survive until they buy, in Chrome and in Safari?
Pixel health 0
Do the shopping events reach each platform once, with value, currency and products, and past ad blockers?
Checkout visibility 66
Can your platforms still see the shopper once they reach the checkout?
Consent and privacy 66
Do tags wait for consent, honour a refusal, and keep personal data out of what they send?
Match quality 82
How well can Meta and Google tell who bought?
Speed 66
What your tags cost in page weight and processor time.
What is running on your store
Every ad and analytics platform we saw, how it sends, and where in the journey.
| Platform | Sends from | Landing | Product | Add to cart | Cart | Checkout |
|---|---|---|---|---|---|---|
Google Analytics 4 G-SAMPLE0004 | Browser only | |||||
Google Ads AW-90000000003 | Browser only | |||||
Microsoft Ads (UET) 900000005 | Browser only | |||||
Meta Pixel 900000000000006 | Browser only |
Your stack, and where it disconnects
A scan sees the pages, not the tools behind them. Tap what you use; we pre-filled what the scan saw.
Your store runs on
Your checkoutfrom the scan
Email and SMS
WhatsApp and cart recovery
Sending events from a server
You judge ads by
2 places your stack disconnects
1 of 6 answered
GoKwik knows the buyer. Your ads do not.
GoKwik holds the phone and email of every checkout, paid or abandoned. Meta and Google only learn them if someone sends them back, tied to the ad click.
Cookiebees reads GoKwik's checkout feed and sends checkout, payment and Purchase from our server, with the click and hashed contact details.
Cancelled and returned orders still count
A cash-on-delivery order refused at the door was reported as a sale the moment it was placed. The platform keeps optimising toward buyers who never pay.
Cookiebees can report cash orders when they are delivered, and takes back a sale that is cancelled or returned.
One ad click, followed through your store
We arrived with a click id made for this visit and watched what your site did with it on each page.
The Meta click we arrived with, on the iPhone walk
fbclid=IwY2xjawCbAudit77josmunLanding
Kept in _fbc
Sent to Meta with PageView
Product
Kept in _fbc
Sent to Meta with PageView, ViewContent
Add to cart
Kept in _fbc
Sent to Meta with AddToCart
Cart
Kept in _fbc
Sent to Meta with PageView
Checkout
Kept in _fbc
Sent to Meta with InitiateCheckout
Written by a script (capi-automation.s3.us-east-2.amazonaws.com/public/client_js/). Safari caps every script-written cookie at 7 days, and at 24 hours when the visit came from an ad click with an id in the link.
Other tools on your site also kept a copy (multiFbc, WIGZO_CURRENT_URL, vwoSn), but Meta does not read those.
What it costs, in your numbers
Every figure is a range because every assumption is one. Change any of them.
Ad sales the platforms likely miss
13% to 42%
of the sales your ads make
Add your revenue to see this in rupees.
Where the range comes from
Combined by multiplying, not adding: a sale lost to an ad blocker is not counted again as lost to Safari.
Everything the browser recorded
Each pixel, the checkout, consent, ad blockers, matching and speed, read from the requests your store sent.
Cookiebees fixes 12 of these 13.
This audit was one visit. Cookiebees builds your store its own measurement system: it keeps the ad click on your domain, sends each sale from our server with the click and hashed customer details, and checks it every day.
Start with CookiebeesThis is a sample
A real audit of another business, with its name and ids removed. Yours takes about two minutes and needs no login.
Audit my storeWhat this audit cannot see
- We walked your store as one visitor arriving from an ad, once on a desktop and once as an iPhone. Tags that only run for some visitors, some countries or some pages can be missed.
- We never type anything or pay, so the Purchase event itself is outside what any scan can see. What we can see is whether the steps before it carry what a Purchase needs.
- Safari's cookie limits are applied from how each cookie was written (by a script or by a server, and from which network), which is what Safari checks. We run Chromium, not Safari.
- A server-side setup sends from a server, so a page can show that one is set up, never that it is sending.
- Our visit is labelled utm_source=cookiebees-audit, so you can filter it out of your analytics.