1.1 billion people block ads. Their purchases slip past your campaigns. Your campaigns optimize without them, and you pay for every sale 13% more than you should, on average. wesaw sends each sale from your server, where nothing blocks it.
✓ Official Meta connection✓ Guided setup✓ No codeSources: eyeo, Ad-blocking report 2026 (1.1 billion ad-blocking users, Q4 2025). Meta, Performance 5, October 2022 (13% lower cost per acquisition with server-side sending).
Real screen of wesaw on Bloxks, our own SaaS, on 5 November 2026.
✕ ObserveIt starts with a real sale. Recorded at its source, with its amount and time.
From sale to signal↗ wesawConversion receipt / 1042 ···
Shopify · signed webhook Order #1042
149.00 €
✓ Shopify order recorded 14:32:14
Observed Product illustration · fictional data VerifySee what was prepared. The visitor's choice, the matching data, one shared ID.
See the evidence↗ wesawConversion receipt / 1042 ···
Matching data Ready for delivery
Recorded consent ✓ Granted
Email normalized ✓
Phone normalized ✓
Event identifier demo_purchase_1042
Server send requires granted consent.
Product illustration · fictional data wesawConversion receipt / 1042 ···
Meta Conversions API ✓ Accepted
14:32:17
Destination response HTTP 200
Delivery attempts 1
Accepted describes delivery. Attribution remains unknown.
Product illustration · fictional data wesawConversion receipt / 1042 ···
Delivery overview
Illustrative period Observed 142
Accepted 141
Rejected 1
! 1 delivery to investigate Destination permission error
Check Meta connection permissions ↗ Product illustration · fictional data
Where sales go missing
Your next customer clicked your ad.
Your campaign will never know. An ad blocker, Safari, a checkout on another domain: the pixel never fires. You paid for the click. The sale goes nowhere.
Get started Catch Recorded where it happens.
✓ Order or payment✓ Received on your side✓ Even if the pixel is blocked 14:32:14 · Sale recorded
Prepare Matched to the buyer.
✓ Visitor's choice respected✓ Prepared on our servers✓ One ID, no double count Consent · granted
Send Meta learns from it.
✓ Sent to Meta✓ Answer kept✓ Retried on failure 14:32:17 · Accepted
Explain You see what sold.
✓ Linked to its ad✓ Real revenue next to Meta's✓ Unknown stays unknown Meta merge · not observable
Product illustration · fictional data Pause automatic progression
No more guessing
You know what you spend.
wesaw tells you what it earns.
wesawConversion receipt / 1042 ···
Shopify → Meta Order #1042
✓ Accepted ✓ Shopify order recorded 14:32:14
Observed ✓ Recorded consent Recorded state
Granted ✓ Event created Recorded state
Observed ✓ Matching signals prepared Recorded state
Available ✓ Sent to Meta Recorded state
Observed ✓ Destination answered 14:32:17
Accepted ◌ Final Meta merge Not observable
Open the technical evidence+
Event identifier demo_purchase_1042
Destination response HTTP 200 · events_received: 1
Delivery attempts 1
Ad attribution Not observable Product illustration · fictional data wesawConversion receipt / 1042 ···
Delivery overview
Illustrative period Observed 142
Accepted 141
Rejected 1
! 1 delivery to investigate Destination permission error
Check Meta connection permissions ↗ Product illustration · fictional data wesawConversion receipt / 1042 ···
Delivery overview
Illustrative period Observed 142
Accepted 141
Rejected 1
! 1 delivery to investigate Destination permission error
Check Meta connection permissions ↗ Product illustration · fictional data wesawConversion receipt / 1042 ···
OBSERVATIONS 142 Observed purchases
141 Accepted deliveries
1 Rejected delivery
↓ DIAGNOSTIC A destination rejected one event.
↓ NEXT STEP Inspect the response and connection permissions.
Product illustration · fictional data The sale receipt
Every sale
gets a receipt. Start from the sale. ↗ Open any sale and follow its path. Missing pieces stay visible.
Read what was sent. ↗ What left, when, and how Meta answered. If nothing was sent, you see why.
Know the limit. ↗ Meta's own merge and ad credit stay on Meta's side. The receipt says so.
Read a sale receipt→ wesawConversion receipt / 1042 ···
Shopify → Meta Order #1042
✓ Accepted ✓ Shopify order recorded 14:32:14
Observed ✓ Recorded consent Recorded state
Granted ✓ Event created Recorded state
Observed ✓ Matching signals prepared Recorded state
Available ✓ Sent to Meta Recorded state
Observed ✓ Destination answered 14:32:17
Accepted ◌ Final Meta merge Not observable
Open the technical evidence+
Event identifier demo_purchase_1042
Destination response HTTP 200 · events_received: 1
Delivery attempts 1
Ad attribution Not observable Product illustration · fictional data wesawConversion receipt / 1042 ···
Matching data Ready for delivery
Recorded consent ✓ Granted
Email normalized ✓
Phone normalized ✓
Event identifier demo_purchase_1042
Server send requires granted consent.
Product illustration · fictional data wesawConversion receipt / 1042 ···
Meta Conversions API ✓ Accepted
14:32:17
Destination response HTTP 200
Delivery attempts 1
Accepted describes delivery. Attribution remains unknown.
Product illustration · fictional data Tracking health
Less noise.
A clear next step. Check what arrived. ↗ Your sales and their sends, for the period you pick.
See what failed. ↗ Meta's last answer, and whether a retry is coming.
Fix it. ↗ The connection, the setting or the sale to check.
Explore tracking health→ wesawConversion receipt / 1042 ···
Delivery overview
Illustrative period Observed 142
Accepted 141
Rejected 1
! 1 delivery to investigate Destination permission error
Check Meta connection permissions ↗ Product illustration · fictional data wesawConversion receipt / 1042 ···
Delivery overview
Illustrative period Observed 142
Accepted 141
Rejected 1
! 1 delivery to investigate Destination permission error
Check Meta connection permissions ↗ Product illustration · fictional data wesawConversion receipt / 1042 ···
▣ Browser emission Browser emission attested
▤ Server delivery Server accepted
Same event ID demo_purchase_1042
↓ Final merge inside Meta: not observable
Product illustration · fictional data Data, with a purpose
From numbers
to a reason to act. Start with the totals ↗ Sales and sends, side by side.
Spot the issue ↗ A refused send keeps Meta's answer.
Follow it ↗ Open the sale. Unknown stays unknown.
See how it works→ wesawConversion receipt / 1042 ···
Shopify · signed webhook Order #1042
149.00 €
✓ Shopify order recorded 14:32:14
Observed Product illustration · fictional data wesawConversion receipt / 1042 ···
OBSERVATIONS 142 Observed purchases
141 Accepted deliveries
1 Rejected delivery
↓ DIAGNOSTIC A destination rejected one event.
↓ NEXT STEP Inspect the response and connection permissions.
Product illustration · fictional data wesawConversion receipt / 1042 ···
Shopify → Meta Order #1042
✓ Accepted ✓ Shopify order recorded 14:32:14
Observed ✓ Recorded consent Recorded state
Granted ✓ Event created Recorded state
Observed ✓ Matching signals prepared Recorded state
Available ✓ Sent to Meta Recorded state
Observed ✓ Destination answered 14:32:17
Accepted ◌ Final Meta merge Not observable
Open the technical evidence+
Event identifier demo_purchase_1042
Destination response HTTP 200 · events_received: 1
Delivery attempts 1
Ad attribution Not observable Product illustration · fictional data
What we know.
What we don't. Observed The sale happened. We received it from its source. Independent of any ad report.
Source: the sale itself Reported by Meta Meta answered. Accepted means received. Ad results stay Meta's.
Source: Meta's response Inferred A link is estimated. Always labelled, with its method. Never mixed with what we saw.
Source: an explicit method Not observable Some answers are Meta's. Whether Meta credited this sale to an ad, it does not tell us.
Boundary: inside Meta
wesawConversion receipt / 1042 ···
▣ Browser emission Browser emission attested
▤ Server delivery Server accepted
Same event ID demo_purchase_1042
↓ Final merge inside Meta: not observable
Product illustration · fictional data Connects to
Where you sell.
Where you advertise. Your sales at the source. Your ads on the other side. wesaw in between.
Each connection depends on the platform's permissions.
Explore the integrations↗ Connectors
More platforms next. Meta today. Instagram posts and Google Ads next. Nothing is shown as ready before it is.
Explore the integrations↗ Meta Available Instagram Planned Google Ads Planned Snapchat Planned Pinterest Planned K Klaviyo Planned Planned connectors are not available yet.
Up and running
Connect. Check. See. 01 Connect where you sell A few guided clicks. No developer needed.
02 Connect Meta Pick your pixel. We check your sales arrive.
03 See your first sale From the ad to the payment.
What it costs you
How much of your budget
goes nowhere? Estimate: 13% of your budget, the average drop in cost per acquisition Meta reported for advertisers who add server-side sending (Performance 5, October 2022). Not a measurement of your account.
Your pixel misses sales. Your budget still pays for them.
A few things worth knowing. I am not technical. Is this for me?+ Yes. You connect your accounts, wesaw does the rest. No code to write.
Why does Meta miss some of my sales?+ Its pixel runs in the browser, and browsers block it more and more. wesaw records the sale on your side, where nothing blocks it.
Will Meta count a sale twice?+ No. Both sides send the same sale with the same ID, so Meta keeps one.
Does it show what my posts bring in?+ Not yet. Linking your Instagram and TikTok posts to sales is being built.
What about visitors who refuse tracking?+ They are never sent to Meta. wesaw keeps a record of why.
Are the figures on this page real?+ The product illustrations use fictional data. They show how wesaw works, not customer results.
Stop guessing
Stop paying for sales
nobody sees. See it run on your own sales before you pay. Money back if our numbers don't match yours.