Tag Archive for: Marketing automation

AI Will Not Fix Broken Marketing Operations. It Will Expose Them.

, , , , , , ,

For CMOs, CDOs, and marketing operations leaders, the question is not if AI can create value. The question is whether the business has the data, systems and workflows, governance, and measurement model needed to turn AI into measurable value (and growth).

What You’ll Learn

  • Why AI value depends on the operating model behind the marketing function.
  • Why unified customer data, APIs, governance, and measurement matter more than another isolated AI tool.
  • How leaders should assess AI-readiness across data, MarTech, teams, privacy, and business-value measurement.

I number of Marketing leaders I’ve spoken to all share a similar story; they’re under pressure to do more with less: move faster, to more with less, prove marketing value and ROI, reduce headcount, and support sales yesterday.

AI can help. But AI does not create value on its own.

It all needs the right foundation: clean customer data (1st party data), connected systems, sound governance, usable assets and content, and people that know how to operationalize it into action.

That is where modern marketing is changing.

The role of marketing is no longer limited to campaigns, content, and channels. That stopped almost 10 years ago and SME’s and SMBs are now catch up with the same realization.

IToday, marketing often sits at the hub of customer experience, data, MarTech, automation, channel execution, personalization and revenue growth.

Combined with leadership over Sales, you know have a full-bench team of Revenue Ops.

For CMOs and digital leaders, the question I’m hearing is not “Which AI tool should we buy?” It is “Is our what use-case should we apply it too?” and “Where should we deploy AI in a way that improves what’s most important to our team; revenue, efficiency, or customer experience?”

Adobe’s 2026 AI and Digital Trends research points to this same gap: many organizations want to learn AI and how to scale generative and agentic AI.

But what is still lacking are the tools and internal guardrails to allow employees to unleash AI in their function or area. While the desire is there among teams, they lack the tools, data structures, content workflows, and measurement practices needed for broader deployment beyond their functional areas.

That is the real issue. Most companies do not have an AI problem. They have an operating model problem.

The old MarTech problem has become an AI-readiness problem

For years, companies invested in CRM, marketing automation tools (ex. Klavyio, Marketo, Eloqu, HubSpot), analytics, websites, eCommerce, explored CDPs, data warehouses, and campaign tools.

Many of those investments created value. Many also created complexity and the necessity for more training, skills and time.

Customer data sits in too many systems across an oraganization.

Recognizing 2nd and 3rd party data has been untapped to reaper deeper insights, deeper segmentation, deeper personalization or deeper look-a-like models.

Marketing operation teams executing campaigns use different tools for different things.

Sales and marketing do not always share the same customer view.

Reporting is slow.

Personalization is limited.

Attribution is unclear.

And content production cannot keep up with channel demand.

Now AI is being added on top of this stack.

That creates risk. AI can accelerate good systems and processes, but it can also accelerate bad ones.

If the data is fragmented and has little to no oversight, AI works from an incomplete picture.

If content workflows are weak, AI creates more output without better quality, which defeats anyone trying to test AEO and GEO.

If governance is unclear, AI can introduce brand, privacy, compliance, or trust issues.

The smarter path is to treat AI as part of a larger digital growth architecture.

The AI-Ready Marketing Operating System

MJ Digital’s point of view: AI-ready marketing needs five connected layers. If one layer is weak, the value of every AI use case is limited.

Layer

What it means

1. Unified customer data

Connect the signals that matter across CRM, web analytics, marketing automation, eCommerce, product data, sales activity, customer service, campaign engagement, and first-party behavior.

2. Connected MarTech and APIs

Move data and decisions across websites, CRM, automation, CDP, analytics, advertising, eCommerce, service, and reporting systems.

3. Cross-functional operating model

Align marketing, sales, data, IT, product, CX, and compliance around shared workflows, ownership, KPIs, and decision cadences.

4. Trust, consent, and privacy by design

Build personalization on transparent consent, preference management, data governance, and responsible AI usage.

5. Measurement tied to business value

Measure AI and automation against revenue, cost, speed, CX, productivity, lead quality, and customer value — not tool usage alone.

1. Unified customer data

This does not mean collecting more data for the sake of it. It means creating a usable customer and account view that helps the business understand who the customer is, what they need, what they have done, and what action should happen next.

