Marketing Cloud implementation, done in order
A structured Marketing Cloud Engagement implementation that gets the foundations right first: account setup, sender identity, data model, integration and your first live programmes.
A new Marketing Cloud Engagement account is a blank space with many decisions hidden inside it. The subscriber key you choose, how business units are structured and how CRM data arrives will shape every send for years. Changing these later is possible but expensive, so a good Marketing Cloud implementation makes them deliberately and early.
GeekMidst implements Marketing Cloud for organisations launching for the first time, moving from another email platform, or rebuilding an account that was set up quickly and never revisited.
What makes implementations go wrong
- Subscriber key chosen by accident. Using email address as the key feels simple until someone changes their email and becomes two contacts.
- Sender identity left until the end. Domain authentication and the sending domain need DNS changes that involve other teams and take time to agree.
- Integration bolted on. Marketing Cloud Connect or file feeds are configured after journeys are designed, so journeys assume data that never arrives in the right shape.
- No operating model. The account goes live, but nobody knows who approves sends, who monitors automations or who handles unsubscribes from other systems.
Implementation phases
- 01
Discovery and design
We confirm use cases, channels, audiences, consent rules and source systems, then agree the subscriber key, business unit structure and data model on paper.
- 02
Account and sender setup
Business units, users and roles, sender profiles, delivery profiles and domain authentication are configured, coordinating DNS changes with your IT team.
- 03
Data foundation
Data extensions, relationships in Contact Builder and import or sync routines are built and loaded with test data first, then validated against source counts.
- 04
Integration
Marketing Cloud Connect or file-based feeds are configured with clear rules for which objects and fields sync and how often.
- 05
First programmes
We build a small number of priority journeys and automations end to end, such as a welcome series and a newsletter, to prove the foundation.
- 06
Testing and launch
Seed lists, test sends, content checks on real data shapes and a controlled first live send with monitoring.
- 07
Handover
Runbooks, a data dictionary and training sessions so your team can operate and extend the account.
Workstreams we cover
Data model and Contact Builder
Keys, relationships and retention designed for how you segment.
→CRM integration
Marketing Cloud Connect sync design and the pitfalls to avoid.
→Journeys and automations
Lifecycle journeys and the automations that feed them.
→Templates and content
Modular email templates with tested personalisation.
→Deliverables by phase
| Phase | What you receive |
|---|---|
| Discovery | Use case list, solution design, data model diagram and agreed subscriber key strategy |
| Setup | Configured business units, roles, sender and delivery profiles, authentication records for your DNS team |
| Data | Built data extensions, import or sync routines, load validation report |
| Programmes | Live priority journeys and automations with design notes |
| Launch | Test evidence, launch checklist and monitoring plan |
| Handover | Runbook, data dictionary and recorded training |
What we need from you
An implementation is a shared piece of work. To keep it on track we ask for:
- A product owner who can make decisions on audiences, consent and priorities within a few days, not weeks.
- Contacts in IT for DNS changes and in the CRM team for Marketing Cloud Connect permissions and field access.
- Source data samples early, with an agreed way to handle them. We prefer anonymised or test data wherever possible.
- Brand assets, approved copy and legal footer text for the first programmes.
- Agreement on who will run the platform after launch, so training is aimed at the right people.
If you are moving from another email platform, data and history migration becomes its own workstream. Our Migrating from a Legacy ESP to Marketing Cloud blueprint describes how we approach it, and the Salesforce Implementation Checklist is a useful companion for planning.
Questions we hear
How long does a Marketing Cloud implementation take?
Should we use email address as the subscriber key?
Do we need Marketing Cloud Connect?
Can you migrate our existing subscribers and unsubscribes?
Will our team be able to run it afterwards?
Plan your Marketing Cloud implementation
Share your channels, data sources and launch goals, and we will outline a realistic phased plan.
