DATA 360 / SEGMENTATION & ACTIVATION
Segmentation & Activation
Building segments that hold up, activating them where they do work — including back into Marketing Cloud Journeys — and the data actions that make activation real-time.
Foundation · 2
Production note
Segmentation & activation gotchas: where a segment stops being potential energy
A Data 360 segment is potential energy until it activates — and the central decision is batch publish versus real-time data action. Ten segmentation and activation gotchas, each with the question to answer first and the cost of getting it wrong. Two threads run through all of them: consent at the activation boundary, and the bridge from a Data 360 segment to a Marketing Cloud Journey.
Decision framework
Data 360 Segmentation & Activation: Style Guide
The opinionated rules Cleon applies to every Data 360 activation decision — the batch publish vs. real-time data action call at the center, the target discipline, the cost and freshness discipline, consent enforced at the boundary, the patterns to prefer and the ones to refuse, plus a pre-ship checklist for any segment or activation. The discipline document that ties the Segmentation & Activation subcategory together.
Reference · 5
Reference
Building a segment: the membership rules before it activates anywhere
How a Data 360 segment is built: the object you segment on (typically the unified individual), the container-based AND/OR rules that define membership, filtering on Calculated Insights and related-object attributes, and the refresh cadence that decides how fresh the membership is. Building the audience only — where it activates is a sibling page.
Reference
Activation targets: where a Data 360 segment goes, and what travels with it
A segment is potential energy until it activates somewhere it does work. This is the target decision: what an activation target is, the destination types Data 360 supports, and the activation object plus attributes that decide what data actually rides along to the channel.
Reference
Batch vs. real-time activation: scheduled segment publish or a real-time data action
The decision the whole subcategory turns on: a scheduled segment publish recomputes a whole audience on a cadence and ships it to an activation target; a real-time data action fires off a single data change as it happens. One answers 'who, as of the last run'; the other answers 'react now to this one change'. The two mechanisms, their real limits, and how to tell which one a requirement actually needs — the exact parallel to the query layer's Calculated-Insight-vs-live-Query call.
Reference
Activating into Marketing Cloud: the bridge that connects the two platforms most clients run
Cleon's signature bridge: a Data 360 segment activating into Marketing Cloud Engagement so a Journey can act on it. There is no direct segment-to-Journey pipe — the handoff is a shared, sendable Data Extension. The data flow, the two clocks that govern it, the contact point it keys on, and the attributes that ride along carrying their own freshness.
Reference
Consent and activation: making the opt-out physically un-activatable
Segment logic is consent-blind: a segment built on behavior will include a person who opted out, and the activation will send them — unless consent is enforced at the activation boundary. This is where it gets enforced: Contact Point Filtering, backed by the Contact Point Consent DMO, filtering on consent status and data-use purpose so a non-consenting person is excluded from what ships. Cleon's stance is compliance by design — model consent alongside the data and make the safe path the only path.