Pulsar · Field guide · No. 28 · The revenue the pixel misses, how to upload offline and CRM conversions, and why matching real value changes what Meta optimizes toward.
Close the Loop
Plenty of revenue happens where the pixel can’t see — phone orders, in-store, CRM deals. Feed those conversions back to Meta and it learns from your real buyers, not just the online ones.
The revenue the pixel never sees
The pixel watches the website. But sales happen in places it can’t: phone orders, in-store purchases, invoices, and sales-team deals that close weeks later. To Meta, those buyers look like they never converted.
If the algorithm can’t see a sale, it can’t learn from it — and it keeps finding more of the wrong people.
Send those conversions back to Meta
You upload them — via an offline event set or the Conversions API — as events carrying hashed customer info (email, phone) and the order value and time. Now Meta knows the sale happened.
How matching closes the loop
Meta matches your uploaded records to the people who saw your ads, using the hashed email/phone. Match found → the sale gets attributed to the ad, and — crucially — fed into optimization. Your match rate is the health metric to watch.
Optimize toward real value
Send the actual order value, not just “a conversion happened”. Then Meta can chase revenue — finding people who buy the £300 order, not the £9 one (value optimization).
The lead-gen loop
If you run lead ads, this is the difference between “more form-fills” and “more customers”. Upload which leads actually became customers, and Meta stops optimizing for cheap leads and starts finding people who close.
Set it up
The algorithm can only optimize toward outcomes it can see. Show it the whole business — not just the part that happens in a browser.