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

Contact Builder and Data Modelling

A Marketing Cloud Engagement data model built on a stable contact key, clear relationships and documented data extensions, so every journey and segment uses the same data.

Data modeller threads three colours of punched index cards onto one key ring while a colleague holds them

The Marketing Cloud Contact Builder data model decides what every journey, segment and personalised email can see. When it is designed well, a marketer can split a journey on a customer's latest order without writing SQL. When it is not, teams copy data into dozens of single-use data extensions, contacts are duplicated under different keys, and nobody can say which table holds the current value.

GeekMidst designs and repairs data models in Marketing Cloud Engagement, from the choice of contact key to the relationships in Data Designer and the processes that keep data current.

Signs your data model needs attention

  • The same person exists as several contacts because some sends used email address and others used a CRM ID as the subscriber key.
  • Journey decision splits cannot reach the data they need, so every journey depends on a custom entry data extension.
  • Data extensions have no primary keys, unclear names and no retention settings, and the contact count keeps growing.
  • Synchronised data from Salesforce and imported data disagree, and nobody knows which wins.
  • Deleting a contact for a privacy request is slow and uncertain because data is spread across untracked tables.
Isometric stack of storage, integration and entity layers, with related data entities on the top layer and a detailed entity card listing keys and fields

The decisions that shape the model

DecisionWhat to consider
Contact keyUse a stable, unique ID such as the Salesforce Contact or Lead ID, not email address, and apply it everywhere
Attribute groupsGroup related data extensions around the contact so journeys and filters can navigate them
RelationshipsSet cardinality correctly, one-to-one for profile data and one-to-many for orders or events
Primary keysEvery data extension needs keys that match its grain to prevent duplicate rows
Sendable data extensionsDefine the send relationship to Subscriber Key consistently
RetentionSet retention policies on transient and staging data so storage and contact counts stay controlled
Source of truthDecide which system owns each field and how often it refreshes
Data modeller linking customer tables on a glass board while colleagues follow

How Contact Builder fits together

Contact Builder links your data extensions to the contact record through attribute groups. Inside each group, Data Designer relationships say how one table relates to another, for example a customer profile linked to many orders, each linked to many order lines. Journey Builder and some filtering tools use those relationships to look up contact data at the point of decision, which is why an incorrect relationship can produce a split that quietly evaluates the wrong row.

If you use Marketing Cloud Connect, synchronised data extensions bring Salesforce objects into Marketing Cloud on a schedule. They are read-only in Marketing Cloud, so transformations usually happen in SQL Query Activities that write to your own data extensions. We cover common issues in Marketing Cloud Connect sync patterns and pitfalls.

Data extension design deserves its own care: primary keys, sendable fields and retention are the choices that most often cause trouble later.

How we approach a data model project

  1. 01

    Map sources and uses

    List every source feeding Marketing Cloud and every journey, segment and email that consumes data, so the model serves real needs.

  2. 02

    Audit the current state

    Check contact key usage, duplicate contacts, data extension keys, relationships, retention and automation that loads data.

  3. 03

    Design the target model

    Document the contact key, attribute groups, data extensions, relationships, refresh frequency and field ownership.

  4. 04

    Plan the transition

    Sequence changes so live journeys and automations keep running, including any contact key clean-up and re-pointing of sends.

  5. 05

    Build and validate

    Create or restructure data extensions and relationships, update loading automations and check row counts and sample contacts at each layer.

  6. 06

    Document and hand over

    Provide a data dictionary and diagram, and walk your team through how to add new data without breaking the design.

Workflow diagram

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

Workflow

Contact and subscriber data relationships

