Pixel FAQ. Every question answered.
Implementation, match rates, data privacy, and compliance — all in one place. Updated 2025.
- Image Pixel: a 1-line HTML tag using standard image syntax.
- Distributor Tag: JavaScript-based; offers filter configuration and requires domain authentication. This is what TDTM deploys.
- Image Pixel — single-line HTML tag.
- Distributor Tag — JavaScript implementation that requires domain authentication.
- IP-Based Solution — for high-volume use cases where the other mechanisms aren't a fit.
- Resolve the pixel to a hashed email.
- Resolve that hashed email to our Super Identity Graph (SIG) — delivering verified identity data.
- IP address
- 3rd-party cookies
- Device/browser characteristics
- Cookie IDs
- Device/browser details
- Encoded query string values
0.7· Precision — for high-accuracy use cases (e.g. personalized offers).0.3· Balanced — for general targeting or attribution.0.1· Reach — for broader targeting and mid-funnel segments. (Default)- LiveIntent licenses our full Super Identity Graph.
- Audience Acuity leverages the LiveIntent publisher network and web pixel technology to enable anonymous-to-known resolution through hashed emails.
What is a pixel?
A pixel is a lightweight URL call placed on a webpage. Each time a visitor lands on that page, the pixel fires — triggering a real-time match attempt to resolve the anonymous visitor to a known hashed email (HEM). The HEM is then matched to our identity graph to resolve a verified individual (name, address, email).
Do you offer different types of pixels?
Can the pixel resolve to other hash types?
Yes. In addition to MD5, we support SHA1 and SHA256 resolutions.
What is your pixel match rate?
Match rates range from 20% to 60%, with most clients seeing 30–40%. These are among the highest in the industry when balancing match rate and accuracy.
Our two-step process:
How do I implement the pixel on my website?
Pixels can be added to your website's global <head> or deployed via a tag manager like Google Tag Manager (GTM).
How does the pixel resolve a visitor to a hashed email?
When the pixel fires, it captures non-PII metadata including:
That metadata is matched to an MD5 hashed email via a continuously updated reference database. The hashed email is then resolved to a verified identity in our Super Identity Graph, built from deterministic linkages across transactional and behavioral data.
The pixel never collects plain-text PII (names, emails, phone numbers, etc.).
Will the pixel slow down my website?
No. The pixel is a lightweight, asynchronous call and does not introduce latency. Core Web Vitals are unaffected.
What data does the pixel collect? Is anything stored?
The pixel collects non-PII metadata like:
No user-entered data or sensitive inputs are collected, stored, or shared with any 3rd parties other than to facilitate delivery of the service. Audience Acuity does not store this data — it's used only for real-time identity resolution. Audience Acuity does not support geo-location-based tracking and does not track an individual's actions over time.
What defines an identity?
An identity is a unique combination of first name, last name, and postal address. Each resolved identity is assigned a persistent ID within our Super Identity Graph.
How accurate is the identity resolution?
Our resolution accuracy exceeds 90%, based on deterministic linkages validated through multi-source signals.
Do MD5 emails resolve to a single individual?
Yes. Each distinct MD5 in our system maps to one unique individual.
Can you batch MD5s instead of resolving 1 per pixel?
No. The pixel is a real-time service, resolving one event per pixel fire.
Can I white-label or proxy the pixel URL?
We do not support white-labeling or proxying of the pixel URL. However, some clients have deployed the pixel through a container managed within their infrastructure.
Can I apply filters to the pixel?
Image Pixel: No filters can be applied.
Distributor Tag: Yes, quality filters can be set.
Quality Filter Options:
window.liQd_did_00b8.resolve(
function(result) { if (result.unifiedId) console.log(result.unifiedId); },
function(err) { console.error(err); },
{ qf: "0.3", resolve: "md5" }
);Can I use the pixel on a B2B site?
Yes, but only consumer identities will be returned. Our graph does not support business addresses, and match rates will be significantly lower than typical consumer sites.
Are there restrictions on who can use the pixel?
Yes. The pixel may not be used on websites offering products or services related to:
Each client is responsible for ensuring their privacy policy allows for this kind of data collection. See our Privacy Best Practices guide
Do we need to amend our privacy policy?
Yes — each client is responsible for ensuring their privacy policy allows for this kind of data collection. See our Privacy Best Practices guide for sample language. We are typically not a named 3rd party on client privacy policies.
What is your relationship with LiveIntent / Zeta?
TDTM has partnered with LiveIntent (now part of Zeta) for 7+ years.
This joint identity resolution stack enables high-performance resolution across web. We're fully transparent with customers that we use LiveIntent's pixel — many are already familiar with it and appreciate the interoperability.
Ready to unlock your website traffic?
Privacy-conscious identity resolution with 30–40% typical match rates and verified consumer data. Get started or talk to our team.