Client
Pottsalat GmbH
Unit
prodct [Elements] · + /skills
Duration
4 months · 2022
Shape
Rollout · event & identity plumbing
Headline
Segment CDP as Pottsalat's single source of customer truth — unified identity, clean events, activation surfaces wired to real channels.
// prodct [Elements] case · Pottsalat · 2022 · food delivery · CDP rollout

Data scattered.
One clean source of truth.

Every team was deciding from a different slice of customer reality — ordering from one dashboard, marketing from another, ops from a spreadsheet. We rolled out Segment end-to-end: a governed event tracking plan, one identity model, clean destinations. The customer record became a shared asset — not a negotiation.

16 wk
// kickoff → Segment live in production
// on plan
1 identity
// unified user across web, app, orders, CRM
// no duplicate profiles
Governed
// tracking plan + QA + protocols enforced at the pipe
// no event drift
// 01 / the situation

Three dashboards. Three different customers.

Every team had its own view of the customer — and no two agreed. Ordering events didn't reach marketing; CRM profiles didn't match the app; ops ran on spreadsheet exports from last week.

The ask wasn't "add more dashboards." The ask was to end the negotiation over which number was real — and do it without freezing the product team.

  • 01

    Identity fragmented across surfaces.

    Same customer, three IDs, no stable join key.

  • 02

    Events drifted from their definitions.

    Naming, properties, timing — all decided per feature, never reconciled.

  • 03

    Activation stuck in exports.

    Marketing ran on yesterday's CSV, not today's signal.

// 02 / approach

Tracking plan first. Then the plumbing.

Before a single event fired through Segment, we wrote the tracking plan — with the teams that actually use the data. Names, properties, types, when they fire, what they mean. The plan became the contract.

Then the plumbing: Segment sources on every surface, a governed identity resolution layer, destinations wired to the tools each team already runs.

  • A

    Tracking plan owned by the teams that consume it.

    Marketing, product, ops — in the same room, before a line of code.

  • B

    Identity resolution as a first-class concern.

    Deterministic joins where possible; stable anonymous IDs where not.

  • C

    Destinations wired to existing tools, not new ones.

    Activation inside the stack the teams already operate — no retraining tax.

// 03 / what we built

A tracking plan, three live surfaces, a governed pipe.

[Contract]
Tracking plan · v1
Every event, property, type, and firing condition — owned jointly by marketing, product and ops. Enforced in Segment Protocols.
[Source]
Web + app + server sources
Instrumented the storefront, mobile app, and backend order events. Same user, same identity, across surfaces.
[Identity]
Resolution + merge logic
Deterministic on authenticated users; stable anonymous chain pre-login. Merge on identify, not on guesswork.
[Destinations]
CRM, email, analytics, warehouse
Wired to the tools each team already runs — plus a clean warehouse load for the ad-hoc questions nobody predicted.
// 04 / outcomes

One customer. Shared by every team.

16 wk
// kickoff to Segment live in production
// on plan
1 plan
// tracking plan governs every event across surfaces
// no event drift
3 surfaces
// web, app, backend — one identity, one event vocabulary
// unified
Warehouse ready
// clean load for ad-hoc analysis on day one
// no afterthought
// similar engagement?

Every team on a different customer? We end that negotiation.