Marketing Analytics

Chapter 14
MarTech, AI and Digital Transformation

Bachelors Program in Business Analytics
Marketing Analytics   •   Bachelor

MarTech, AI and Digital Transformation

Introduction

Marketing technology (MarTech) refers to the software, data, platforms and analytical capabilities used to plan, execute, measure and improve marketing. Contemporary marketing is increasingly built on connected systems: customer relationship management (CRM) platforms record interactions, customer data platforms (CDPs) unify customer identities, data warehouses support analysis, automation tools activate decisions, and artificial intelligence (AI) improves prediction and content generation.

Digital transformation is broader than purchasing software. It is the organisational redesign of processes, capabilities, governance and decision rights around digital data and technology. A firm may possess advanced tools yet remain digitally immature if its data are unreliable, systems are disconnected, employees lack skills, or managers do not trust analytical recommendations.

This chapter examines the architecture and managerial use of MarTech, machine learning and generative AI. It also considers model evaluation, human oversight, deployment, privacy and organisational readiness.

Learning Objectives

By the end of this chapter, students should be able to:

  1. Distinguish CRM systems, CDPs, data warehouses, data lakes and marketing-automation platforms.
  2. Explain a modern marketing analytics architecture and the role of data governance.
  3. Apply machine-learning methods to prediction, segmentation, personalisation and campaign decisions.
  4. Explain appropriate uses and limitations of generative AI in marketing.
  5. Evaluate models using suitable performance metrics and business criteria.
  6. Design responsible human oversight and deployment processes.
  7. Assess organisational readiness for marketing-related digital transformation.

1. The MarTech Ecosystem

A MarTech stack is a portfolio of interconnected technologies rather than a single application. Common layers include:

LayerMain purposeTypical examples
InteractionCaptures or delivers customer contactWebsite, mobile app, email, social media, call centre
Record systemsStores operational customer and transaction informationCRM, sales platform, service platform
Data foundationIntegrates and preserves data for analysisData warehouse, data lake, lakehouse, CDP
IntelligenceProduces descriptions, predictions and recommendationsBI, machine learning, experimentation tools
ActivationExecutes decisions at scaleMarketing automation, ad platforms, recommendation engines
GovernanceControls access, quality, privacy and riskIdentity management, consent systems, audit logs

The stack creates value only when information can move reliably between layers. For example, a purchase may be recorded in a commerce platform, linked to a customer identity in a CDP, analysed in a warehouse, scored by a propensity model and used by an automation platform to select a message. Each transition can introduce error, delay or privacy risk.

CRM systems

A CRM system is primarily an operational system for managing customer and prospect relationships. It commonly stores contact details, leads, opportunities, service cases, sales activities and account histories. CRM data are valuable for coordination and frontline action, but the system is not necessarily a complete record of customer behaviour. Website events, advertising exposure, point-of-sale transactions and external demographic data may remain elsewhere.

CRM systems answer questions such as: Which sales representative owns this opportunity? What service case is open? When was the last contact? Their strength is operational workflow; their limitation is that data may be structured around organisational processes rather than analytical requirements.

Customer data platforms

A CDP collects customer-level data from multiple sources, resolves identities and creates persistent profiles intended for marketing activation. A CDP may connect email addresses, device identifiers, loyalty numbers and transaction records. Identity resolution can be deterministic, based on a known matching key, or probabilistic, based on a calculated likelihood that records refer to the same person.

A CDP is not automatically a data warehouse. It is generally designed for accessible, near-real-time audience creation and activation. Organisations must define identity rules carefully: incorrectly merging two people can expose private information, while failing to link the same person fragments measurement and personalisation.

Data warehouses, lakes and lakehouses

A data warehouse stores structured, cleaned and modelled data for reporting and analytical queries. A data lake stores data in a broader range of formats, often before extensive transformation. A lakehouse seeks to combine the flexibility of a lake with the governance and analytical performance associated with a warehouse.

A useful distinction is between operational data and analytical data. Operational systems optimise current transactions; analytical systems integrate historical data for comparison, modelling and decision support. Extract-transform-load (ETL) processes transform data before loading, whereas extract-load-transform (ELT) loads data first and transforms it within the analytical environment.

