Open Tracked/Guides/Marketing data enrichment

Marketing data enrichment

Enrichment adds missing details to what you already know. Add from your own data first, and be careful with anything you buy.

4 min read · Updated October 26, 2026

EEvent with gapsEEnrichmentRRicher event
In this guide
Key takeaways
  • Enrichment adds fields to an event or a record: location, device, customer data you stored earlier.
  • First-party enrichment uses data you collected with consent. Third-party enrichment buys data from outside and carries privacy risks.
  • In Open Tracked the Enricher, Visitor Location and Device Info add first-party and CDN-derived data on every plan.

A page view with no information is hard to use. Enrichment fills in what is missing so the event is more useful to analytics and ad platforms. It comes in several kinds, with different risk. This page explains them and a safe approach. It follows the Enricher and a lightweight customer data layer.

Kinds of enrichment

KindSourceExampleRisk
TechnicalThe request and the CDNCountry, region, city from CDN headers; device and browser from the user agentLow. Check IP and location rules
First-party identityData you stored earlier with consentHashed e-mail and phone added to later events from the same browserModerate. Needs consent and retention rules
Business contextYour own systemsCustomer segment, order history, marginModerate. Use only what is needed
Third-partyA data providerCompany from an IP address, demographic dataHigher. Lawful basis and accuracy are harder
Data in, clean out

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.

First-party enrichment on the server

01

Visitor Location

Adds country, region, city and postcode from your CDN's location headers to events sent to Meta, TikTok and Google Ads.

02

Device Info

Adds operating system, browser and whether the visitor is on a phone, for richer GA4 reports.

03

Enricher

Adds stored hashed e-mail, phone and other fields you chose to later events from the same browser, with consent switches.

04

User ID

Sends an anonymous ID as external_id to Meta.

Third-party enrichment: cautions

  • Check that you have a lawful basis for using the data and telling people.
  • Test accuracy. IP-based company data is often wrong for remote and mobile visitors.
  • Avoid combining it with identifiers in ways visitors would not expect.
  • Document the vendor and the data in your records.
The short version

3 things to remember

Scroll and the points stack up.

01

Enrichment adds fields to an event or a record: location, device, customer data you stored earlier.

02

First-party enrichment uses data you collected with consent. Third-party enrichment buys data from outside and carries privacy ris

03

In Open Tracked the Enricher, Visitor Location and Device Info add first-party and CDN-derived data on every plan.

Do it safely

1

List the fields you want

And the decision each supports.

2

Prefer first-party sources

Collected with consent.

3

Apply consent and retention

Use the Enricher's consent switches and short retention.

4

Keep a record

What is added, where from, for how long.

5

Review twice a year

Remove fields you do not use.

0 of 5 done

A realistic example

A store wants better matching for returning visitors without buying data. It turns on Visitor Location and Device Info to add country, city and device details to events, and the Data Store and Enricher to add stored hashed e-mail and phone to later events from the same browser, with consent switches set to follow its banner. It tests with a purchase and a later page view, and checks Meta's event match quality for add-to-cart events, which rises over the following weeks. It decides against a third-party enrichment service after a test shows its company matches by IP address are wrong for many mobile visitors. The first-party route was cheaper, safer and more accurate, and it used data the visitors had given the store directly.

Trusted

Brands that grow on cleaner data

Stores and agencies use Open Tracked to see which ads earn the sale.

Frequently asked questions

What is marketing data enrichment?

Adding missing details to an event or record, such as location, device or stored customer data.

Is enrichment allowed without consent?

Technical enrichment is lower risk. Adding identifiers or customer data usually needs consent where the law requires it.

What does the Open Tracked Enricher do?

It adds stored customer data from the Data Store to later events from the same browser.

Is third-party enrichment risky?

It can be: lawful basis, accuracy and transparency are harder.

How do I start?

With technical fields and first-party data you already collect with consent.

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.

Open Tracked
Written by

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?

Write to us Read the docs

Was this article helpful?

Comments

Loading comments...

Turn better tracking into better marketing performance

Start free