Tip: This often involves creating a scaleable identity identity resolution model, profile unification and converting anonymous-to-known vistor stitching and consent and preference management.

This is where a Customer 360 strategy comes into play, enabled by a CDP solution (or Marketing-specific CDP solution; Marketing Data Services Platform),  data clouds (ex. Azure, Google Cloud, Amazon AWS, Snowflake, etc.) data lakes, warehouses, and composable data models (ex. flexible, connected components like lego blocks for data) enter the conversation.

For example, Adobe Real-Time CDP is positioned around harmonizing customer and account data from multiple sources and activating audiences in real time for more relevant experiences. 

Others, with the capital and will can build their own home-grown CDP-like solution that plays friendly with their existing MarTechs and systems.

But the key decision is not  “Should we buy a CDP?”

The better question is: What use-cases would deliver real business value, what customer data do we need to activate, where should it live, who owns it, how will it be activated and orchestrated, and how will it create measurable business value?

For some organizations, a packaged CDP is the right move. For others, a warehouse-native or composable model built around platforms like Snowflake, Databricks, BigQuery, Azure, or AWS may be a better fit.

For example, once national automative brand were handcuffed to over 30 OEM compliant tools that must be adopted across their dealer ecosystem.

Although far far better and cheaper tools would be common sense, a compliance-driven organization can be forced to use the tools they have.

In this example a composable CDP approach would work best to ensure the flexibility supports the build and management of a durable customer data foundation in a lakehouse for consuming and operationalizing data for business insights, segmentation, personalization, attribution and AI-driven use-cases.

The point is not the platform. The point is the business outcome.

Unified data should help marketing and sales improve for segmentation, personalization, lead scoring, churn prevention, campaign ROI, customer experiences and overall KYC (know your customer). 

2. Connected MarTech and APIs

Data only creates value when it can move.

That is why APIs and integrations matter. They connect the systems that run the customer journey: websites, CRM, marketing automation, CDP, analytics, advertising platforms, eCommerce, call tracking, customer service, and reporting tools.

Without that connectivity, teams stay trapped in manual work.

They export lists. Rebuild reports. Move data between systems. Recreate audiences. Chase inconsistent numbers. Launch campaigns without knowing which customer signals should guide the next action.

A connected MarTech stack gives teams a better operating layer. It lets the business trigger customer experiences and send real-time high-intent signals to Sales.

A connected MarTech triggers emails, SMS, personalize website experiences, route leads, suppress irrelevant audiences and enrich customer profiles.

This is where AI becomes practical. AI can help summarize insights, recommend segments, predict intent, generate content variations, automate workflows, and support next-best-action decisions — but only when the data and systems are connected enough to act.

3. Marketing, data, and technology teams working as one system

The modern marketing team cannot operate alone.

AI-enabled marketing requires marketing, sales, data engineering, data science, IT, product, CX, and legal/compliance to work from the same operating model.

Marketing brings the customer context.

Sales brings account and pipeline intelligence.

Data teams bring architecture and quality control.

IT brings integration, security, and platform governance.

CX and product teams bring journey insight.

Compliance protects consent, privacy, and risk.

The modern marketer becomes the translator and orchestrator across these teams — not the owner of everything, but the connector.

That is a major shift. The best marketing leaders are now building operating models, not just campaign calendars. They are creating shared workflows, KPI definitions, governance rules, content systems, data models, and performance cadences.

This matters because AI value is rarely created by a tool in isolation. It is created when the workflow changes.

The greatest revenue benefits from AI are most often seen in marketing and sales, strategy and corporate finance, and product or service development.
McKinsey’s 2025 State of AI Research Report

4. Trust, consent, and privacy by design

Personalization only works when customers trust the experience.

That means marketing teams need stronger consent, preference, and data governance, and this moreso with legal compliance requirements driven by  GDRP, CASL and CCPA / CPRA; how customers; privacy and communication laws governing how the business collect, use, protect, and get permission to contact people with personal data or marketing messages, and its data retention and access.

So if data is the currency, these compliance regulations are the rules of the financial system.

This cannot be ignored as first-party data is your organizations gold. It’s valuable, but only when it is collected, stored, and used responsibly.