Automation platforms

Marketing automation platforms execute rules, journeys and triggers. Examples include sending an abandoned-cart message, routing a lead, suppressing a customer from an acquisition campaign, or changing an offer after a service complaint. Automation improves speed and consistency, but a badly designed rule can reproduce errors at scale. Every important automated action should have eligibility criteria, frequency limits, an exception process and an audit trail.

2. A Reference Marketing Analytics Architecture

A practical architecture can be understood as a sequence:

Sources → ingestion → storage and modelling → identity and consent → analytics → activation → measurement and feedback

Sources include transaction systems, web and app events, advertising platforms, surveys, service records and loyalty programmes. Ingestion may occur in batches or through event streams. Storage preserves raw and curated data. Modelling creates analytical tables such as customer, order, campaign exposure and event tables. Identity and consent determine what may be joined and used. Analytics generates segments, forecasts or scores. Activation sends decisions to channels, while measurement returns outcomes for learning.

The architecture should support four properties:

  • Traceability: analysts can identify the origin and transformation of a metric.
  • Timeliness: data arrive quickly enough for the decision being made.
  • Reliability: pipelines have tests, monitoring and recovery procedures.
  • Security: access is restricted according to role and sensitivity.

Data quality and governance

Important dimensions of data quality include accuracy, completeness, consistency, validity, uniqueness and timeliness. Governance assigns ownership and establishes definitions. For example, “active customer” might mean a purchase within 90 days, an app login within 30 days, or a currently subscribed account. If teams use different definitions, dashboards may disagree even when their calculations are technically correct.

A data dictionary should specify field meanings, units, permitted values, source systems, update frequency and responsible owners. Data lineage records how a field moves from source to report or model. Access controls should follow least privilege: users receive only the access necessary for their role.

Measurement architecture

Marketing measurement requires more than counting conversions. A conversion may be associated with several touchpoints, and observed association does not prove that a channel caused the outcome. Useful designs include randomized holdout experiments, geo experiments, pre-test/post-test comparisons and carefully constructed observational models. Attribution reports can support description, but incremental experiments are stronger evidence of causal impact.

For a campaign, incremental conversions can be estimated as:

ΔY = YT − YC

where YT is the outcome rate or total outcome for the treatment group and YC is the corresponding outcome for a comparable control group. The estimate is interpretable as causal only when treatment assignment and measurement satisfy the experiment’s assumptions, including adequate randomisation or credible comparability.

3. Machine Learning in Marketing

Machine learning (ML) learns patterns from data to generate predictions or decisions. It does not replace the need to define a business problem, a target variable, an action and a success criterion.

Common marketing tasks

  • Classification: predicting churn, response, fraud or likelihood of conversion.
  • Regression: predicting revenue, customer lifetime value or demand.
  • Clustering: grouping customers by behavioural similarity without a predefined label.
  • Recommendation: ranking products, content or offers.
  • Forecasting: estimating future demand, traffic or retention.
  • Natural-language processing: analysing reviews, conversations and open-ended feedback.

A typical supervised-learning workflow separates data into training, validation and test sets. The training set estimates model parameters; validation data support model selection and tuning; the test set provides an approximately unbiased final evaluation when it has not influenced development. Time-dependent marketing data require temporal splits to avoid using future information to predict the past.

Classification metrics

For a binary classifier, a confusion matrix contains true positives (TP), false positives (FP), true negatives (TN) and false negatives (FN). Important metrics include:

Accuracy = (TP + TN) ÷ (TP + TN + FP + FN)
Precision = TP ÷ (TP + FP)
Recall = TP ÷ (TP + FN)

Accuracy is useful when classes and error costs are reasonably balanced. Precision measures the proportion of predicted positives that are actually positive. Recall measures the proportion of actual positives detected. When positive cases are rare, accuracy can be misleading. Threshold selection should reflect business costs: contacting an uninterested customer may waste budget, while missing a likely donor may reduce revenue.

