In this guide
- A server container can act as a light customer data layer: it receives events, remembers identifiers, enriches later events and routes them to many tools.
- With Open Tracked, the Data Store and the Enricher are the memory and the enrichment. Both are on every plan.
- It is not a full CDP. It lacks identity graphs and a big catalogue of destinations, but it covers the common needs of small and mid-size teams.
Customer data platforms promise one profile per customer and every tool fed from it. For many teams, the real needs are smaller: recognise a returning visitor, add the e-mail they gave before to later events so ad platforms can match them, send the same event to five tools. A server container does that, and costs far less. This page shows how to use one as a lightweight data layer. For the comparison with CDPs see CDP vs CRM.
What it needs
| Need | Building block |
|---|---|
| Receive events from the site and backends | The GA4 client and custom clients |
| Remember what a visitor gave | Data Store |
| Recognise the visitor later | A key: GA4 client ID, User ID or a cookie |
| Add remembered data to later events | Enricher |
| Keep cookies alive | Cookie Keeper |
| Add location and device | Visitor Location and Device Info |
| Send to many tools | Tags in the container |
| Respect consent | Consent settings and the Enricher's consent switches |
Brands that grow on cleaner data
Stores and agencies use Open Tracked to see which ads earn the sale.
A worked flow
A visitor gives an e-mail at checkout
The event carries the hashed e-mail and phone.
The Data Store keeps it
Under a key for that visitor, for the days you choose, up to 400.
They return and browse
The page view has no e-mail.
The Enricher adds it
The stored hashed e-mail and phone are added to the event.
Tags send richer events
Meta, TikTok, Google Ads and GA4 receive the enriched event.
A CRM stage arrives later
A webhook with the same key adds the stage and sends the offline conversion.
What you can build on this
Audience seeds
Send high-value events with customer data to build audiences.
Server-only events
Orders, refunds and CRM stages from your backend.
Consistent data for all tools
Clean the event once, send it everywhere.
Ask Ari instead of digging through reports
Ari reads your tracking and ad data and answers in plain words.
What it will not do
- Merge identities across many sources automatically.
- Store full customer profiles. The Data Store holds small, compact entries.
- Provide a large catalogue of ready-made destinations. You use Tag Manager tags.
- Replace a CRM.
Limits and cost
The Data Store holds 1,000 keys on Free, 50,000 on Pro, 500,000 on Business and 5 million on Enterprise. Every plan includes these power-ups. See the Data Store, the Enricher and every power-up.
Privacy
Remember only what you use, keep it as short a time as you can, and tie it to consent. Hashed identifiers are personal data. See GDPR and server-side tracking and customer data management.
A realistic example
A direct-to-consumer brand sells through its own shop and uses Meta, Google and TikTok. A third of its visitors return before buying. Before the change, returning visitors reached the ad platforms with no match data until the purchase. The brand turned on the Data Store and the Enricher in automatic mode, with the GA4 client ID as the key, and told the Enricher to remember hashed e-mail and phone. A visitor who joins the newsletter on Monday and returns on Friday now reaches Meta and TikTok with their hashed e-mail on every event in between. Match quality for add-to-cart rose, and the platforms could build better audiences from people who had not yet bought. The brand did not buy a CDP, and the whole set-up took an afternoon.
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.
Frequently asked questions
Can a server container replace a CDP?
For common small-business needs such as remembering visitors and enriching events, yes. It does not offer identity graphs or large destination catalogues.
What is a lightweight data layer?
A server container with a data store and enrichment that remembers identifiers and adds them to later events.
Which Open Tracked features make this possible?
The Data Store, the Enricher, Cookie Keeper, Visitor Location and Device Info, all on every plan.
How much can the Data Store hold?
From 1,000 keys on Free to 5 million on Enterprise.
Do I need consent?
Where the law requires it. Use the Enricher's consent switches.
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 · 6 min read