Open full size
Contact and subscriber data relationshipsA record arrives from CRM, an import or the API and is given a stable contact key. It is stored in a data extension keyed on that contact key, marked sendable by relating the key to Subscriber Key, and linked to the contact in an attribute group. At send time the All Subscribers status decides whether the email is sent or suppressed.Contact and subscriber data relationshipsSource systemsContact BuilderSend timeSubscriberYesNoRecord arrives: CRM, file or API. Contact data reaches Marketing Cloud from CRM synchronisation, file imports or API calls. Every route must use the same identifier for the same person.Record arrivesCRM, file or APIContact key assigned: Stable ID, never email. The contact key, which is also the subscriber key for email, should be a stable ID such as the CRM Contact or Lead ID. Email as a key creates duplicates when it changes.Contact keyassignedStable ID, never emailData extension: Primary key = contact key. Each data extension row carries the contact key in a primary key field. Use the same data type and length for the key everywhere it is stored.Data extensionPrimary key = contactkeyMarked sendable: Field relates to Subscriber Key. A sendable data extension has a send relationship that maps its key field to Subscriber Key, plus an email address field for the email channel.Marked sendableField relates toSubscriber KeyAttribute group: Linked in Data Designer. In Data Designer, attribute groups link data extensions to the contact through the key, one-to-one or one-to-many, so journeys can use the fields in splits.Attribute groupLinked in DataDesignerAll Subscribers: Status checked. At send time the subscriber status in All Subscribers is checked. New keys are added on first send, which is where a mismatched key becomes a duplicate.All SubscribersStatus checkedStatus active?. Only active subscribers receive commercial email. Unsubscribed, held and bounced statuses block the send even when the data extension row is present.Status active?Email sent: Tracked by key. The email is sent and tracking is stored against the subscriber key, so engagement links back to the same contact and CRM record.Email sentTracked by keySuppressed: Not sent. The subscriber is skipped for this send. Their status, not the data extension, decides this, so status must stay in step with CRM consent.SuppressedNot sentStartProcess stepDataSystem or platformDecisionEnd 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. Record arrives Source systemsCRM, file or API

    Contact data reaches Marketing Cloud from CRM synchronisation, file imports or API calls. Every route must use the same identifier for the same person.

    Next: Contact key assigned

  2. Contact key assigned Contact BuilderStable ID, never email

    The contact key, which is also the subscriber key for email, should be a stable ID such as the CRM Contact or Lead ID. Email as a key creates duplicates when it changes.

    Next: Data extension

  3. Data extension Contact BuilderPrimary key = contact key

    Each data extension row carries the contact key in a primary key field. Use the same data type and length for the key everywhere it is stored.

    Next: Marked sendable

  4. Marked sendable Contact BuilderField relates to Subscriber Key

    A sendable data extension has a send relationship that maps its key field to Subscriber Key, plus an email address field for the email channel.

    Next: Attribute group

  5. Attribute group Contact BuilderLinked in Data Designer

    In Data Designer, attribute groups link data extensions to the contact through the key, one-to-one or one-to-many, so journeys can use the fields in splits.

    Next: All Subscribers

  6. All Subscribers Send timeStatus checked

    At send time the subscriber status in All Subscribers is checked. New keys are added on first send, which is where a mismatched key becomes a duplicate.

    Next: Status active?

  7. Status active? Send time

    Only active subscribers receive commercial email. Unsubscribed, held and bounced statuses block the send even when the data extension row is present.

    Next: Yes: Email sent; No: Suppressed

  8. Email sent SubscriberTracked by key

    The email is sent and tracking is stored against the subscriber key, so engagement links back to the same contact and CRM record.

    End of the flow.

  9. Suppressed Send timeNot sent

    The subscriber is skipped for this send. Their status, not the data extension, decides this, so status must stay in step with CRM consent.

    End of the flow.

A record arrives from CRM, an import or the API and is given a stable contact key. It is stored in a data extension keyed on that contact key, marked sendable by relating the key to Subscriber Key, and linked to the contact in an attribute group. At send time the All Subscribers status decides whether the email is sent or suppressed. Original GeekMidst explanatory diagram; not an official Salesforce reference architecture.

Questions we hear

Should we use email address as the subscriber key?
Generally no. Email addresses change and are shared, so a stable ID from your CRM or customer system is a safer contact key. If you already use email address, we assess whether migrating is worth the risk.
Do we still need Contact Builder if we use Data Cloud?
Yes, if you send from Marketing Cloud Engagement. Data Cloud (now branded Data 360) can build unified profiles and segments, but activated audiences still land in data extensions that need a sensible model.
How do you handle data retention?
We set retention on staging and transient data extensions, agree retention periods for the rest with your privacy owner and document how contact deletion requests are handled.
Can you work in our live account?
We prefer a sandbox or test business unit for design and testing, then apply changes to production in planned steps with your approval.
What do you deliver at the end?
A data model diagram, a data dictionary, the configured data extensions and relationships, updated loading automations and a short operating guide.

Get your Marketing Cloud data model right

Tell us how data reaches Marketing Cloud today and where it causes problems. We will suggest whether an audit or a redesign makes sense.

Request a data model review →

Next step: Contact Builder and Data Modelling

  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