Products
PixelCops
Most tracking sees scattered events. PixelCops sees the whole visitor: every interaction, tied to one identity, checked for bots before it counts, and, where durable identity is switched on, remembered for up to 400 days.
The problem
A normal pixel does not see people. It sees isolated events. It fires once when a page loads, again when a form is submitted, and never connects the two to the same visitor, or to the ad that brought them. Each firing is a disconnected hit with no memory, no history, and no sense of the journey that led to it. And to add even one of those events, you usually have to build a tag, a trigger, and a data layer by hand.So you are asked to do a lot of manual work to produce a picture that is fragmented by design. You get a pile of hits, not an understanding of who did what, in what order, and why.
Why it breaks, technically
There are three separate failures stacked on top of each other, and each one loses a different slice of the truth.
- The events are stateless. A browser pixel has no durable memory of the visitor. The moment the tab closes, or the browser clears storage, the person is gone. The next visit starts from zero, as a stranger, even if they are the same buyer coming back to convert.
- The delivery is blocked. The pixel loads from a third-party domain, which ad blockers, Safari, and Brave strip on sight. A large share of the events never leave the browser at all, so even the disconnected hits you were counting on are incomplete.
- The clean and the fake are counted the same. A pixel cannot tell a real shopper from a bot or a headless script. Every firing is treated as a real event, so your picture is not just fragmented, it is polluted.
The net effect is that you are reconstructing a customer journey from a handful of blurry, unlinked snapshots, half of which are missing and some of which are fake.
What it costs you
- You cannot see the journey. You know a form was submitted, but not that the same person clicked a Google ad nine days earlier, browsed twice, and came back to convert. The story that would tell you which ad actually works is lost.
- You pay to reacquire people you already had. A returning buyer looks brand new, so the ad that first earned them gets no credit, and you spend again to win the same customer.
- Your optimisation learns from noise. Fake and unlinked events go to your ad platforms as real conversions, and the algorithm chases more of the same.
- You burn engineering time on setup that still produces this broken picture.
How DataCops solves it
PixelCops is DataCops page-level capture. Once the first-party script is on your site, it stops treating events as isolated hits and starts sensing the visitor as one continuous person. Every interaction, from the ad click they arrived on to the thank-you page they finish on, is captured, tied to a single durable identity, and passed through the fraud verdict before it counts. You get a real person with a history, not a pile of disconnected events, and you get it with no tags to build and no data layer to maintain.It works on all three failures. The identity can be durable, so the person is remembered. The script runs on your own domain, so blockers are far less likely to strip it. And every interaction is fraud-checked, so the picture is cleaner.
What it senses
PixelCops reads the visitor's behaviour across the whole visit, automatically, with nothing to configure:
- The ad click they arrived on, captured from the link and kept attached to everything that follows.
- The pages they view, including the thank-you and confirmation pages that mark a conversion.
- The forms they submit, and which fields carried the identifying detail.
- The buttons they click, like add to cart, book a call, or a phone number.
- The shape of the visit: how they moved through the site and in what order.
These are not stored as separate rows. They are woven into one behavioural history for that person, so you can see the sequence, not just the endpoints.
One person, remembered
Everything PixelCops senses is attached to one identity for the visit. Durable identity adds a signed, first-party ID that can last up to 400 days, set by the server so it survives the seven-day wipe that Safari and iOS apply to normal browser storage. It is rolling out now and is not yet on for every site. It is only set when consent allows and the browser can hold it. Where it is on, a visitor who clicks an ad today and comes back three weeks later to buy is recognised as the same person, with the original ad click still attached.
This is the difference between a pile of anonymous events and a real customer journey. The behaviour is not just captured, it is connected, across visits, to one person you can credit correctly.
Clean from the first touch
Sensing a visitor's whole behaviour only helps if the visitor is real. Every interaction PixelCops captures runs through the same fraud verdict that powers the rest of the platform: the network the visit comes from, and how the session behaves on the page. When a session is flagged as a bot, its events are skipped instead of being sent to your ad platforms as conversions, and the delivery log shows the reason.
For anything unusual
When you have a button or element that is not standard, you open your live site inside DataCops and click the thing you want to track. No code, no CSS selectors, no tag manager. It joins the same behavioural history as everything else, tied to the same person, cleaned by the same verdict.