ServicesSalesforce consultingArchitectureImplementationOrg health checkDevelopmentIntegrations and APIsData migrationTesting and QAManaged supportSpecialist supportMarketing Cloud auditDeliverability
SolutionsMarketing Cloud EngagementMarketing Cloud NextSalesforce + BrazeAccount EngagementData Cloud (Data 360)Identity resolutionInsights and segmentsAgentforce and AIMCP integrationsSales and Service CloudReal-time personalisationIntegration solutionsEnterprise AI integrationBy industry
ArchitectureSalesforce CRMData 360Salesforce + BrazeAgentforceCustomer 360API-led integrationEvent-drivenMCP host, client and serverIdentity and consentMCP securityData governanceCI/CD and releasesOur public MCP server
ResourcesEngineering journalDecision guidesSolution blueprintsSalesforce productsProjects and achievementsSales ROI calculatorWhere we workChecklists and templatesPlanning toolsReadiness assessmentGlossaryAbout GeekMidstOur approachOur expertiseContact
CompanyAbout GeekMidstOur approachDelivery methodologyTrust and evidenceProjectsAchievementsBook a consultationContactWhere we workSecurity and data
Book a Consultation

Audience Segmentation and Personalisation

Segments built from behaviour and value rather than guesswork, personalisation that degrades gracefully when data is missing, and holdout tests to show whether any of it helps.

Analyst sorts coloured marbles into three glass bowls with a small fourth bowl set aside as a colleague counts

Most teams segment by whatever field is easiest to filter on, then personalise with a first name and call it done. Real gains come from audiences defined by behaviour and value, content that changes for reasons a customer would recognise, and testing that shows whether the extra effort earned anything. Marketing Cloud segmentation and personalisation work best when the data, the rules and the measurement are designed together.

GeekMidst helps marketing and CRM teams define useful segments, build them in Marketing Cloud Engagement or Data Cloud (now branded Data 360), and personalise content in a way that is maintainable.

Workflow diagram

Explore how the pieces fit together. Select a step to read what happens there.

Workflow

Audience segmentation workflow

Open full size
Audience segmentation workflowMarketing agrees a segment brief, then the builder chooses a filter activity for simple rules or a SQL query activity for joins and ranking. The result lands in a segment data extension with suppressions applied, counts and samples are checked against the brief, and only a matching segment is used in journeys or sends.Audience segmentation workflowMarketing opsFilter activitySQL queryData extensionsYesNoYesNo, refine rulesBrief agreed: Rules, exclusions. Marketing and the builder agree the rules in plain words, including exclusions, consent, time windows and the expected size, before anything is built.Brief agreedRules, exclusionsSimple rules only?. Filters suit simple attribute rules on one data extension. Joins across tables, ranking or date logic need a SQL query activity instead.Simple rules only?Data filter on a DE: Attribute rules, no code. A filter activity applies attribute rules to one source data extension and writes the result. Marketers can maintain it without writing SQL.Data filter on a DEAttribute rules, nocodeSQL query: Joins, ranking, dedupe. A query joins orders, engagement data views and profile data, keeps one row per contact with ROW_NUMBER and overwrites the segment table.SQL queryJoins, ranking,dedupeSegment data extension: Exclusions applied. The output holds one row per contact key with the fields the send needs. Global suppressions and consent exclusions are applied here, not later.Segment dataextensionExclusions appliedCounts checked: Samples vs brief. Someone compares the count with the expected size and opens sample records. A big swing from the last run usually points to a source data problem.Counts checkedSamples vs briefMatches the brief?. Only a segment that matches the brief moves on. A mismatch goes back to the rules rather than being patched by hand in the data extension.Matches thebrief?Segment ready: Journey or send. The segment becomes the entry source for a journey or the audience for a send, and its automation refreshes it on schedule.Segment readyJourney or sendStartDecisionProcess stepDataPerson or teamEnd or outcomeOriginal GeekMidst explanatory diagram, not an official Salesforce reference.

Select any step in the diagram, or use Step through, to see what happens at that point and why.

Text version: every step in order
  1. Brief agreed Marketing opsRules, exclusions

    Marketing and the builder agree the rules in plain words, including exclusions, consent, time windows and the expected size, before anything is built.

    Next: Simple rules only?

  2. Simple rules only? Marketing ops

    Filters suit simple attribute rules on one data extension. Joins across tables, ranking or date logic need a SQL query activity instead.

    Next: Yes: Data filter on a DE; No: SQL query

  3. Data filter on a DE Filter activityAttribute rules, no code

    A filter activity applies attribute rules to one source data extension and writes the result. Marketers can maintain it without writing SQL.

    Next: Segment data extension

  4. SQL query SQL queryJoins, ranking, dedupe

    A query joins orders, engagement data views and profile data, keeps one row per contact with ROW_NUMBER and overwrites the segment table.

    Next: Segment data extension

  5. Segment data extension Data extensionsExclusions applied

    The output holds one row per contact key with the fields the send needs. Global suppressions and consent exclusions are applied here, not later.

    Next: Counts checked

  6. Counts checked Marketing opsSamples vs brief

    Someone compares the count with the expected size and opens sample records. A big swing from the last run usually points to a source data problem.

    Next: Matches the brief?

  7. Matches the brief? Marketing ops

    Only a segment that matches the brief moves on. A mismatch goes back to the rules rather than being patched by hand in the data extension.

    Next: Yes: Segment ready; No, refine rules: Brief agreed

  8. Segment ready Marketing opsJourney or send

    The segment becomes the entry source for a journey or the audience for a send, and its automation refreshes it on schedule.

    End of the flow.

