Skip to main content Back CRM Cloud Mastery Sign up Create account

Segmentation, Activation & Consent

Segments that survive six months, activation as a promise to another system, and honouring the customer's no.

  • Intermediate
  • 23 lessons
  • 6 modules
  • English

Designed and created by Salesforce Expert

What you'll learn

  • Design a segment against a business question, not a field list
  • Keep a segment correct as the underlying data drifts
  • Activate to a downstream system and know what you have promised it
  • Model consent so a customer's refusal is actually honoured
  • Act on the data without becoming the reason somebody unsubscribes

Course content

6 sections · 23 lectures · 9 hands-on labs

The catalogue that went to Nessa three times 3 lectures
  1. 1.1 Three Emails, One Customer, and Four Things That Were Each Working Correctly
  2. 1.2 What You Already Built, What This Course Adds, and an Honest Read of the Exam
  3. 1.3 From "Send Something to Our Lapsed Customers" to a Specification Somebody Can Build
Designing an audience that survives contact with the business 5 lectures
  1. 2.1 What You Segment On Decides What You Can Ask, and Unified Individual Is Not Always the Answer
  2. 2.2 Hands-On: Build Ingleby's Win-Back Audience, Exclusions First Hands-on
  3. 2.3 Audiences That Fight Each Other: Overlap, Mutual Exclusion, Priority, and the Suppression Set That Outranks Them All
  4. 2.4a Hands-On: Size It, and Preview It Under a Governance Policy Hands-on
  5. 2.4b Hands-On: Defend the Number to Nasreen Hands-on
Living with a segment for six months 4 lectures
  1. 3.1 Membership Over Time: Adds, Removes, Persists, and the Six Reasons a Count Moves
  2. 3.2H Hands-On: Schedule, Refresh, Recount and Publish — What Each Control Actually Causes Hands-on
  3. 3.3 The Segment Estate Nobody Prunes: Naming, Ownership, Data Spaces and the Cost of a Segment That Still Runs
  4. 3.4H Hands-On: Diagnose the Audience That Collapsed to Nine People Overnight Hands-on
Activation is a promise to somebody else's system 4 lectures
  1. 4.1 The Payload Is an Interface
  2. 4.2H Hands-On: Publish the Autumn Catalogue Audience Hands-on
  3. 4.3 Why the Activation Count Is Lower Than the Segment Count
  4. 4.4H Hands-On: Read the Delta Hands-on
Honouring the no 4 lectures
  1. 5.1 Consent Is a Claim You Can Prove
  2. 5.2 The Suppression Path, End to End
  3. 5.3H Hands-On: Prove She Is Gone Hands-on
  4. 5.4 Deletion, Retention, and the Questions Maeve Will Ask
Acting on the data 3 lectures
  1. 6.1 Activation, Data Action or Flow
  2. 6.2H Hands-On: Data 360 Inside a Salesforce Flow Hands-on
  3. 6.3 What You Can Now Do, and What the Exam Actually Asks

Requirements

  • DATA-101 Data 360 Fundamentals, or equivalent
  • A Data 360 enabled org

Description

It opens with a catalogue that went to the same person three times. This course is about the half of Data 360 that touches real customers: designing an audience that survives contact with the business, living with a segment for six months as the data drifts, and activation — which is a promise made to somebody else's system.

The consent module is the one most implementations skip. Honouring the no is treated here as a design requirement, not a checkbox.

Who this course is for

  • Marketing operations and Data 360 practitioners who own audiences and activations.

Skills you'll practise

SegmentationActivationConsent managementData 360Audience designMarketing operations

Related reading