Skip to main contentSkip to navigationSkip to footer
    Strategy

    Marketing Context Layer: Define KPIs Before Using AI

    In short

    Why valid SQL can produce misleading marketing reports. A context card for lead definitions, data sources, filters and brand knowledge.

    November 4, 20263 min readDavies Meyer Team
    Share:
    Marketing Context Layer: Define KPIs Before Using AI

    Table of Contents

    Two reports show different lead counts. Both queries execute successfully. The disagreement may lie in what “lead” means: one counts submitted forms, the other qualified companies. A technically valid query is not necessarily a valid business answer. An agent accelerates this inconsistency if it lacks the definitions.

    The engineering context

    On 9 October 2026 LinkedIn Engineering described an internal Data Context Layer. Agents can generate valid SQL while selecting the wrong datasets or omitting required filters. Automatically generated dataset profiles are combined with human-maintained definitions, join rules and constraints. Reviewed context stays separate from automatically refreshed profiles.

    Adam Greco had already used Marketing Context Layer on 2 June 2026, including brands, products and channel knowledge. We use our own working definition of an existing term, not a claimed industry standard or a phrase invented here.

    A fictional reporting conflict

    A team asks an agent for “German leads last month”. The form system counts submissions. The CRM counts qualified business contacts. The ad account uses click-attributed conversions with a different time basis. These cannot be presented as interchangeable measurements.

    First clarify the decision: technical delivery, sales qualification or campaign optimisation? Each requires different data and definitions.

    The marketing context card

    FieldWhat to documentTypical failure without it
    MetricDefinition and accountable ownerTreat a form as a qualified enquiry
    SourceAuthoritative system and freshnessTreat an old export as current truth
    TimeEvent, timezone and intervalConfuse click and qualification dates
    RegionHow country or market is determinedTreat browser location as company location
    ExclusionsTests, spam, duplicates and cancellationsCount test submissions as demand
    RelationshipsValid joins and keysCount contacts repeatedly
    UsePermissions and consent rulesEnrich personal data without authority
    Brand knowledgeApproved names and claimsOutput inconsistent product names

    This is more specific than “use our data”. The card identifies boundaries and when to ask for clarification. Missing definitions should not be replaced by confident guesses.

    Maintain context rather than uploading it once

    Assign an owner and version. If sales changes qualification criteria, reports must explain the change. Historical records should not silently be interpreted as if the new rule always applied. Refresh generated profiles without overwriting reviewed human guidance.

    Implementation may use a repository, data catalogue or structured configuration. The location matters less than discoverability, reviewability and appropriate access. A long prompt file without a change process does not solve accountability.

    Five questions for a reporting agent

    1. Which approved definition are you using?
    2. Which source and data version are you reading?
    3. Which event determines the reporting period?
    4. Which exclusions and joins affect the count?
    5. What is unknown or outside your permission?

    Present these alongside the result. A report without provenance and limits may look plausible while supporting a wrong budget decision. Technical acceptance and business review remain necessary.

    From analytics to Creative Engineering

    Context also covers approved product names, supported claims and intended audiences. Human decisions become usable in the production chain without replacing creative judgement. Comparing hooks and formats requires consistent metrics and versions.

    Start with one disputed metric and one actual report. Align definition, source and filters with marketing and data owners before automating repeated analysis. The best first improvement is often a shared understanding of a number, not another agent feature.

    Sources and context

    As of 4 November 2026. Product claims describe vendor statements, not independent evidence of outcomes. The working templates and recommendations are our editorial contribution.

    Further reading and next step

    Want to review a bounded workflow with us? Describe your project in the Agenten-Pilot. Scope, timing and pricing are agreed after the initial conversation.

    Frequently Asked Questions

    What is "Marketing Context Layer: Define KPIs Before Using AI" about?

    Why valid SQL can produce misleading marketing reports. A context card for lead definitions, data sources, filters and brand knowledge.

    The engineering context: what matters?

    On 9 October 2026 LinkedIn Engineering described an internal Data Context Layer. Agents can generate valid SQL while selecting the wrong datasets or omitting required filters.

    A fictional reporting conflict: what matters?

    A team asks an agent for “German leads last month”. The form system counts submissions. The CRM counts qualified business contacts.

    The marketing context card: what matters?

    This is more specific than “use our data”. The card identifies boundaries and when to ask for clarification. Missing definitions should not be replaced by confident guesses.

    AI solutions by Davies Meyer

    From an application to the right delivery

    Good AI applications need brand knowledge, a clear idea and the right execution. Davies Meyer brings strategy, creativity, content production and technology together. Creative Engineering is our method for making that collaboration repeatable.

    We take responsibility for the concept and quality.