In this guide
- Pick one source of truth for each kind of customer data and sync from it.
- Record consent, define retention and control access.
- Automate the sync to ad platforms and tools so lists stay fresh and removals propagate.
Customer data collects itself in many places: the shop, the e-mail tool, the CRM, the helpdesk, the ad platforms. Without a plan, the same person exists in six versions, each a little different, and nobody knows which is right. Data management is the plan. It does not need a big project. It needs a few clear rules and a routine. This page lists them, building on customer data collection and first-party data. It is general guidance, and not legal advice.
1. A source of truth
Decide which system owns each piece of data. Orders belong to the shop. Lead stages belong to the CRM. Consent belongs to the consent platform. Other tools read from these and do not overwrite them. When two systems disagree, the owner wins.
| Data | Owner | Readers |
|---|---|---|
| Orders, refunds | Shop | Analytics, CRM, ad platforms |
| Lead and deal stages | CRM | Ad platforms, reports |
| Consent choices | Consent platform | Tag Manager, e-mail tool |
| E-mail subscription status | E-mail tool | CRM, ad lists |
| Tracking identifiers | Tracking server and CRM | Ad platforms |
Raw events in. Clean events out.
Open Tracked collects each event on your own domain, removes the noise and sends what is left to Meta, Google Ads, TikTok.
2. Identity
Use stable IDs: a customer ID, a lead ID, an order number. Match on them rather than on names. Normalise e-mail and phone so duplicates merge. Keep a clear rule for what happens when two records are the same person.
3. Consent and withdrawal
Store consent with a date, a version of the notice and the purposes agreed. When someone withdraws, update every system and remove them from audience lists. Build this as a routine, not a one-off.
3 things to remember
Scroll and the points stack up.
Pick one source of truth for each kind of customer data and sync from it.
Record consent, define retention and control access.
Automate the sync to ad platforms and tools so lists stay fresh and removals propagate.
4. Quality
- Validate on entry. Re-check with a periodic clean-up.
- Remove bounced e-mail addresses and obvious fakes.
- Standardise country, phone and address formats.
- Report on completeness: what percent of customers have an e-mail, a phone?
5. Retention and deletion
Keep data only as long as you need it. Define a period for each kind, and delete or anonymise afterwards. In Open Tracked, the Data Store keeps hashed identifiers for the days you choose, up to 400, and entries can be removed. See the Data Store.
6. Access
Give people the access they need and no more. Use named accounts, not shared logins, and review who has access twice a year.
7. Sync
Define what goes where
Customer lists to ad platforms, subscriber lists to e-mail, stages to ad platforms.
Automate it
Scheduled uploads or webhooks.
Include removals
People who withdrew or unsubscribed.
Check the result
Match rates and counts after each sync.
A realistic example
A shop finds that the same customer appears in its e-mail tool, its CRM and its shop with three different spellings of their name and two different phone numbers. A customer who unsubscribed from e-mail still appears in a Meta audience built last quarter. The shop names the shop as the owner of orders, the CRM as the owner of lead stages and the e-mail tool as the owner of subscription status, and sets up a weekly sync that carries unsubscribes into the ad audiences. It also cleans phone formats once and enforces the format at the form. A month later the lists agree, removals propagate and nobody has to wonder which system to believe.
Brands that grow on cleaner data
Stores and agencies use Open Tracked to see which ads earn the sale.
Frequently asked questions
What is customer data management?
The rules and routines for where customer data lives, who owns it, how it is kept clean and how it moves between tools.
Do I need a CDP?
Not usually at small scale. A CRM and a good tracking set-up cover most needs. See CDP vs CRM.
How do I handle deletion requests?
Remove the person from the shop, CRM, e-mail tool, audience lists and the Data Store.
How often should I clean data?
Check quality monthly and clean up at least twice a year.
Who should own customer data?
One named person or team, with each system having a clear owner.
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