For predicted probabilities, calibration asks whether cases assigned a probability of 0.70 experience the event approximately 70% of the time in a sufficiently large group. Ranking metrics such as area under the receiver operating characteristic curve (ROC-AUC) assess discrimination across thresholds, but neither ranking nor calibration alone proves commercial value.

Regression and forecasting metrics

For actual values yi and predictions ŷi, mean absolute error is:

MAE = (1 ÷ n) ∑|yi − ŷi|

where n is the number of observations. MAE has the same units as the target and treats errors linearly. Root mean squared error is:

RMSE = √[(1 ÷ n) ∑(yi − ŷi)2]

RMSE penalises large errors more heavily than MAE. Both assume the observations and evaluation design are appropriate for the decision; neither automatically measures profit or customer welfare.

Worked example: response targeting

Suppose a campaign model identifies 200 customers as likely responders. Of these, 50 respond. There are 100 actual responders in the full evaluation sample, and 30 of them were not selected. Thus TP = 50, FP = 150, FN = 30 and TN = 770.

Precision = 50 ÷ (50 + 150) = 0.25, or 25%.

Recall = 50 ÷ (50 + 30) ≈ 0.625, or 62.5%.

The model finds 62.5% of responders, but only one in four targeted customers responds. Whether this is acceptable depends on contact cost, response value, fatigue and the performance of alternative targeting rules.

From prediction to uplift

A response model estimates who is likely to respond. An uplift model estimates how treatment changes behaviour relative to no treatment. This distinction matters because some customers would purchase without advertising, while others may respond negatively to contact. A treatment policy should therefore consider incremental response, cost and customer experience rather than targeting the highest predicted response alone.

4. Personalisation and Decisioning

Personalisation ranges from simple rule-based treatment to real-time individual recommendations. Its potential benefits include relevance, convenience and improved resource allocation. Its risks include stereotyping, excessive surveillance, unfair exclusion and the creation of “filter bubbles.”

A sound decisioning process includes:

  1. Define the eligible population and objective.
  2. Establish consent and purpose limitations.
  3. Select features available at decision time.
  4. Predict an outcome or estimate treatment effect.
  5. Apply business constraints such as margin, inventory, frequency and fairness.
  6. Deliver the action through an approved channel.
  7. Measure incremental outcomes and unintended effects.

Customer lifetime value (CLV) may be estimated using a detailed discounted cash-flow model:

CLV = ∑t=1T [(Rt − Ct) × pt] ÷ (1 + r)t − AC

Here Rt is expected revenue in period t, Ct is expected variable cost, pt is the probability the customer remains active, r is the discount rate, T is the planning horizon and AC is acquisition cost. The model assumes the estimates are defined consistently and that discounting, retention and margin assumptions are appropriate. CLV is an estimate, not an accounting fact; uncertainty should be reported.

5. Generative AI in Marketing

Generative AI produces text, images, audio, code or structured outputs from prompts and context. Large language models generate sequences by estimating likely tokens from learned patterns. They can support:

  • draft copy, subject lines and product descriptions;
  • summarisation of research, calls and reviews;
  • translation and tone adaptation;
  • conversational service assistance;
  • creative variation for controlled testing;
  • retrieval and synthesis from approved internal knowledge;
  • scenario analysis and decision-support narratives.

Generative AI is not a guaranteed source of truth. It can hallucinate facts, reproduce training-data bias, disclose confidential information, infringe intellectual-property rights or produce persuasive but unsuitable language. A model’s fluent output is not evidence of accuracy.

Responsible generative-AI workflow

A robust workflow separates generation from approval:

  1. Define the task, audience, constraints and success measure.
  2. Use approved data and avoid unnecessary personal information.
  3. Provide grounded context, such as verified product facts.
  4. Generate multiple candidates where appropriate.
  5. Check factual accuracy, brand suitability, accessibility, bias and legal claims.
  6. Obtain human approval for consequential or public outputs.
  7. Log prompts, source material, model version and final edits.
  8. Monitor complaints, performance and drift.

