Lifecycle marketing audit: a 50-point scorecard

Short answer. Score each control from 0 to 2: missing, partial, or operational. The 50 controls cover strategy, consent, data, acquisition, lifecycle journeys, campaigns, deliverability, measurement, experimentation, and operations. Prioritize red-risk failures first, then high-impact gaps with reliable data. The total score is a conversation tool, not a universal maturity benchmark.

A lifecycle audit should explain where value leaks, where customer risk exists, and what the team can realistically change next. It should not reward the account with the most flows, segments, or dashboards.

This scorecard works with Klaviyo, Brevo, Customer.io, HubSpot, or another CRM and messaging stack. Adapt the evidence to the business model.

How to score the audit

Use the same scale for all 50 controls:

• 0, missing or unsafe: no evidence, serious defect, or undefined ownership;
• 1, partial: exists but is incomplete, manual, unreliable, or inconsistently used;
• 2, operational: documented, tested, owned, monitored, and used in decisions.

Maximum score: 100.

Add three fields beside every score:

1. evidence link or screenshot;
2. named owner;
3. recommended action and dependency.

Do not average away severe risk. A program can score 75 and still have a critical consent or duplicate-send problem. Flag controls as red when they create legal, customer, security, or deliverability risk.

A. Strategy and customer journey, 10 points

1. Commercial objectives are explicit

Lifecycle has two or three measurable objectives such as first-to-second purchase, activation, renewal, or contribution margin, not only "grow email revenue."

2. Customer lifecycle is mapped

The team has a current map from acquisition through activation, purchase, use, retention, reactivation, and exit, including important offline or human touchpoints.

3. Customer jobs define communication

Messages solve a customer problem or decision at each stage. The program is not organized only around internal product categories.

4. Channel roles are defined

Email, SMS, push, in-app, WhatsApp, support, sales, and transactional systems have explicit responsibilities and escalation rules.

5. Priorities reflect impact and dependency

The roadmap ranks initiatives by expected impact, customer or compliance risk, confidence, effort, and data prerequisites.

B. Consent and preference governance, 10 points

6. Consent is stored by channel

Email, SMS, push, and other permissions are separate. A customer order or one channel opt-in is not treated as universal permission.

7. Source and timestamp are retained

The organization can explain where, when, how, and under which disclosure the person subscribed, subject to applicable requirements.

8. Preferences propagate reliably

Subscribe, unsubscribe, suppression, and resubscribe changes reach all relevant senders without uncontrolled delay or overwrite.

9. Transactional and promotional purposes are separated

Every operational message has one owner and an appropriate purpose. Promotional content does not hide inside critical service communication.

10. Market-specific rules have an owner

Legal and operational requirements are reviewed for the markets where the program sends. The lifecycle team knows when to request specialist advice.

C. Identity and data quality, 10 points

11. A stable identity model exists

The team knows how email, phone, customer ID, account, device, and anonymous activity resolve into people and organizations.

12. Core events have specifications

Signup, product use, checkout, order, fulfillment, refund, subscription, and other critical events have defined trigger moments, properties, types, and owners.

13. Event payloads are validated

Monitoring checks volume, nulls, duplicates, timestamps, identifiers, currencies, product data, and unknown values rather than only connector status.

14. Profile properties are governed

Properties have controlled names, types, allowed values, sources, update rules, and documented business uses. Redundant fields are retired.

15. Data changes follow a process

Schema or integration changes are communicated, tested, versioned where needed, and reviewed before they break segments or personalization.

D. Acquisition and onboarding, 10 points

16. Acquisition sources are inventoried

Footer forms, popups, checkout, landing pages, quizzes, events, and paid lead sources are mapped with purpose and consent behavior.

17. Forms match visitor context

Offers and questions reflect page, intent, market, and customer value. The team does not show the same aggressive popup everywhere.

18. Form performance is measured end to end

Reporting covers eligible impressions, completion, valid subscription, first meaningful action, and downstream value, not only form submission.

19. Welcome logic adapts to status

Source, use case, purchaser status, market, and behavior change the welcome path where useful. Customers exit first-purchase persuasion.

20. Acquisition quality feeds decisions

The team compares sources using engagement, conversion, retention, complaint, and customer value, and can reduce poor-quality growth.

E. Lifecycle flows, 10 points

21. Every flow has a specification

The trigger, filters, exclusions, branches, delays, exits, message purpose, success metric, and owner are documented.

22. High-intent journeys are operational

The relevant welcome, activation, cart or checkout, post-purchase, subscription, replenishment, and retention flows work for the model.

23. Flow overlap is controlled

Customers do not receive contradictory reminders from multiple flows, campaigns, transactional systems, sales, or support.

24. Timing follows customer behavior

Fulfillment, product use, buying cycle, subscription state, and time zone inform delays. Fixed timings are not copied across unrelated products.

25. Flows are continuously maintained

The team reviews errors, volume, exits, content, offers, data changes, and performance on a set cadence, with version notes.

F. Campaign program, 10 points

26. Every campaign has a reason to send

Launch, education, replenishment, editorial value, seasonal relevance, proof, or a real promotion drives the message.

27. Audience selection is intentional

