In this guide
- Collect less, but cleaner: e-mail, phone, consent, source, orders and key behaviour.
- Ask in plain words, at the moment of value, with consent where required.
- Validate at the door. A bad e-mail at the form is a bad record for years.
Customer data is the fuel for everything else: audiences, personalisation, attribution, retention. Most businesses collect either too little, because nobody planned it, or too much, because everything was switched on. This page gives a simple plan for what to collect, where and how, with the quality and consent points that make it usable. It continues from first-party data and leads into customer data management.
What to collect
| Data | Purpose | When to ask |
|---|---|---|
| Contact, matching, receipts, remarketing lists | At checkout, sign-up and lead forms | |
| Phone | Delivery, support and matching | At checkout and lead forms, if needed |
| Name and address | Delivery and billing | At checkout |
| Consent choices | Prove what the person agreed to | At the banner and at each form |
| Source and campaign | Know what brought them | Automatically, from the URL and click IDs |
| Orders and returns | Value and behaviour | From the shop |
| Preferences | Relevant offers | In an account or a short survey |
Connected in minutes
Add your domain, install the pixel, connect your ad platforms and watch the first events land.
Where to collect it
Checkout
The place with the most intent. Keep the form short and validate input.
Lead forms
Ask for what you need to follow up. Extra fields reduce completion.
Behaviour events
Product views and cart actions, sent as events with consent. See which events to send.
Collect it well
Write the purpose first
For each field, one sentence on why you need it.
Ask with consent where required
And record the date and version of the notice.
Validate the format
E-mail syntax, phone with country code, address checks.
Normalise
Lower-case e-mail, trim spaces, one phone format.
Send it where it is used
CRM, shop, ad platforms and tracking server, hashed where needed.
Works with your stack
Grab a logo and throw it. These are the tools Open Tracked already talks to.
Hashed customer data for ads
Ad platforms ask for hashed e-mail and phone. Hash them after normalising, and send them only with consent. A tracking server that remembers them for returning visitors, such as Open Tracked's Data Store with the Enricher, means a visit that only browses can still be matched. See Meta event match quality.
Common mistakes
- Collecting date of birth, gender or address when you never use them.
- No validation, so the list fills with typos and fake e-mail addresses.
- Consent hidden in terms nobody reads.
- Data spread over many tools with no owner.
- Never deleting anything.
A realistic example
A small online shop collects name, address, e-mail, phone, date of birth, gender and a free-text "how did you hear about us" at checkout. Completion is low and half of the free-text answers are empty or jokes. The shop cuts the checkout form to what it needs for delivery, adds a clear optional newsletter box with consent, replaces the free-text field with a short list of options and captures the traffic source automatically from the URL. Checkout completion improves, the e-mail list grows with people who actually want it, and the shop has cleaner source data than the old text field ever gave. Less asking produced more and better data.
Runs on your domain, anywhere
Your tracking runs on your own domain, so a visit from any country is handled the same way.
Frequently asked questions
What customer data should I collect?
E-mail, phone where needed, consent choices, source and campaign, orders and key behaviour.
How do I collect it legally?
Tell people why, ask for consent where required, collect only what you need and respect withdrawal.
Why validate data at the form?
Bad data at the start stays bad in every system that uses it.
Do ad platforms need hashed data?
Yes. Format it first, then hash it, and send it only with consent.
Where should I keep it?
In your shop and CRM, with controlled access and a retention period.
Do I need spreadsheets to read my results?
No. Once tracking is live, the Open Tracked analytics shows spend, revenue, ROAS and profit, and you can ask Ari, the built-in AI assistant, questions about your own numbers in plain words. Ari's allowance depends on your analytics plan.
Is Open Tracked different from Open Track or Open Space Track?
No. Open Tracked is the official name of our server-side tracking platform, and the website is opentracked.io. Many people search for it as Open Track, OpenTrack or Open Space Track. All of them lead to the same product: server-side Google Tag Manager hosting, first-party analytics and a CRM pipeline.
Fix your tracking at the source
Open Tracked hosts your server-side Tag Manager, keeps first-party cookies alive and shows what each ad is really worth.
The Open Tracked team
We build Open Tracked: server-side tracking hosting, analytics and the tools around them, for stores that spend on ads. Questions about this guide, or an idea for the next one?
Comments
Loading comments...
Guides · 5 min read