Customers want relevance, but they also want transparency, control, and security. For marketing teams, privacy is no longer a legal checkbox. It is part of the customer experience.

Consent should connect to personalization, communication preferences, advertising, email, SMS, customer profiles, and AI usage. If a company wants to use customer data for better experiences, it needs a clear value exchange and a governance model that protects trust.

5. Measurement tied to business value

AI and MarTech programs fail when they are measured only by activity.

More content. More campaigns. More dashboards. More automation. More AI use cases.

None of that matters if it does not improve business performance.

The measurement model needs to connect marketing and digital activity to outcomes such as qualified demand, MQL-to-SQL conversion, funnel velocity, pipeline influence, customer retention, cost to serve, share-of-voice, content efficiency, personalization lift, and marketing ROI.

This is also where many companies are still behind. Adobe’s 2026 report notes that many organizations still lack measurement frameworks for generative and agentic AI, which makes it harder to prove value and scale investment with confidence. 

 

Marketing leaders need to ask better questions: What manual work did we reduce? What decision became faster? What conversion improved? What customer segment performed better? What sales signal became more useful? What revenue, cost, CX, or productivity metric moved?

If the AI use case cannot connect to a business outcome, it is probably not ready to scale.

Are You AI-Ready? A Simple Diagnostic

  1. Do we have a trusted view of customer and account data?
  2. Are our MarTech systems connected enough to activate data across channels?
  3. Do marketing, sales, data, IT, and CX teams share the same operating model?
  4. Do we have consent, privacy, and AI governance built into the workflow?
  5. Can we measure AI and automation against revenue, cost, speed, CX, or productivity?

What leaders should do next

The next move is not to buy another tool.

The next move is to assess whether the marketing operating system is ready.

Leaders should start with the business outcome first. Revenue growth. Lower operating cost. Faster execution. Better customer experience. Stronger sales intelligence. Higher content velocity. Clearer attribution.

Then work backwards into the capabilities required: data, MarTech, workflow, governance, content, analytics, and team adoption.

That is the foundation for AI-enabled marketing — not hype, vanity shiny objects, scattered pilots, or “AI-powered everything.

The real opportunity is to build a marketing system that can use data, automation, and AI to create better decisions, better customer experiences, and measurable growth.

MJ Digital POV

AI will not replace the need for marketing strategy. It will make weak strategy easier to see.

The businesses that win will not be the ones with the most AI tools. They will be the ones with the clearest data foundation, the strongest operating model, the most connected MarTech stack, and the discipline to tie every use case to business value.

Got questions or need help? I help companies with theese problems and build that foundation: the strategy, MarTech, data, automation, content, analytics, and operating model needed to turn digital transformation into measurable growth.

Ready to assess your AI-ready marketing foundation?

Start with scheduling a conversation and lets understand your current state and what gaps need to close to get you to that future state and what’s needed to turn AI from a tool or experiment into real business value.

by

CASE STUDY: Case Study: From 26 Websites to One Adobe-Powered Website Strategy Built for Enterprise Value and Personalized Digital Experiences

, , , , , , , ,

When a global enterprise outgrows its website ecosystem, the real problem is not the website. It is the operating model behind it

This case study shows how a global heavy equipment dealer moved from fragmented websites and disconnected MarTech and overall digital strategy to a unified digital 'hub-and-spoke' operating model. You’ll see how website strategy, MarTech (Adobe Experience Manager and Adobe Experience) governance, content, analytics, and regional execution came together to reduce complexity, improve control, and create the foundation for personalization, sales intelligence, and future growth.

Case Study: Global Website, MarTech, Content, and Performance Transformation

A heavy equipment dealer with a global footprint, and one of the largest Caterpillar dealers, had built a complex digital ecosystem across regions, languages, business units, industries, platforms, agencies, and customer journeys.

The business did not need another website refresh. It needed a global digital operating model: one that could consolidate MarTech, unify brand and content, standardize performance measurement, improve governance, and give regional teams the flexibility to execute locally within a shared enterprise framework.

At that scale, a website becomes more than a marketing channel. It becomes an enterprise asset: a sales channel, service gateway, product discovery engine, customer data source, and digital experience platform that helps customers do business on their terms — from self-service to high-engagement sales and service support.

Executive Snapshot

