Customer email & phone
Per website, choose whether AdPix receives your customers' email addresses and phone numbers in full, only as a hash, or not for identity at all. The default is Full, and nothing changes until you change it.
Where it is, and who can change it#
In Admin, under the Website group, open Customer email & phone — the direct link is /admin?sel=customer-data. The setting applies to the active website only; your account's other websites keep their own.
Only an account owner can change the mode. Everyone else sees the same screen read-only. If AdPix support has locked the mode at your request (for example for a legal requirement), the screen shows a lock notice and you contact support to change it. Every change is recorded in Website change history.
The three modes#
| Mode | What AdPix receives | Identity by email and phone |
|---|---|---|
| Full (default) | Email and phone as sent | Yes, as today |
| Hashed | Only a hash of each email and phone; the value itself never reaches AdPix | Yes, inside your account |
| None | Only a hash, kept as a private hash for privacy requests only | No; identity uses your own user ID |
In Hashed, the website tag and the plugins hash email and phone (SHA-256) in the browser or on your server before sending, and AdPix immediately turns that into a private hash with a key that belongs to your account. Each account has its own key, so the websites of one account still recognise the same customer, while no other account — inside your organization or outside it — can link that customer to its own data.
In None, email and phone play no part in identity. Identity uses the user ID you send when a customer signs in, plus the anonymous ID and the device fingerprint. The private hash is kept only so that, when a customer asks for their data to be deleted, you can still find them by email or phone.
What stops working#
When you pick Hashed or None, the screen shows this list:
- Linking a customer by email or phone with other businesses on AdPix, or with your organization's other accounts;
- Seeing email addresses and phone numbers in AdPix (they are not stored, so they cannot be shown);
- Email and phone in webhooks, CRM and ad-platform exports — they receive your user ID and a private key (
email_key,phone_key) instead; - In None only: recognising a person by email or phone.
Reports, funnels, attribution, recognising one customer across devices, search and erasure keep working in both modes.
Default calling code#
Required for Hashed and None. A number like 0912… is turned into its international form (+98912…) before hashing, so the tag, the plugins and the server all arrive at the same hash; this code decides which country local numbers belong to. When none has been stored yet, 98 (Iran) is suggested.
Changing the mode#
From the moment you save, the tag and the plugins pick up the new mode on their next request.
Addresses already stored#
Moving from Full to Hashed or None gives you two choices:
- Only from now on — returning customers keep matching: each customer's stored key is converted to the private form the next time they sign in. Addresses already stored stay as they are.
- Also convert and delete stored addresses — a background job converts every key of the website and deletes the email addresses and phone numbers stored for it. This can't be undone, which is why it asks you to type the website's domain.
The job's progress shows in the Converting stored addresses section of this screen: waiting to start, running, finished with the number of people, emails, phones and profiles converted, or failed. You don't need to keep the screen open.
Past identify events are deleted, because they only carried the identifier — the people stay identified. Other events that still carry an email or phone in their parameters are not rewritten; their number is shown in the job's result.
Going back to Full#
The screen warns you before saving and asks you to type the website's domain. From then on email and phone arrive in full again, but the earlier hashed keys can't be turned back into addresses; a returning customer is reconnected to their history only once they sign in with the same email or phone.
Plain email and phone received#
If the website is on Hashed or None and an email or phone still arrives as plain text (an old plugin, your own server code, a hand-written identify call), AdPix converts it before anything is stored and tracking carries on. This screen counts those cases for the last 7 days, by source (website tag or server API) and type.
To bring the number to zero, update your WordPress or WHMCS plugin to the latest version, or send email_sha256 and phone_sha256 instead of email and phone from your server code. In the Debug view, every event converted this way also carries the warning Plain email or phone converted before storage.
Technical details#
When the mode is not Full, the base tag loads a small separate file, /pii.js, that normalizes and hashes email and phone in the browser. identify waits until it has loaded, and if the browser can't hash (an insecure page), email and phone are dropped — never sent as plain text. Websites on Full never load this file.
Frequently asked questions#
If I never touch this setting, does anything change?
No. Every website, old or new, is on Full and works exactly as before: the same data, the same identity, the same webhook payloads.
Do reports and identity still work in Hashed mode?
Yes. Reports, funnels, attribution, recognising one customer across devices, matching across the websites of one account, search and erasure all keep working. What you lose is linking with other businesses, seeing the address itself, and sending it to outside systems.
Do I need to change my WordPress or WHMCS plugin?
Current plugin versions read the website's mode from the responses to calls they already make and send hashes from then on. An old version breaks nothing: plain values are converted before storage and counted in this screen's warning section, so you know to update.
Can I go back to Full later?
Yes, after typing the website's domain to confirm. From then on email and phone arrive in full again, but the earlier hashed keys can't be turned back into addresses; a returning customer is reconnected to their history only once they sign in with the same email or phone.
Thanks — your feedback helps us improve the docs.