Retrieval-augmented generation can reduce unsupported answers by retrieving relevant documents before generation, but retrieval quality and document governance remain critical. Fine-tuning may adapt style or task behaviour, yet it does not eliminate factual error or governance obligations.

6. Evaluating Models and Business Decisions

Technical performance and business performance are related but distinct. A model may have excellent AUC and produce little value if the organisation cannot act on its predictions. Evaluation should therefore occur at several levels:

LevelQuestions
StatisticalDoes the model discriminate, calibrate and generalise?
OperationalIs latency, availability and integration adequate?
FinancialDoes incremental benefit exceed total cost?
CustomerDoes the intervention improve experience or create fatigue?
EthicalAre outcomes fair, lawful and explainable enough for context?
StrategicDoes it support the organisation’s positioning and capabilities?

A simple campaign profit estimate is:

Profit = Incremental revenue − Variable cost − Campaign cost

This expression is useful only when revenue is incremental and costs are consistently defined. If the campaign would have produced many purchases without treatment, using total revenue will overstate value.

Monitoring should include data drift, prediction drift, calibration, segment performance, latency, missingness, opt-out rates and unexpected outcomes. A model should have a retirement or rollback procedure. Monitoring is especially important when customer behaviour, products, prices or regulations change.

7. Human Oversight, Deployment and Control

Human oversight is not simply placing a person at the end of an automated process. It requires meaningful authority, adequate information, time to intervene and accountability for the outcome. Oversight intensity should increase with potential harm, irreversibility, scale and difficulty of appeal.

Deployment practices include:

  • version-controlled code, data and model artefacts;
  • reproducible training and documented features;
  • testing in a sandbox before production;
  • shadow mode, in which predictions are observed without affecting customers;
  • gradual rollout and holdout groups;
  • alerts, rollback and incident response;
  • access controls and audit logs;
  • documented model cards describing purpose, data, limitations and evaluation.

Automation should not obscure responsibility. A named business owner, technical owner, data owner and risk or compliance contact should be identified. High-impact decisions may require explanations, human review and a channel for correction or appeal.

8. Organisational Readiness for Digital Transformation

Technology adoption depends on organisational conditions. A readiness assessment can examine six dimensions:

  1. Strategy: clear business outcomes and executive sponsorship.
  2. Data: accessible, trustworthy, well-defined and governed data.
  3. Technology: interoperable platforms, security and scalable infrastructure.
  4. People: analytical, domain, engineering and change-management skills.
  5. Process: documented workflows, experimentation and model operations.
  6. Culture: willingness to learn, challenge assumptions and use evidence.

A useful transformation sequence is to begin with a high-value, manageable use case; establish data and governance foundations; run a controlled pilot; measure incremental value; and scale only after operational and ethical review. Buying more tools before resolving ownership and definitions usually increases complexity rather than capability.

Illustrative Case: Aurora Retail’s Personalised Retention Programme

Background

Aurora Retail, a fictional omnichannel clothing company, has a CRM, an e-commerce platform, a loyalty database and separate email and advertising tools. Managers report that campaigns are frequent but poorly coordinated. Customers receive acquisition advertisements shortly after purchasing, and analysts cannot agree on the definition of “active customer.”

Problem

The company wants to reduce avoidable churn without increasing message volume. It proposes a machine-learning churn model and generative AI for retention messages.

Analysis

The analytics team first maps data lineage and discovers duplicate loyalty identities, missing consent flags and a leakage problem: the original churn model used a service-cancellation field recorded after the prediction date. The team defines churn as no purchase or meaningful engagement for 120 days, subject to a customer’s contractual status. It creates a temporal training and test split and establishes a holdout group.

The model ranks customers by estimated churn risk, but the team does not automatically contact everyone at high risk. It tests three policies: no contact, a service-oriented reminder, and a small incentive. The evaluation compares incremental retention and margin, not merely clicks. Customers without appropriate marketing consent are excluded.

Generative AI drafts message variants from approved product and policy documents. Human reviewers check claims, tone, accessibility and unnecessary personalisation. The system logs source documents, prompts, model version and approvals.

Outcome

