Engagement data that survives a privacy review
Sooner or later your lead file lands in front of someone whose job is to ask where the data came from. Here is how ours is collected, what we refuse to collect, and why the file is better for it.
Robert Waters
Marketing Director · 2 min read

Every lead program eventually meets a reviewer. Sometimes it's your own legal team, sometimes it's security on the buyer's side, and the question is never whether the numbers look good, it's where they came from. We think a lead file should have a boring answer to that question, so this is ours.
Anonymous by default is a design decision
LG Pixel measures attention, not people. It sets no cookies, it does no fingerprinting, and it stores nothing on the visitor's device, because the job is to know whether content was genuinely on screen and how long a reader actively stayed with it, and that job doesn't require knowing who the reader is. A session that never identifies itself stays anonymous from first paint to last, and it still does useful work in aggregate, since campaign reporting is built from exactly these sessions.
Identity arrives by invitation
The form fill is the moment a record becomes a person, and it only happens because the visitor asked for something and handed over their details to get it. From that point the engagement record belongs to a named contact, which is what makes a delivered lead worth more than a line in a traffic report. Nobody gets unmasked by clever matching, and there is no shadow profile waiting for a name, because the record starts where the request starts.
The browser's no is a no
Some visitors arrive with Global Privacy Control or Do Not Track switched on, which is a preference stated in the clearest way the web currently offers. Our capture treats it as exactly that. When the browser says no, we don't capture, and the session simply never becomes part of anyone's file. It would be easy to treat these signals as a technicality, and some of the industry still does, but a program built on attention has no business ignoring the most explicit signal a person can send.
Consent makes the file better, not thinner
The honest trade is that refusing to collect some things means collecting less, and we think the trade runs in your favor. A file where every row exists because a person asked for an asset reads differently in a sales call than a file assembled about people, since the first conversation can open with the thing the prospect actually requested. Modeled and inferred data answer a different question, plenty of teams use them well alongside programs like ours, and the distinction we'd hold onto is simple: inference estimates interest, a consented engagement record evidences it.
Questions worth asking any vendor
Including us. Does identity ever attach without an explicit action by the visitor? What happens when a browser sends Global Privacy Control? Can the engagement totals be audited, including the traffic that was excluded and why? Who sourced the contact, and can they say how? We like this list because our answers are short, and a vendor whose answers run long is telling you something useful too.
None of this makes a lead file compliant on its own, and your counsel's checklist is still your counsel's checklist. What it makes is a file where every row can explain itself, who the person is, what they asked for, what they read and for how long, collected in a way you can describe to a reviewer in one breath. That's a narrow claim, and it's the kind we prefer.


