When an email or phone number arrives, the collector normalizes it once per network's own rule set, stores each variant's hash, and discards the plaintext. Email gets a standard SHA-256 hash of the trimmed, lowercased address, plus Google's variant with Gmail dots and "+tags" removed. Phone gets a SHA-256 hash of the E.164 format, with Meta's digits-with-country-code form stored alongside where it differs. First and last name, city and state are hashed; ZIP and country stay in the clear only where a network requires it, like Google and Meta. Network browser and click IDs — Meta's _fbp/_fbc, gclid, ttclid, msclkid — and mobile ad IDs from app clients are captured too, alongside our own visitor ID. Each sync then sends only the identifier variant that network actually accepts.
Ads and Pixels / Audience Vault
Audience Vault: your retargeting data, owned by you.
Every client gets their own isolated store of every visitor, event, lead and customer — an Audience Vault built for retargeting that survives whatever a platform or a browser changes next. It's not a shared pool: no person-level data ever crosses between clients, even two clients run by the same agency.
Hashed identifiers, never plaintext
Built from what's already live
The Audience Vault isn't a new idea untested on real traffic — it's built on the film-warehouse collector, live since 2026-09-18, with server-set first-party cookies, hashing, PII scrubbing and GA4 plus Meta Conversions API sending already proven in production, upgraded to a shared, current Meta Graph API version.
Retargeting audiences, synced automatically
Build a rule like "visited pricing in the last 30 days, didn't buy, consented," and the Audience Vault syncs it daily — hourly for hot audiences — to Meta, Google, TikTok, Microsoft and Snap today, sending only the adds and removes since the last sync instead of re-uploading the whole list every time. LinkedIn, Pinterest and Reddit sync the same way the day each of those channels goes live — the Vault is built to add a network without a client having to rebuild the audience.
Google is the one exception, handled honestly
Google's Customer Match requires a strong account history and more than $50,000 in lifetime spend, so most small and new clients don't qualify. For them, Google retargeting runs through GA4 audiences instead, which don't have that threshold; Customer Match is used automatically wherever a client does qualify. We won't tell you Customer Match is live for an account that Google itself won't allow it on.
Why not just use each network's own audience tools
Meta's custom audiences, Google's audience lists and TikTok's saved audiences all work fine — inside that one network. The problem is that a lookalike audience built in Meta doesn't help your Google or Microsoft retargeting, and if a client ever leaves a network, that network's audience leaves with them. The Audience Vault builds the retargeting audience once, from first-party data the client actually owns, and syncs it to every network that supports it, so the work isn't locked inside any single platform's account.
Cost, roughly, before it's confirmed
Running the Audience Vault costs about $3 to $5 per client per month at 1 million events, based on current list prices for the underlying storage and sync infrastructure — an estimate we'll keep testing against real usage across real clients, not a number we're promising is final today or forever.
Ownership, in writing
The client owns their vault. They can export it at any time, including after they leave, and no person-level data is ever shared between clients or pooled for anyone else's benefit. Data use beyond that client's own retargeting is limited to anonymized, aggregate statistics — minimum group sizes, no identifiers — for industry benchmarks and improving the product overall.
Frequently asked questions
Real answers before you make a decision.
Does the Audience Vault store my customers' actual emails and phone numbers?
No, not in the form they arrived in. Identifiers are hashed on arrival using each network's own required format, and the plaintext is discarded after hashing. What's stored is the hash, not the original value.
Can one client's audience data ever end up in another client's account?
No. Each client's vault is isolated. The only data that leaves a single client's vault is anonymized, aggregate statistics with minimum group sizes and no identifiers, used for benchmarks and product improvement — never another client's raw retargeting audience.
What happens to our retargeting audiences if we switch agencies or leave the platform?
The vault belongs to the client, not the agency or to us, and it can be exported in full at any time, including after the client leaves. Retargeting audiences already synced to a network stay there until that network's own retention rules remove them; nothing about leaving Ads and Pixels pulls a client's audience back out of Meta, Google or any other network it was already synced to.
Why doesn't Google Customer Match work for every client?
Google requires a strong account history and more than $50,000 in lifetime ad spend before Customer Match is available on an account — a rule Google sets, not us. Clients who don't meet it get GA4-based retargeting instead, which has no such threshold, and Customer Match turns on automatically the moment an account qualifies.
Does the Audience Vault help with anything besides retargeting?
Yes. The same hashed, first-party store powers lookalike and prospecting audiences built from your best existing customers, feeds real customer counts into the Results Map's verified totals, and gives the AI Media Planner actual history to plan a brand-new campaign against, instead of guessing purely from category averages alone.
Own your retargeting data from day one.
Connect a client and their Audience Vault starts capturing, hashing and syncing before their first campaign even launches.