In the pilot, the service reminder improves retention for one segment, while the incentive produces additional sales but reduces margin for another. The company therefore uses segment-specific policies and suppresses customers who recently complained. A dashboard monitors incremental retention, margin, opt-outs, complaint rates, calibration and segment disparities.

Learning points

The case demonstrates that transformation is not equivalent to deploying a model. Value arose from identity resolution, a valid prediction date, experimental comparison, consent enforcement, human review and operational integration. It also shows why the best predictive score does not necessarily identify the best action.

Challenges, Ethics and Regulation

Marketing analytics can threaten privacy when organisations collect excessive data, combine data for unrelated purposes or make sensitive inferences. Core principles include purpose limitation, data minimisation, transparency, security, retention limits and mechanisms for access or correction. Consent should be meaningful and withdrawal should be operationally possible where consent is the legal basis.

Fairness is context-dependent. A model can have similar overall accuracy across groups but different false-positive or false-negative rates. Conversely, equal error rates may not be achievable when base rates differ. Organisations should define the relevant harm, assess protected and vulnerable groups, document trade-offs and avoid using sensitive attributes merely to create hidden proxies.

Other risks include discriminatory targeting, dark patterns, price manipulation, copyright disputes, synthetic reviews, insecure prompt handling and automation bias. Regulatory requirements vary by jurisdiction and application. Legal review should cover privacy, consumer protection, employment implications, accessibility, intellectual property and sector-specific rules. Compliance is a baseline, not a substitute for ethical judgment.

Contemporary Developments and Best Practices

Current developments include real-time decisioning, multimodal generative systems, synthetic data, privacy-enhancing computation, retail-media analytics, agentic workflow tools and smaller domain-specific models. These developments may improve speed and accessibility, but they also increase the importance of security, evaluation and clear boundaries on autonomous action.

Best practices include:

  • start with a measurable customer or business problem;
  • maintain a documented architecture and data dictionary;
  • prefer incremental experiments to unsupported attribution claims;
  • prevent leakage and preserve temporal validity;
  • evaluate calibration, subgroup performance and business value;
  • separate recommendations from automatic execution until risk is understood;
  • use approved knowledge sources for generative AI;
  • retain human accountability for consequential decisions;
  • monitor after deployment and plan rollback;
  • build skills and governance alongside technology.

Chapter Summary

MarTech is an interconnected ecosystem of interaction, operational, data, intelligence, activation and governance technologies. CRM systems coordinate relationships, CDPs unify customer profiles for activation, and warehouses or lakehouses support integrated analysis. Successful architecture depends on lineage, quality, consent, security and reliable feedback loops.

Machine learning supports classification, regression, clustering, recommendation and forecasting, but technical metrics must be interpreted alongside costs, customer experience and incremental impact. Prediction is not the same as treatment-effect estimation. Generative AI can accelerate content and decision support, yet requires grounded inputs, fact checking, privacy controls, human approval and monitoring.

Digital transformation is organisational as well as technical. Effective deployment requires versioning, testing, observability, rollback and named accountability. Readiness depends on strategy, data, technology, people, process and culture. Responsible marketing analytics balances commercial value with fairness, privacy, transparency and customer autonomy.

Key Terms

CRM: Operational system for managing customer, prospect, sales and service relationships.

Customer data platform (CDP): Platform that integrates customer data, resolves identities and supports audience activation.

Data warehouse: Governed analytical repository containing structured, integrated data.

Data lake: Repository that stores data in varied formats, often before extensive transformation.

Lakehouse: Architecture combining aspects of data lakes and warehouses.

Marketing automation: Software that executes rules, journeys, triggers and campaign actions.

Identity resolution: Process of determining which records refer to the same entity.

Data lineage: Record of a data element’s sources, transformations and destinations.

Feature: Input variable used by a machine-learning model.

Data leakage: Use of information unavailable at the time a prediction would have been made.

Precision: Proportion of predicted positive cases that are actually positive.

Recall: Proportion of actual positive cases identified by a model.

Calibration: Agreement between predicted probabilities and observed frequencies.

Uplift: Difference in an outcome caused by treatment compared with a suitable untreated condition.

