One plan for your customer data, before you buy the platform.

A customer data strategy: what to collect, how to recognise people, where it’s stored and which tools use it, written before any software is chosen.

Usually a fixed project, kept up afterwards within ongoing management if you want.

Sooner or later someone suggests a customer data platform. The demos are impressive and the price is serious. A year on, a good many of them hold a tidy copy of data nobody trusted in the first place.

A platform like that does two things at its core. It collects how people interact with you, across the channels you own and the ones you rent, and it joins that up into segments other tools can use. Whether you need to buy one depends on how far the tools you already have can go.

Often that’s further than expected. Analytics that works at the level of a person instead of a visit, a data warehouse you own, and audiences pushed back to the ad platforms cover a lot of the ground as an interim step.

What can’t be skipped is the plan underneath: one tracking plan across every touchpoint, tied to identities people have agreed to, stored somewhere you control. Get that right and you can change tools later without starting again.

This is for you if

  • You’re being sold a customer data platform and aren’t sure you need one.
  • Customer data sits in the website, the CRM, the email tool and the ad platforms, and none of it joins.
  • Each tool has its own tracking and its own name for the same thing.
  • You’re uneasy about depending on one vendor for everything.
  • Privacy changes have made your audiences smaller and your numbers less reliable.

A universal tracking plan

One specification for what’s recorded across web, app, stores, call centre, ads and email, using the same names everywhere.

Identity and consent

How a person is recognised across those places, tied to what they’ve agreed to.

Storage you control

A warehouse that holds it all in one consistent structure, so it can feed any tool and outlast any of them.

Then the tools

Which system serves each point of contact best. It’s rarely one vendor for everything.

How the work runs.

  1. Audit

    What’s collected today, where it lives, who can use it and what nobody trusts.

  2. Plan

    The universal tracking plan and naming, agreed across the teams that will use it.

  3. Identify

    How people are recognised across channels, and the consent rules that govern it.

  4. Store

    Where the data lands and how it’s structured, so it stays usable.

  5. Activate

    How segments get back to advertising, email, the website and service channels.

  6. Decide

    Whether the tools you have are enough, and what to buy if they aren’t, with the reasons written down.

Deliverables

What you end up with

  • Audit of current data and tools
  • Universal tracking plan
  • Identity and consent approach
  • Data storage design
  • Activation map: which segments go where
  • A recommendation on what to buy, if anything
  • A staged roadmap

Where AI comes in

The same thing under three names, spotted

AI helps compare how different tools describe the same data, draft the tracking plan from workshop notes and check it for conflicts. The recommendation on what to buy is mine, with the reasoning written down so you can test it.

How I use AI

Fair things to ask.

Something else? Ask me directly.

Do we need a customer data platform?

Maybe not yet. If your tracking plan is inconsistent, a platform will store the inconsistency. Fix the plan first, see how far your existing tools go, and buy when you hit a limit you can name.

Can Google Analytics do this?

Part of it. GA4 works at the level of the user, exports to a warehouse and shares audiences with Google’s ad products. It isn’t sold as a customer data platform and it’s weakest outside Google’s own tools, so I treat it as a useful interim step and not the destination.

Should we standardise on one vendor?

I’d be wary. One vendor is usually strong in advertising and analytics and weaker in the website, app or service channels, or the other way round. A plan that isn’t tied to a vendor lets you use the best tool at each point.

Who needs to be involved?

Marketing, whoever owns the website and the CRM, IT or data, and someone who can make decisions about privacy. The plan fails when one of those is left out.

Does this cover privacy law?

The plan is built around consent and around collecting only what you’ll use. It isn’t legal advice, and your legal adviser should check the parts that are.

Do you build it as well?

Yes for the tracking plan, the tagging, GA4, warehouse exports and audiences. For a full platform rollout I work alongside the vendor or your developers.

Something driving you mad?

Tell me what’s going on. I’ll come back with questions or a scoped proposal, and I’ll say so if I’m not the right person for it.