Segments in Marketing Cloud Next: What Changes When Data 360 Is the Source

In Engagement, a segment is usually a query that writes rows into a sendable data extension. In Marketing Cloud Next, a segment is built on unified data in Data 360 and published on a refresh cadence. That difference sounds administrative. It changes how you plan.

Three habits to drop

• Writing a SQL activity and scheduling it just before the send. Publish cadence is a segment property now, not something you sequence by hand.
• Treating the data extension as the audience. The unified individual is the audience; the segment is a view of it.
• Solving data quality inside the segmentation step. Fix it at ingestion and mapping, because every segment reads the same foundation.

What to check on a new segment

• Which unified object it is built on.
• Its refresh cadence, and whether that matches how time-sensitive the campaign is.
• Whether consent is a filter on the segment or an exclusion at send — decide deliberately.

Based on current Salesforce documentation for Marketing Cloud Next segmentation. Verify behaviour against your release.