Generative AI: AI that creates new text, images, audio, code or other outputs.

Hallucination: Unsupported or fabricated output presented by a generative system.

Human-in-the-loop: Design in which a person reviews, approves or can intervene in an automated process.

Model drift: Change in data, relationships or performance after deployment.

Data governance: Policies, roles and controls governing data quality, access, use and accountability.

Digital transformation: Organisational redesign using digital capabilities to improve value creation and operations.

Review Questions

Short Answer Questions

  1. What is the primary operational purpose of a CRM system?
  2. How does a CDP differ from a data warehouse?
  3. Define precision and recall.
  4. Why is data leakage harmful in model development?
  5. State two risks associated with generative AI in marketing.

Long Answer Questions

  1. Explain the components of a modern marketing analytics architecture and the importance of feedback from activation to measurement.
  2. Compare CRM systems, CDPs, data warehouses and marketing-automation platforms.
  3. Discuss why technical model performance does not necessarily imply business value.
  4. Explain how human oversight, monitoring and rollback contribute to responsible deployment.
  5. Evaluate the organisational capabilities required for successful digital transformation.

Analytical / Application Questions

  1. A retailer has a highly accurate churn model but no controlled holdout group. Design an evaluation plan that estimates incremental retention and profit.
  2. An AI system recommends discounts mainly to customers in one demographic group. Identify possible causes, tests and governance responses.
  3. Design a responsible workflow for using a generative AI system to create personalised email campaigns, including data, approval, measurement and incident controls.

Multiple Choice Questions with Answers

Question 1

Which system is primarily designed to coordinate sales, service and prospect relationships?

A. CRM

B. Data lake

C. Recommendation engine

D. Ad-exchange auction

Correct Answer: A. CRM

Question 2

What is a central purpose of a customer data platform?

A. Replacing all accounting systems

B. Resolving customer identities and supporting audience activation

C. Compressing video advertisements

D. Eliminating the need for consent

Correct Answer: B. Resolving customer identities and supporting audience activation

Question 3

A classifier has TP = 40 and FP = 60. What is its precision?

A. 25%

B. 40%

C. 60%

D. 67%

Correct Answer: B. 40%

Question 4

Which practice best prevents temporal data leakage?

A. Randomly shuffling all records regardless of date

B. Using future cancellation records as features

C. Using time-based training and test splits

D. Removing the test set

Correct Answer: C. Using time-based training and test splits

Question 5

What does recall measure?

A. The proportion of predicted positives that are correct

B. The proportion of actual positives identified

C. The average cost of a campaign

D. The percentage of missing data

Correct Answer: B. The proportion of actual positives identified

Question 6

Why can a response model be inferior to an uplift model for campaign targeting?

A. Response models cannot use customer data

B. Response models estimate likely response but not necessarily incremental treatment effect

C. Uplift models do not require an outcome variable

D. Response models are only used for forecasting weather

Correct Answer: B. Response models estimate likely response but not necessarily incremental treatment effect

Question 7

Which is an appropriate control for generative-AI marketing content?

A. Publishing every output automatically

B. Disabling factual review to preserve creativity

C. Checking claims against approved sources and obtaining human approval

D. Uploading all confidential customer records to the model

Correct Answer: C. Checking claims against approved sources and obtaining human approval

Question 8

Which metric has the same units as the predicted target?

A. MAE

B. ROC-AUC

C. Precision

D. Recall

Correct Answer: A. MAE

Question 9

What is the main purpose of a holdout group in a campaign experiment?

A. To increase message frequency for everyone

B. To estimate what would have happened without treatment

C. To remove the need for consent

D. To guarantee every customer purchases

Correct Answer: B. To estimate what would have happened without treatment

Question 10

Which condition most directly indicates organisational readiness for MarTech transformation?

A. Many disconnected tools with no owners

B. A clear use case, governed data, skilled staff and accountable processes

C. Automating decisions before defining outcomes

D. Maximising the number of dashboards

Correct Answer: B. A clear use case, governed data, skilled staff and accountable processes

Marketing Analytics
Chapter 14 of 15