Work that keeps running.

Pharma

A global consent model across dozens of business units

The challenge

An international pharmaceutical group running Marketing Cloud across dozens of business units, with healthcare professional (HCP) consent data spread across several enterprise sources, Veeva among them.

What we built

New business units created and set up. Marketing Cloud integrated with the group’s Master Data Management platform through an integration middleware, to centralise, standardise and distribute HCP consent. Email, SMS and WhatsApp consent flows from the Enterprise BU to every child BU through Shared Data Extensions and Automation Studio, with Veeva data models and Marketing Cloud automations updated to apply the latest available consent.

What changed

More accurate, traceable and consistent preference management worldwide. New markets roll out progressively, data stays segregated between business units, and local teams carry less operational load.

• Multi-BU
• Shared Data Extensions
• Automation Studio
• Veeva
• MDM
• WhatsApp

How it flows

1. 
   Veeva and sourcesHCP data
2. 
   MDM platformOne consent record
3. 
   MiddlewareIntegration layer
4. 
   Enterprise BUShared Data Extensions
5. 
   Child BUsEmail, SMS, WhatsApp

Banking

Marketing Cloud Personalization across app and web

The challenge

A major Italian banking group wanted personalised content in its iOS and Android apps and on the web, and wanted those moments to start Marketing Cloud journeys.

What we built

The integration architecture between Marketing Cloud Personalization and the digital channels: user tracking through the native SDK, Mobile Data Campaigns, Server-Side Campaigns for real-time personalised content, and Triggered Campaigns that enter users into Marketing Cloud journeys from personalisation events.

What changed

Personalised content in real time on app and web, journeys started by what customers actually do, with data security and one consistent customer identity across systems.

• MC Personalization
• Native SDK
• Server-Side Campaigns
• Triggered Campaigns
• Journey Builder

How it flows

1. 
   App and webiOS, Android, web
2. 
   Native SDKUser tracking
3. 
   PersonalizationReal-time decisions
4. 
   Server-side contentShown in app and web
5. 
   Triggered journeyIn Marketing Cloud

Events

From invitation to QR check-in

The challenge

Invitations, registrations and attendance lived in different places, so there was no single view of who was invited, who signed up and who actually came.

What we built

Invitation emails sent from Marketing Cloud, follow-up engagement until people request to register, a QR code sent to confirm each registration, and live check-in at the event that updates who is physically there.

What changed

All event data unified in one Salesforce platform, instead of being scattered across tools.

• Marketing Cloud
• Engagement journey
• QR codes
• Live check-in

How it flows

1. 
   InvitationEmail from Marketing Cloud
2. 
   EngagementUntil they ask to register
3. 
   RegistrationRequest received
4. 
   QR codeSent to confirm
5. 
   Live check-inAttendees updated

Motorcycle accessories

A data model rebuilt for a multinational

The challenge

A multinational in motorcycle accessories had data in external systems that no longer matched how the business worked in Salesforce.

What we built

External systems connected and their data reintegrated into Salesforce. The data model recreated and the whole Salesforce architecture adapted around it.

What changed

One data model the business can rely on, with external data flowing back into Salesforce instead of living beside it.

• Data model
• Integrations
• Salesforce architecture

How it flows

1. 
   External systemsWhere the data lived
2. 
   IntegrationConnected and mapped
3. 
   New data modelRecreated
4. 
   SalesforceData reintegrated
5. 
   ArchitectureAdapted around it

Email personalisation

Product recommendations inside every email

The challenge

The recommendation platform knew which products suited each customer. The emails had to show them, one customer at a time.

What we built

A dynamic AMPscript and HTML component that identifies the customer, calls the recommendation platform through dedicated endpoints and generates images and tracked links for each product. It accepts contextual parameters such as product, category, order and brand.

What changed

Every email carries recommendations personal to the reader, tracked product by product, in a responsive layout for desktop and mobile.

• AMPscript
• HTML
• Recommendation API
• Responsive email

How it flows

1. 
   CustomerIdentified at send
2. 
   ContextProduct, category, order, brand
3. 
   Recommendation APIDedicated endpoints
4. 
   ProductsImages and tracked links
5. 
   EmailDesktop and mobile

Data governance

A data retention policy, applied automatically

The challenge

Data retention had never been managed systematically, so Triggered Send Data Extensions kept data with no consistent rule.

What we built

A governance process that inventories Triggered Send Data Extensions through the API, records them in a control list and automatically applies a fixed 36-month retention, keeping track of the configurations already processed.

What changed

One uniform retention policy across the account, applied automatically and traceable over time.

• Marketing Cloud API
• Automation
• Data retention
• Governance

How it flows

1. 
   API scanTriggered Send DEs
2. 
   Control listEvery DE recorded
3. 
   Retention rule36 months
4. 
   AppliedAutomatically
5. 
   TrackedAlready-processed configs

Also delivered

1. AuditWhat runs today, and what it costs you.
2. DesignData model, journeys and channels on paper.
3. BuildInside your instance, in short iterations.
4. QAEvery path tested before a real contact enters.
5. HandoverDocumentation and a session with your team.
6. EvolveOptional support as the programme grows.