One clear framework.
41 providers, 1,220 sites.
Zero proprietary dependencies.

Measurement Framework

A canonical KPI definition for every metric, exact trigger, required parameters, and allowed values, so data means the same thing across all 1,220 dealer sites regardless of which of the 41 providers built them.

Roadmap & Gantt

Discovery, KPI design, audit, and spec work run in parallel. Provider categories onboard as their specs are ready. QA and documentation run continuously across all phases from the moment the first provider goes live.

Data Collection Audit

A provider-by-provider inventory of current-state data collection across all 41 certified providers, establishing the factual baseline that makes the specification achievable, not aspirational.

• Website Providers (7): All 7 currently push to Adobe Analytics. Audit confirms existing data layer maturity, variable mapping, and Ensighten deployment model per provider, establishing the baseline each must standardize to.
• Chat Tools (8): Tracking capability varies significantly. Audit assesses whether each provider supports postMessage or direct dataLayer write, documenting limitations before spec publication so the spec reflects reality.
• Digital Retail Tools (10): iFrame architecture review per provider. Documents event passthrough feasibility and required schema by integration type, preventing spec requirements that providers physically cannot implement.
• Trade-In (7) & Service Scheduler (9): Widget event inventory identifying which funnel steps are currently tracked, which are missing, and which require custom instrumentation, prioritizing highest-gap providers for early engagement.
• Platform constraints: CMS, TMS, and iFrame limitations documented per provider so the spec accounts for real-world constraints before providers receive it. No aspirational requirements that fail in production.

Solution Design

A standardized, TMNA-owned data layer architecture applicable across all dealer websites and every embedded TDDS-certified third-party tool, the single schema all 41 providers implement consistently.

• Simplicity over volume: Every field in the schema earns its place against a specific KPI requirement. No speculative attributes that add complexity without adding decision value.
• Vendor-agnostic by design: The dataLayer object is plain JavaScript. It does not depend on Ensighten, Adobe, or any TMS to exist, any provider can write to it regardless of their platform.
• TMNA ownership enforced in the schema: The dealer_code and provider_id fields are required on every hit, ensuring TMNA can always attribute data to a specific dealer and provider without relying on vendor-side logic.
• CDP-extensible: The user.session_id field is architected to accept a hashed identity value when TMNA activates its CDP; no re-instrumentation required.
• iFrame event passthrough: Embedded tools communicate back to the parent page via postMessage, the schema defines the required payload structure for each tool category so providers know exactly what to fire.

Implementation Recommendations

Provider-specific implementation guidance derived from the TMNA-approved spec clear enough that any certified provider can implement consistently without bespoke Merkle involvement for every site.

• Per-category implementation guides: Separate guidance for website providers, chat tools, digital retail tools, trade-in tools, and service schedulers accounting for each category's architectural constraints.
• Acceptance criteria: Explicit pass/fail definitions for every required event, so providers know exactly what QA validation will test.
• Platform-specific notes: Where a provider's platform creates a constraint, the guide documents the approved workaround or alternative implementation path.
• TMNA approval gates: No provider receives implementation guidance until the underlying spec has received explicit TMNA sign-off.

Data Literacy & Consulting

Structured working sessions with all 41 certified providers translating the TMNA-approved spec into shared understanding before any implementation begins.

• Provider-specific sessions: Each certified provider receives a dedicated spec review covering requirements, technical questions, and platform-specific constraints not a generic group call.
• Environment inventory: CMS, TMS, and iFrame architecture confirmed per provider so platform limitations are documented before implementation begins.
• Acceptance criteria walkthrough: Providers understand exactly what QA will test eliminating the ambiguity that produces re-work and implementation delays.
• Direct engagement model: Merkle operates as an extension of TMNA engaging providers directly for day-to-day execution, with TMNA providing governance and escalation support.

Provider Training

Hands-on training built around the TDDS spec giving each provider's technical team the context and confidence to implement correctly the first time.

• Role-specific content: Training structured for the technical implementers at each provider specific guidance on the TMNA data layer and acceptance criteria they need to pass.
• Real TDDS use cases: Training uses actual TMNA examples not sample data so providers understand the business context behind each event they're implementing.
• Category cohorts: Providers grouped by category for training shared constraints, shared guidance, efficient use of provider time.
• Office-hour support: Structured Q&A availability during implementation windows so providers can resolve technical questions without blocking progress.

Implementation Guidance

Active technical support during the implementation window resolving blockers, enforcing spec consistency, and tracking progress across all five provider categories simultaneously.

• Website Providers (7): Phased first foundational layer before embedded tools. All 7 currently push to Adobe Analytics; implementation standardizes trigger conditions, naming conventions, and required attributes.
• Digital Retail (10): iFrame event passthrough with standardized action schema. Payment estimator and full DR flows covered.
• Chat Tools (8): Post-message bridge vs. direct dataLayer write assessed per provider. Tracking capability varies; guidance reflects each provider's actual architecture.
• Trade-In (7): Widget events: start, step, valuation received, completion. Abandonment tracking required at each funnel step.
• Service Scheduler (9): Appointment funnel: start, step, confirmation, abandonment. Nine providers with high variability in current capability.