The organization moved from digital sprawl to a unified web, MarTech, content, and performance operating model.

Proof Points

  • 26 websites consolidated to 6 localized websites.
  • One enterprise architectur approach with one Adobe MarTech foundation standardized across website management (AEM), Analytics (Adobe Analytics), personalization and experiementation, and marketing script and tag management.
  • One glocal (global + local) hub-and-spoke operating model with Centre of Excellence created across central and regional teams.
  • KPI reviews established with framework to drive insights into the next best action.
  • Community of Practice sessions created for training and knowledge sharing across teams.

KPIs

  • Six-figure reduction in digital operating cost / OPEX.
  • 3X improve speed, agility and output
  • Seven-figure improvement in MarTech return on capital invested.
  • High double digit increase in web-generated qualified leads MQLs, SQLs and pipeline speed to win/loss.

Contact to discuss more among other major KPIs and performance indicators realized.

The Current State

The company’s digital ecosystem had grown with the business, but the operating model behind it had not kept up.

It had 26 websites across regions, languages, business units, industries, and equipment categories. Different markets used different MarTechs and platforms, 7 agencies, 3 analytics tools, no standarized reporting models, content workflows, or customer journeys.

Brand voice was inconsistent. Messaging and positioning were inconsistent. Systems and MarTechs were not connected. Data wrangling was manual. Content was hard to govern and buit a plethora of SOV debt. SEO was not yet a shared enterprise discipline. Reporting took days, sometimes weeks, of manual data wrangling and PowerPoint production. The outputs often focused on vanity metrics instead of lead generation, funnel movement, pipeline influence, or marketing return.

The Opportunity

As part of a broader enterprise transformation strategy, the opportunity was to turn a fragmented website ecosystem into a global digital experience foundation and demonstrate it as an enterprise asset for customer and revenue growth, at a lower cost-to-serve, and scalable for growth.

This was not just about consolidating websites. It was about creating an internal digital accelerator: a shared operating model, MarTech foundation, performance language, and customer data path that could help the business scale digital capabilities across regions.

For leadership, the opportunity was tied to value realization for a sales and product-driven organization that had a 80 year legacy of operating the same way.

The business could reduce operating cost by removing duplicated websites, platforms, tools, reporting processes, and agency effort. It could improve the return on MarTech investments by standardizing the enterprise foundation around Adobe Experience Manager, Adobe Analytics, Adobe Target, and tag management. It could also unify brand, content, SEO, analytics, GDPR and CASL consent, marketing automation, CRM integration, and customer data under one global framework.

The operating model was just as important as the technology as was the strategy had to demonstrate value across both COO and CMO metrics.

Underpinning the strategy, cost-savings, technology, etc. was a goal to centralize the standards and decentralize the execution with a hub-and-spoke model.

Central teams would own strategy, platforms and tech, lead the CoE, governance, compliance, analytics, best practices, and technical quality.

Regional teams would manage localized content, lead voice-of-customer and customer needs into the strategy, campaign execution while adopting global-driven programs simply requirying localization, language / market and compliance nuances, and business-unit execution within shared guardrails.

That model gave the business more control, agility, speed and flexibiltiy without slowing regional ‘I need it yesterday’ demands.

It also created a stronger foundation for growth, agility and scale. With the right website strategy, the digital ecosystem could support changing marketplace dynamics, lead generation tactics, product discovery and customer self-serve personalized preferences, online equipment insights and appointment booking, customer self-service tools, sales intelligence, ABM (account based marketing), personalization, and future CDP (customer data management) and AI (artificial intelligence) enablement.

The bigger opportunity was to make digital easier to govern, easier to measure, and easier to scale.

Instead of operating as disconnected regional teams and websites, the web ecosystem could become a global business platform: one that helped leadership lower cost, improve customer experience, commercialize data, better understand customers and adjust to their always changing demands and connect digital activity to revenue, service, and growth priorities.

The Solution

The solution was delivered in phases so the business could move from digital sprawl to a scalable global digital operating model without trying to fix everything at once.

Each phase had a clear purpose: build the foundation, capture quick wins, lay ground work for long-term big wins, reduce complexity, improve governance, gain immediate internal adoption, and create the conditions for future growth.

Phase 1: Digital Ecosystem Assessment