Marketing agrees a segment brief, then the builder chooses a filter activity for simple rules or a SQL query activity for joins and ranking. The result lands in a segment data extension with suppressions applied, counts and samples are checked against the brief, and only a matching segment is used in journeys or sends. Original GeekMidst explanatory diagram; not an official Salesforce reference architecture.
Triggers such as cart activity and events start a journey that moves across email, SMS, push and web lanes, splitting into a follow-up path

The questions we help you answer

  • Which customer groups behave differently enough to deserve different messages?
  • Where should each segment be built: SQL in Marketing Cloud, filters, or Data Cloud?
  • How much personalisation is worth maintaining, given the data you actually have?
  • How will you know whether a segment or a personalised block improved results?

What we deliver

Marketers grouping customer profile cards into segments on a glass wall

A worked example: repeat buyers in the last 180 days

A common first segment is customers who have bought at least twice recently. In Marketing Cloud Engagement this is usually built with a SQL Query Activity that writes to a target data extension on a schedule.

Assumptions: a Customers_DE data extension keyed on SubscriberKey, an Orders_DE data extension with one row per order, and a target data extension Repeat_Buyers_180D with SubscriberKey as its primary key and the query set to overwrite.

sql
SELECT
    c.SubscriberKey,
    c.EmailAddress,
    COUNT(o.OrderID) AS OrderCount,
    MAX(o.OrderDate) AS LastOrderDate
FROM Customers_DE c
INNER JOIN Orders_DE o
    ON o.SubscriberKey = c.SubscriberKey
WHERE o.OrderDate >= DATEADD(DAY, -180, GETDATE())
GROUP BY c.SubscriberKey, c.EmailAddress
HAVING COUNT(o.OrderID) >= 2
Sample segment query for a Query Activity. Field and data extension names are examples.

Subscription status is still checked at send time against All Subscribers and any publication lists, but it is good practice to exclude known suppressions in the query too, so audience counts match what will actually be sent. If several sources feed the order table, deduplicate it first, typically with ROW_NUMBER() partitioned by order ID.

Personalisation in layers

We think about personalisation as layers, adding each one only when the data supports it:

  1. Relevance by segment. Different content blocks for clearly different groups, using dynamic content rules.
  2. Attribute personalisation. Names, locations, tier or account details, always with a fallback.
  3. Behavioural content. Recently viewed or purchased categories, using lookups against data extensions refreshed on a known schedule.
  4. Predictive features. Einstein features such as send time optimisation or content selection, where your edition includes them and you have enough data for them to be useful.

Each layer adds maintenance. A segment that nobody can explain, or a block that depends on a feed that breaks monthly, costs more than it returns.

Measuring honestly

For any new segment or personalised element we agree a holdout or control group before launch, record a baseline, and compare like with like after a set period. Open rates are a weak measure because of mail client privacy features, so we prefer clicks, conversions and downstream revenue where they can be tracked.

How the work runs

  1. 01

    Data and goals review

    Look at the data available, its freshness and quality, and the commercial goals each segment should support.

  2. 02

    Segment framework

    Agree a small set of segments with definitions, priority rules for overlaps and an owner for each.

  3. 03

    Build

    Create the queries, filters or Data Cloud segments, plus refresh schedules and exclusion logic.

  4. 04

    Personalise

    Add dynamic content and AMPscript to templates with fallbacks, and test with edge-case records.

  5. 05

    Measure and refine

    Run holdouts, review results with your team and retire segments that do not earn their place.

Questions we hear

Should we build segments in Marketing Cloud or Data Cloud?
It depends on where the data lives and how many sources need combining. SQL in Marketing Cloud suits data already there; Data Cloud suits audiences that need several unified sources.
How many segments should we have?
Fewer than most teams expect. A handful of well-defined segments with clear content differences is easier to run and measure than dozens of overlapping ones.
What happens when personalisation data is missing?
Every dynamic element gets a fallback, and we test with records that have empty or unusual values before anything is sent.
Can you personalise journey emails as well as campaigns?
Yes. The same segment logic and content blocks can be used in Journey Builder, with entry data and decision splits designed to match.
Do we need consent for personalisation?
Using customer data to personalise marketing has consent and privacy implications that depend on your markets and lawful basis. Your privacy or legal team should confirm the approach; we build to the rules they set.

Plan segments and personalisation that pay off

Tell us what data you have and what you want customers to do next. We will suggest a practical starting set of segments and how to test them.

Talk to a segmentation specialist →

Next step: Audience Segmentation and Personalisation

  1. We read it A practitioner reads your message and replies by email.
  2. Short call We confirm goals, constraints and what success looks like.
  3. Written scope You get a scope and estimate before any work starts.

Tell us what you are trying to fix.

Share your Salesforce setup, goals and constraints. A practitioner reads every message and replies with questions, first thoughts or an honest view of whether you need outside help at all.

Talk to a Salesforce Expert
Book a Consultation