QA & Certification Readiness

A four-stage QA process ensuring every provider implementation is accurate, complete, and TMNA-spec-compliant before the framework goes live, zero tolerance for drift.

Data Quality Index

A size-stratified scoring framework giving TMNA comparable, defensible data quality benchmarks across all 41 providers, and a factual basis for holding each one accountable at certification renewal.

• Eliminates composition bias: A provider serving primarily Size A dealers will appear stronger on raw KPIs than one serving Size E dealers, even if implementation quality is identical. Raw scores reward portfolio composition, not execution quality.
• Exposes implementation gaps: Size-stratified views reveal whether data quality inconsistencies are provider-wide or concentrated in specific dealer cohorts, a critical distinction for targeted remediation.
• Sets fair benchmarks: TMNA holds each provider accountable to the performance norms of the segment they actually serve; not a network-wide average that disadvantages providers focused on smaller dealers.
• Prioritizes QA resources: Size A and B dealers receive QA attention first, the 270 highest-volume sites where data quality gaps most affect TMNA's enterprise reporting and media attribution decisions.

Remediation SLA's

Formal cure periods with defined resolution deadlines ensuring that every gap identified in QA review has an owner, a timeline, and a consequence for non-resolution.

• Gap identification: DQI scoring and four-stage QA reviews surface implementation gaps with specificity exact event, exact provider, exact failure mode.
• SLA clock starts at failure: Every failed QA check triggers a formal cure period. The provider receives a documented gap statement and the specific acceptance criteria they failed.
• Escalation path: Gaps unresolved within the cure period are escalated to TMNA/TDDS program leadership with Merkle's documented evidence for contractual enforcement.
• TMNA leads enforcement: Merkle tracks, documents, and escalates. TMNA holds contractual authority and leads enforcement conversations with providers directly.

Provider Certification Renewal Gates

Compliance with the TMNA-approved tagging specification embedded as a mandatory condition of TDDS certification making data quality a permanent, self-enforcing program requirement.

• Spec compliance as certification condition: TDDS will formalize the tagging spec in an update to provider governance materials making implementation a permanent certification requirement, not a one-time project ask.
• Annual renewal QA gate: Each provider's DQI score and QA audit results are reviewed at certification renewal providers who have drifted face a formal remediation requirement before renewal is granted.
• New provider onboarding standard: Any new TDDS-certified provider must demonstrate compliance as a condition of initial certification the framework becomes self-perpetuating.
• Decertification backstop: Persistent non-compliance can result in decertification the program's ultimate enforcement lever, held exclusively by TMNA/TDDS.

Structured Handoff to TMNA Ops

A planned, documented transition that leaves TMNA's internal team fully capable of operating, monitoring, and evolving the analytics framework independently with no ongoing Merkle dependency.

Ongoing Governance & Enhancements

A persistent governance layer running beneath all three phases and continuing post-handoff that keeps the measurement framework accurate, current, and aligned with TMNA's evolving program needs.

• Bi-weekly QA cadence: Regular DQI scoring reviews across all provider categories a continuous quality signal, not a single end-of-project audit.
• Alert framework: Event volume drop-off monitoring in DataTrue. When a provider's tag implementation degrades, TMNA sees it in real time.
• Enhancements roadmap: Structured process for incorporating new TDDS-certified providers, spec evolution, and KPI additions.
• Certification renewal integration: Annual provider certification cycle includes QA gate review governance embedded into TDDS's existing operating rhythm.

How the Machine Runs

An adaptive transformation structure built on agile delivery drawing on Merkle's deep bench of specialists to meet program needs at every phase while maintaining strategic alignment and accountability.

Meet the Team

An integrated team of analytics architects, delivery leaders, and automotive specialists certified in Adobe Analytics and CJA, with direct experience managing multi-tier dealer ecosystems at scale.

Case Studies

Analogous engagements demonstrating Merkle's ability to standardize analytics across complex multi-site ecosystems, govern multi-vendor implementations, and deliver TMNA-scale programs.

References

Two client contacts available for TMNA to speak with directly both from engagements involving multi-site analytics ecosystems, standardized tagging architectures, and complex vendor governance models.

• Multi-site / multi-entity ecosystem: Global automobile retailer engagement covered Tiers 1, 2, and 3 across 2,400 dealer sites with 7 certified development providers the closest direct analog to the TDDS scope.
• Standardized tagging architecture: Global Mobility Company engagement established a centralized, event-driven data layer standardizing data collection across all digital experiences directly mirroring the TMNA data layer spec objective.
• OEM with franchise model: Automotive experience across Volkswagen, Ford, Hyundai (Nicholas von Hahn) and Nissan/Infiniti (Adriana Grajales at Critical Mass) demonstrates familiarity with OEM-to-dealer governance structures and multi-tier analytics accountability.
• Multi-brand governance: Global Rental Car Company engagement unified analytics across three brands into a single trusted Adobe ecosystem analogous to the TDDS challenge of unifying 41 certified provider implementations into one TMNA-owned data architecture.