The first phase mapped the full current state across websites, MarTechs and platforms, agencies, regional teams stakeholders and needs captured in over 140 user stories, analytics tools, content workflows, reporting, governance, customer journeys, and MarTech overlap.

The purpose was to understand where complexity was creating cost, risk, duplication, and slow execution. This created the business case for consolidation and value realization.

Phase 2: Global Strategy and Operating Model Design

The next phase defined the global digital strategy and a new hub-and-spoke operating model.

Teams would collaborate and own strategy withing a given framework, roles and guardrails. The centrla team would lead the strategy ownership, among governance and compliance (GDPR, CASL), MarTech and platforms and integrations, data and analytics consumption and orchestration, KPIs frameworks, technical execution and quality standards, and lead a CoE (Centre of Excellence with regions and cross-functional teams for shared and best practices.

Regional teams would dedicate cross-functional individuals to partner and create shared-hybrid teams with Central, manage localized content, represent the voice-of-customer, execute on campaigns and adopt global programs with a ‘lift-and-shift’ approach for fast adoption and go-t0-market execution, and business-unit execution within shared guardrails.

Phase 3: Website Consolidation and Adobe MarTech Standardization

The business consolidated its website footprint from 26 websites to 6 localized websites and standardized its digital experience foundation around Adobe Experience Manager enabled with Adobe Analytics, Adobe Target, and Adobe tag management.

The centralization of Martech didn’t just at Adobe. It embraced a tech-agnostic approach to select and integrate the tools that were ‘fit for business’, and not forced solutions that forced Macgyver a solution.

For example, Oracle Eloqua; Oracle’s enterprise marketing automation platform  and Microsoft Azure as the data cloud to support and unify massive volume of the dispersed data from across the organizations; 6 x CRM’s ERPs, and the needs for MarTech’s data orchestration to Adobe Experience Platform (ex. personalization and content experiences). Overall, this transformational enterprise infrastruecture and data architecture initiative worked in parallel to the website strategy to unify volumes of customer data to enable orchestration across all digital touchpoints.

This reduced MarTech platform fragmentation and created a cleaner enterprise architecture for scale. The purpose was to lower operating complexity while improving governance, speed, and MarTech value realization.

Phase 4: Brand, Content, SEO, and Reusable Experience Framework

The business unified its global brand voice, messaging, content strategy, SEO discipline, and digital asset governance under the same team and a connected arm to the Digital strategy.

Adobe Adobe Experience Manager (AEM) as the core CMS, Reusable templates and components acted like “Lego blocks,” helping regional teams build pages, web forms, campaign landing pages, tracking structures, and content modules faster without breaking global standards. This phase supported content and page production velocity, search visibility, inbound demand generation, and local market flexibility.

Phase 5: Product, Commerce, Portal, and GeoLocation Experience Integration

The website became more connected to the way customers actually do business. New, used, and rental equipment data was integrated through PIM and APIs, OEM product data was enriched for the business, rental eCommerce was connected for online bookings, and authenticated customer portals supported parts, service, billing, reminders, and appointments. Google Maps API helped tailor the experience to the visitor’s closest retail or service location.

Phase 6: Measurement, Reporting, and KPI Performance Management

The business moved from manual reporting and vanity metrics to centralized reporting, standardized KPIs, and recurring performance reviews.

Semi real-time dashboards created via consuming Adobe Analytics data and surface through Tableau, and bi-weekly KPI reviews helped teams translate data into optimization plans and next-best actions. This phase gave leadership a clearer view of digital performance tied to business objectives, OKRs, lead generation, funnel movement, and marketing return.

Phase 7: Integrations with Marketing Automation, CRM, and Sales Intelligence

SDK’s from marketing automation implemented with web forms connected to Oracle Eloqua, CRM systems (SalesForce, Microsoft Dynamics and custom), lead scoring and routing, downstream integration to the Azure data lake for future enablement of a CDP pathway. Known visitors could receive more personalized or pre-populated forms, while marketing automation could support converting anonymous users to known users and customers for profile enrichment, visitor behavior could support lead scoring, and driving lead segmentation for lead nurturing programs, triggered email or SMS, and high-intent event tracking. This helped turn website behavior into sales intelligence, ABM signals, and better customer relationship conversations.

Phase 8: Centre of Excellence, Adoption, and Future Personalization Readiness

A Centre of Excellence and Community of Practice helped teams adopt the new model through training, best practices, mentoring, and knowledge sharing. The foundation also prepared the business for future personalization, experimentation, first-party data activation, and future customer data management solution (CDP) enablement. This turned the transformation from a platform rollout into a repeatable digital capability across the enterprise.

Results & Impact

The transformation created a leaner, faster, and more governed digital operating model.

The business unified its global brand voice and content strategy while allowing regional messaging to fit local markets. It improved MarTech value realization by making Adobe platforms the central enabler and tool for more connected, adopted, and usefulness across the organization. It created stronger compliance controls for consent, privacy, cookies, preferences, and web forms.

The web strategy also moved performance management forward. Improved cross-board teams and cross-functional teams collaborations, centralized critical disciplines (ex. web development, UX designers, Marketing technologists, strategy and roadmapping,  data strategy and reporting, standardized KPIs, bi-weekly KPI reviews, and shared insights helped teams shift from manual reporting to action planning.

Most importantly, the foundation prepared the business for the next stage of digital growth: value realization that the digital capabilities are an enterprise asset, enabled teams to shift perceptation as a cost-centre to the organization to a hybridge revenue-centre like Sales, customer centricity thru hyper-personalization, experimentation mindset, ABM (account-based marketing) support Sales executives to scale account management, enabled new high-intent sales signals to spark timely and relevant sales conversations to close more deals, commercialized first-party data and its activation through marketing automation, and the groundwork to enable a future CDP to create a true Customer 360 and its Marketing activation and orchestration to act on the data and signals.

The Takeaway

For global enterprises, a website strategy is more than just a redesign or consolidation. It is a strategic business decision to unlock new value, grow new and incremental revenue, enhanced customer experience,  and lower the cost to serve at scale and to more with less.

It’s not just about technology. The operating model along with the capabilities are critical to support its success.

This transformation shows what becomes possible when Digital strategy, business buy-in with cross-functional team participation, brand and content, MarTech, data and analytics, customer experience, governance, and regional adoption are connected through one global strategic framework and solution.

MJ Digital helps enterprise teams turn fragmented digital ecosystems into scalable growth engines — connecting strategy, customer channels, people, technology, data, and execution to measurable business outcomes and value.

by

PLAYBOOK: The Global Marketing & MarTech Reset: An Executive Playbook for One Customer, One Truth

, ,

Whether you scaled globally first and figured out MarTech and data “later,” or you’ve grown through rapid M&A and inherited a patchwork of regional stacks, the challenge is the same: too many clouds, too many tools, too many versions of the customer. For enterprise leaders, the mandate is now clear—consolidate the complexity, reduce total cost of ownership, and build a governed foundation for compliant growth at global scale.

Why This Problem Is Showing Up Now

Many businesses grew up too fast, or grew through organic M&A’s. Regardless how your business got there, you’re now global and the business did not design its current marketing, data and identity ecosystems—they inherited them or it was an afterthought of legacy thinking and priorities.

Recent research reinforces this urgency: many organizations have invested heavily in Martech yet still “struggle to clearly articulate or measure ROI,” often because fragmented stacks, poor user adoption; which speaks to lack of strategy and prioritized execution roadmap; and poor integration preventing technology from delivering meaningful business impact at scale.

McKinsey notes, unlocking the next wave of growth requires reimagining Martech not as disconnected tools, but as an integrated, enterprise-wide system aligned around the customer. It’s shift from a sunk-cost POV to understanding how MarTech enables and contributes enterprise value, and an engine for revenue growth. See McKinsey article Rewiring MarTech: From Cost Center to Revenue Growth.

Why this problem is surfacing now, lets briefly touch on where it all started.

Typically with enterprises, over time, regions moved off-premise into the cloud, and setup different cloud platforms (AWS, Azure, GCP, OCI), data warehouses (Snowflake, Databricks, BigQuery), and marketing tools (Adobe, Oracle, SalesForce or a hybrid toolbox that make up your MarTech) stack.

What once enabled regional speed now creates enterprise drag: rising costs, duplications, conflicting customer identities and records, inconsistent consent enforcement, reporting disputes, and difficulty scaling globally.

Executives and leaders are now tasked with driving down the cost-to-serve (OPEX), improve the ROCI, etc. all  through  consolidating, simplifying, and scaling—while reducing TCO (total cost of ownership).

This is not a tool replacement exercise. It is an architectural realignment.

Start at the Root Problem

Most organizations confuse where data is stored with how customers are understood. Let alone, rarely had the luxury to define strategy informed by internal and external user-stories.  To to set the stage to understand the root problem, view your architecture like this:

  • Your Land = Your cloud platforms. Think Amazon (AWS), Microsoft (Azure) or Google (GCP)
  • Your Home & Buildings = Data platforms are the tools and tech like Snowflake, Databricks, and BigQuery where your data is organized, structured, and made usable.
  • Your Car = Marketing platforms — the delivery vehicles that move your message, carry the customer experience, and take you to the right destinations across channels (email, SMS, web, mobile, ads).
  • Your City Rules = Governance + the global data model — the shared standards (customer ID, consent, definitions, naming) that turn regional chaos into one coordinated system so every team builds and operates off the same “truth.”

The missing layer is harmonization and identity governance.

Architectural Models: Centralized or Federated?

When you’re consolidating a global MarTech stack, there are two practical ways to organize the mess: bring everything into one shared “global core,” or let each region keep its setup while following the same rules and avoid the politics ;-).

It’s important we touch on this point as it will help explain what they offer, and what they cost you over time.

The way I would explain this, it’s the difference between running one well-managed headquarters for the whole company versus running multiple regional offices that follow the same playbook—but can drift without super strong oversight and governance (and when does that often work seamlessly?)

Model A – Centralized Global Harmonization:

All regional data converges into one governed harmonization layer before activation.

Pros:

  • Single source of truth
  • Strong compliance
  • Unified reporting,
  • Lower long-term TCO.

Cons:

  • Higher initial integration effort
  • Higher organizational alignment required.
Model B – Federated Harmonization (Mirrored Across Regions):

The federated approach, or mirror or replication approach. Each region applies the global standard schema locally. 

The global standard typically includes:

  • Universal Customer ID framework — how identities are created, matched, and maintained across systems.
  • Consent model — standardized fields for opt-in status, source, jurisdiction, timestamp, and permitted channels.
  • Core data definitions — consistent meaning for key attributes like customer status, account type, lifecycle stage, and engagement signals.
  • Product and service taxonomy — shared naming and categorization so offerings are understood the same way globally.
  • Channel eligibility rules — how contactability is defined (emailable, marketable, suppressions, etc.).
  • Regulatory classifications — flags that align with CASL, GDPR, CCPA, PIPL, and other regional requirements.
  • Data quality and formatting standards — normalization of fields such as country codes, addresses, and identifiers.
  • Naming conventions and metadata structure — ensuring data can be aggregated and reported consistently.

Ok…your cheat notes, the good and the ugly of the federated model.

Pros:

  • Faster deployment
  • Regional autonomy.

Cons:

  • Governance drift
  • Identity duplication
  • Higher long-term operational costs.

The tradeoff

View it like this. Model B or the federated approach optimizes for speed today.

Model A or central approach optimizes for scale tomorrow, but takes more time to get there.

So what’s in a global data model then?

I’m usually a red pill person here—if I’m starting with a blank canvas and no major technical debt or politics that would hinder balancing speed with value realization—I lean to the global centralized model. Here’s why…

The global data model defines how the enterprise understands customers EVERYWHERE.

It includes:

  • Universal customer ID logic
  • Consent attributes by jurisdiction
  • Product taxonomy
  • Lifecycle status definitions
  • Channel eligibility rules
  • Regulatory classifications

This model must be centrally governed, even if regions retain separate cloud platforms.

So if you take this path, then the natural fork in the road will be how you choose to handle the data to build your Customer 360 or universal customer identity and their profile.

Customer 360 & The Role of a CDP

A CDP (Customer Data Platform) such as SalesForce Data Cloud, Adobe Real-time CDP or Segment (Twilio) serves as the engine for customer identity and consent.

Picture this. You have 5 different tools or systems where a single customer lives. Let’s call her Lisa. Her profile and data lives in many siloed or fragmented systems in your business:

  • Marketing automation tool: Lisa receives emails, SMS and push notifications from marketing
  • Website: Lisa visits your brand website to stay connected and see what’s new.
  • eCommerce: Lisa browses and shops and transacts in your eStore.
  • POS: Lisa sometimes like to go offline to your Robson street store to purchase in-store.
  • CRM: Your sales reps. created a record for her under the company account she works for.
  • Social: Lisa stays engaged and connected across Meta, Instagram and TikTok
  • 3rd Parties: Other data providers may have data about her, whether its her local bank, other stores or competitors she shops at, tickets to a concert she attended, etc.

So now that Lisa’s data dna is everywhere, thus fragmented and siloed, imagine what you could do if you had one simple universal or unified identity and profile of Lisa from all the data across those systems

Think hyper-personalization and experiences you could enable to keep her engaged with your brand and your eco-system for future up-sell, cross-sell and long-term loyalty.

So unifying all the profile data about Lisa, reconcile her consent, creates activation-ready audiences like Lisa and bridges the enterprise data about Lisa and all your customers into marketing platforms for orchestration and activation. 

A CDP is by no means a replacement for a data warehouse. It sits between enterprise data and marketing orchestration and activation.

Where Should Consent Live?

Consent should live above marketing tools.

Enterprise systems store consent events.

The CDP resolves and governs consent.

Marketing platforms execute only on approved audiences.

This structure reduces regulatory risk and ensures global enforcement consistency across CASL, GDPR, CCPA, PDPA or mixes of them.

Marketing Orchestration Layers: B2C vs B2B

One of the most common MarTech drivers of architecture discussion and needs is driven by marketing automation, personalization and its orchestration. 

While the best-of-breed tools from SalesForce, Adobe, Oracle are all great enterprise tools, the reality is most of you have these plus a dozen or two of other mid-tier MarTechs. 

But in spirit of understanding the Marketing activation layer, lets look at one of the most effective MarTech solutions; marketing automation.

Let’s take SalesForce for a second (not a paid plug).

SalesForce, their B2C Marketing (Marketing Cloud Engagement) focuses on lifecycle marketing at scale, multichannel orchestration, and behavioral engagement. For those of you not familiar with lifecycle marketing, just think of it as all those high-value touchpoints when engaging a business; from staying top-of-mind, nurturing, converting, welcoming, onboarding, up-sell, cross-sell, retention and loyalty opportunities to touch the customer– and do it at scale and hyper-personalized and tailor to the individual (across their channel preference).

SalesForce B2B solution, SalesForce Marketing Account Engagement focuses is tailored to the B2B crowd where lead nurturing, qualification, scoring, pipeline management, CRM alignment, and sales pipeline acceleration are the priorities.

Their marketing automation solutions serve different needs and different orchestration purposes but rely on the same unified identity foundation.

So whether its marketing automation, journey orchestration, segmentation, website personalization, customer profiling or BI reporting, a unified identity and profile are key.

The Outcome: Solve the Original Problem

By centralizing data harmonization and user identity before Marketing activation, businesses like yours reduce duplication, improve compliance, improve customer consent, lower TCO, and enable scalable personalization.

The enterprise shifts from fragmented regional silos to coordinated global orchestration with local execution.

To wrap it up and keep it simple, think of your enterprise architecture blueprint for global marketing and Martech like this: 

  1. Regional Tools: CRM, eCommerce, Marketing Automation
    ↓
  2. Regional Cloud Systems (AWS / Azure / GCP)
    ↓
  3. Data Platforms (Snowflake / Databricks / BigQuery)
    ↓
  4. Global Harmonization Layer (Canonical Data Model)
    ↓
  5. CDP / Identity Resolution
    (ex. 1 identity for a customer across all systems and tools, stitching or unifying 1st party, 2nd party and 3rd party data)
    ↓
  6. Marketing Activation (B2B or B2C)
    • Marketing automation
      (email, SMS, push, digital advertising, website)
    • Journey orchestration
    • Personalization
    • CMS and content fragments
    • eCommerce platform
    • Website Analytics
      (enabled with the latter)

Got questions or ideas to share on your journey to unify your MarTech stack and realize that one single customer identity? Reach out to schedule a call or connect on LinkedIn.

by