Skip to content
NEW: Martech, explained →

Martech, explained · Data foundations · 1:48

How consent travels across your stack

She said no once, and her data was already in five places: how a choice reaches every copy, and what gets in its way

Embed this film

Paste this where the film should play. It links back here.

The short answer

A customer's no is made in one tool, but her data lives in many: the CDP, the warehouse, the ad platforms, the CRM. Each copy has to hear it, by push (the change is sent to every tool) or pull (every tool checks one shared place first). Store consent as a dated field per purpose on the profile.

Questions this answers

Why does an unsubscribe not stop every tool?

Because the choice is made in one tool, but her data was already copied to others: the CDP, the warehouse, the ad platforms, the CRM. The email tool stops at once. Each other copy keeps acting on a yes that is gone until it hears the no.

What is the difference between push and pull for consent?

Push: the tool where she chose sends the change to every other tool as soon as it happens. It is fast, but every new tool needs its own connection, and one missing link is enough. Pull: every tool checks one shared place for the latest choice before it acts. Fewer connections, but every tool has to check, every time.

Where should consent live?

As part of the profile: a field per purpose, with a date, that travels with the person. Then every tool that holds a copy of her can read the same answer, and you can show when it was given or withdrawn.

What does identity have to do with consent?

If her email and her phone are two profiles, a no on one does not reach the other. Consent travels with the person only if the stack knows those two records are one person.

How long can a no wait?

As long as the slowest sync. A daily sync to the ad platform means a no can wait a day before the ad platform hears it, and she keeps seeing the ad until then. In a stack where consent travels, the ad stops the same day and the sales email never goes out.

Transcript

Every chapter as text. Click a time to play the film from there.

0:00 She said no once

A customer clicks unsubscribe. The email tool stops at once.

Three days later, she sees your ad. And a sales email from a different tool.

She said no once. Her data had already been copied to five places.

0:18 Every copy needs the no

That's the part of consent nobody draws. The choice is made in one tool, but her data lives in many: the CDP, the warehouse, the ad platforms, the CRM.

Each copy needs to hear the no, or it keeps acting on a yes that's gone.

0:35 Push or pull

There are two ways to make that happen.

Push: the tool where she chose sends the change to every other tool, as soon as it happens.

It's fast, but every new tool needs its own connection, and one missing link is enough.

Pull: every tool checks one shared place for the latest choice before it acts.

Fewer connections, but every tool has to check, every time.

1:02 Consent in the profile

Either way, consent works best as part of the profile: a field per purpose, with a date, that travels with the person.

It also depends on identity. If her email and her phone are two profiles, a no on one doesn't reach the other.

Then there's timing. A daily sync means a no can wait a day before the ad platform hears it.

1:28 One choice, every tool

Back to her unsubscribe. In a stack where consent travels, the ad stops the same day, and the sales email never goes out.

One choice, every tool. That's the whole idea.

Learn more at Martech Stack Builder, or build your own.