The team uses engagement, behavior, value, market, eligibility, and pressure rules. Full-list sends require a defensible reason.

28. Frequency is governed

Campaign and flow pressure is visible across channels. Recent purchasers, support cases, VIPs, and cold recipients receive appropriate treatment.

29. Creative production is systematic

Briefs, reusable modules, copy and design standards, accessibility, localization, approval, QA, and deadlines are defined.

30. Calendar and inventory agree

Product availability, margin, fulfillment capacity, offer conditions, and other operational constraints are verified before send.

G. Deliverability and list health, 10 points

31. Authentication is correct

SPF, DKIM, DMARC, branded sending and tracking domains, and relevant provider requirements are configured and monitored.

32. Bounce and complaint controls exist

Hard and repeated soft bounces, complaints, block events, and unusual provider patterns have alerts, thresholds, and owners.

33. Engagement-aware sending is routine

Regular campaigns prioritize recent, trustworthy behavior. Opens are interpreted with privacy limitations and not used alone.

34. Reactivation and sunset are defined

The team knows when to reduce frequency, attempt reactivation, and suppress long-term inactive contacts based on the normal lifecycle.

35. Volume changes are controlled

Migrations, domain changes, holidays, acquisitions, and promotions use a deliverability-aware rollout rather than an uncontrolled spike.

H. Measurement and economics, 10 points

36. Metric definitions are shared

Delivery, conversion, revenue, active customer, churn, and other KPIs have documented formulas, sources, and time zones.

37. Attribution is transparent

The platform window and model are recorded. Stakeholders understand that attributed revenue is not automatically incremental.

38. Net economics are included

Reporting uses discounts, returns, margin, cost of goods, and relevant operating cost where decisions require them.

39. Customer guardrails are visible

Unsubscribe, complaint, support contacts, preference changes, cancellation, and satisfaction can block a superficially positive result.

40. Cohorts connect lifecycle to retention

First-to-second purchase, activation, repeat behavior, renewal, or time-to-value is measured by relevant signup or customer cohort.

I. Experimentation and learning, 10 points

41. Tests start with a hypothesis

The team states the expected behavior change, primary metric, population, variants, and decision rule before launch.

42. Sample and duration are planned

Tests account for baseline rate, detectable effect, traffic, buying cycle, seasonality, and repeated peeking rather than stopping at a convenient result.

43. Downstream outcomes matter

Click or open changes are interpreted alongside conversion, margin, retention, and customer guardrails.

44. Holdouts are used for material journeys

Major flows or program changes have randomized or credible comparison groups where practical, helping estimate incrementality.

45. Learnings are retained

An experiment log records setup, exposure, results, limitations, decision, and follow-up. Teams do not repeat the same unresolved test.

J. Operations, security, and governance, 10 points

46. Roles and access follow least privilege

People use individual accounts, multifactor authentication, appropriate roles, and prompt access removal. Shared owner credentials are prohibited.

47. QA is branch-based

Checklists cover audience, consent, trigger, filters, dynamic content, links, coupons, time zones, mobile rendering, fallback data, and rollback.

48. Documentation supports handover

Lifecycle maps, event dictionaries, segment definitions, flow specifications, templates, dashboards, and runbooks have owners and current locations.

49. Platform cost is actively managed

The team reviews active profiles, sends, mobile usage, add-ons, connector cost, and unused capabilities without sacrificing valid data or customer value.

50. A recurring operating cadence exists

Weekly monitoring, monthly performance decisions, quarterly roadmap review, and incident escalation are scheduled with accountable participants.

Interpret the score

Use broad bands only as internal orientation:

Do not compare this score publicly across companies without normalizing the business model and evidence. A small SaaS and a global retailer need different controls and depths.

Turn findings into a roadmap

For every gap, assign:

• severity: red, amber, or green;
• customer and business impact;
• confidence in the finding;
• effort and dependency;
• accountable owner;
• target date;
• proof of completion.

Sequence work:

1. compliance, security, duplicate-send, and deliverability risk;
2. broken data and critical customer journeys;
3. high-impact revenue or retention opportunities;
4. measurement and experiment foundations;
5. optimization and scale.

Do not build a new flow when the event it needs is unreliable. Do not add a dashboard before agreeing on definitions. Dependencies are part of prioritization.

FAQ

What is a lifecycle marketing audit?

It is a structured review of customer journeys, consent, data, messaging, deliverability, measurement, experimentation, and operating controls across the lifecycle.

Is 100 the target score?

Not necessarily. Some controls may be lighter for a simple business. The score helps reveal gaps and ownership. Red-risk items matter more than the total.

How often should the audit be repeated?

Run it after major migrations or incidents and on a regular cadence such as twice a year. High-change teams can review critical controls quarterly.

Who should participate?

Lifecycle marketing, CRM, data or engineering, ecommerce or product, legal or privacy ownership, deliverability, creative, analytics, and customer-facing teams as relevant.

Can the audit be used for platform selection?

Yes. It separates process and data problems from software gaps. A migration should not be recommended when the primary failures are ownership or execution.

Audit the operating system, not only the account

Deliver uses evidence, risk, customer impact, and dependencies to turn lifecycle audits into an executable roadmap. Request a 50-point lifecycle marketing audit.