Analytics & Attribution
Marketing Data Dictionary for B2B Teams
A marketing data dictionary helps B2B teams define the metrics, fields, events, sources, and lifecycle stages used across analytics, CRM, dashboards, and reports.
Without shared definitions, marketing data becomes difficult to trust. One person may define a lead as any form submission. Another may define a lead as a qualified sales-ready request. A dashboard may count conversions differently from the CRM. A campaign report may use one source name while sales uses another.
A data dictionary solves this by giving the team one shared language for measurement.
For B2B marketing, this matters because decisions depend on the connection between traffic, conversions, lead quality, sales acceptance, SQLs, and pipeline movement.
Key takeaways
- A marketing data dictionary defines the terms and fields used in analytics, CRM, and reporting.
- It helps prevent confusion between leads, qualified leads, MQLs, SQLs, opportunities, and conversions.
- B2B teams should document source fields, campaign naming, lifecycle stages, event definitions, and dashboard metrics.
- A data dictionary improves reporting quality because everyone uses the same definitions.
- The goal is not documentation for its own sake. The goal is better marketing decisions.
Table of contents
- What is a marketing data dictionary?
- Why B2B teams need shared definitions
- What should be included?
- How to define lifecycle stages
- How to define source and campaign fields
- How to define conversion and event data
- How to maintain the dictionary
- Common mistakes
- FAQ
- Practical summary
What is a marketing data dictionary?
A marketing data dictionary is a structured reference document that explains what each marketing metric, field, event, and status means.
It can include definitions for:
- lead;
- qualified lead;
- MQL;
- SQL;
- opportunity;
- conversion;
- key event;
- traffic source;
- campaign;
- landing page;
- lifecycle stage;
- disqualification reason;
- sales acceptance;
- pipeline created;
- attribution field;
- dashboard metric.
The dictionary should be practical. It should help a marketer, analyst, sales manager, or founder understand how a number is created and how it should be used.
A good data dictionary answers three questions:
- What does this field or metric mean?
- Where does the value come from?
- How should the team use it in decisions?
Why B2B teams need shared definitions
B2B reporting often breaks because different teams use the same words differently.
Marketing may say a campaign generated 100 leads. Sales may say only 15 of them were usable. Analytics may show 120 conversions because it counts every form submission and resource download together. CRM may show 70 leads because some forms did not sync correctly.
The problem is not only technical. It is definitional.
A shared dictionary helps align:
- marketing reports;
- CRM records;
- sales feedback;
- campaign dashboards;
- attribution analysis;
- conversion tracking;
- weekly metrics reviews;
- leadership reporting.
When definitions are unclear, teams debate the numbers instead of making decisions.
When definitions are clear, teams can focus on what needs to improve.
What should be included?
A practical marketing data dictionary should start with the fields that affect decisions.
| Data area | What to document |
|---|---|
| Lead definitions | lead, qualified lead, MQL, SQL, sales accepted lead |
| Source tracking | source, medium, campaign, first touch, last touch |
| Conversion data | form submission, booked call, demo request, key event |
| CRM stages | lifecycle stage, lead status, opportunity stage |
| Quality fields | fit status, disqualification reason, sales acceptance |
| Campaign naming | campaign name, channel, content, audience, offer |
| Dashboard metrics | CPL, CAC, SQL rate, qualified lead rate, conversion rate |
| Ownership | who maintains the field or metric |
The dictionary does not need to document every possible field at the beginning. Start with the data that appears in reports, dashboards, and decision meetings.
If a field is used to make decisions, it should be defined.
How to define lifecycle stages
Lifecycle stages are one of the most important parts of a B2B data dictionary.
A lifecycle stage shows where a person or company is in the marketing and sales process. If these stages are unclear, reporting becomes unreliable.
A simple lifecycle model may include:
| Stage | Definition | Owner |
|---|---|---|
| Visitor | A person visits the website or tracked asset | Analytics |
| Lead | A person submits a form or provides contact information | Marketing |
| Qualified lead | The lead matches basic fit or intent criteria | Marketing / Sales |
| MQL | Marketing considers the lead worth review or nurture | Marketing |
| Sales accepted lead | Sales agrees the lead is worth follow-up | Sales |
| SQL | The lead is sales-ready based on agreed criteria | Sales |
| Opportunity | A real potential deal is created in CRM | Sales |
| Customer | The deal is closed and activated | Sales / Customer team |
The exact stages can vary. The important point is that each stage should have a clear rule.
For example, “qualified lead” should not mean “someone we like.” It should have criteria such as company type, business email, relevant need, region, budget fit, timeline, or service fit.
How to define source and campaign fields
Source data is often messy because it comes from different systems.
A data dictionary should explain how source fields are created and used.
Useful source fields include:
| Field | Definition |
|---|---|
| First-touch source | The first known source that introduced the visitor or lead |
| Last-touch source | The last known source before conversion |
| Lead creation source | The source connected to the form submission or lead creation |
| UTM source | The campaign source from tagged URLs |
| UTM medium | The channel type from tagged URLs |
| UTM campaign | The campaign name from tagged URLs |
| Landing page | The first page of the session |
| Conversion page | The page where the lead action happened |
The dictionary should also explain naming rules.
For example:
- use lowercase source names;
- do not mix
linkedin,LinkedIn, andlinked_in; - do not use internal links with UTM tags;
- keep campaign names readable;
- store both source and landing page when possible.
These rules reduce cleanup later.
How to define conversion and event data
Conversions and events should be documented carefully because they often control reporting and campaign optimization.
A B2B company may track many events, but only a few should be considered primary business actions.
A useful dictionary should separate:
| Type | Example | Use |
|---|---|---|
| Primary conversion | qualified form submission, consultation request, demo request | Business performance reporting |
| Secondary conversion | resource download, email click, file download | Engagement and nurture analysis |
| Diagnostic event | scroll depth, button click, form start | UX and behavior diagnostics |
| CRM-stage conversion | MQL, SQL, opportunity created | Sales and pipeline reporting |
This prevents a common mistake: treating every tracked action as equal.
A form submission from a high-intent service page should not have the same meaning as a scroll event or newsletter signup.
How to maintain the dictionary
A marketing data dictionary should be maintained like an operating asset.
It should not be created once and forgotten.
Update it when:
- a new form is launched;
- a new campaign naming rule is introduced;
- CRM stages change;
- a new dashboard is created;
- a new analytics event is added;
- a source field changes;
- sales qualification rules change;
- reporting definitions are updated.
A practical maintenance process can include:
- Assign an owner.
- Review changes before implementation.
- Update definitions when fields change.
- Keep examples for unclear fields.
- Remove unused fields.
- Review the dictionary during reporting problems.
- Use it during onboarding for marketers, analysts, and contractors.
The owner does not need to approve every small change, but someone should be responsible for keeping the system consistent.
A practical data dictionary template
A simple dictionary can use the following structure:
| Field | Description |
|---|---|
| Field name | Exact name used in analytics, CRM, or dashboard |
| Business definition | Plain-language meaning |
| System source | Where the data comes from |
| Allowed values | Accepted options or formats |
| Owner | Person or team responsible |
| Used in reports | Where the field appears |
| Update rule | When the value changes |
| Example | Example of correct use |
This format keeps the dictionary useful for both technical and non-technical users.
Common mistakes
Defining too many fields at once
A large dictionary can become hard to maintain. Start with the fields used in decisions.
Using vague definitions
Definitions like “good lead” or “engaged user” are not enough. The rule should be specific.
Not involving sales
B2B marketing definitions often need sales input, especially for qualification, SQLs, and rejection reasons.
Ignoring source naming
Source and campaign naming problems can damage attribution and reporting.
Treating the dictionary as a static document
Marketing systems change. The dictionary should change with them.
Not connecting definitions to dashboards
If dashboard metrics are not defined, the team may misread the numbers.
FAQ
What is a marketing data dictionary?
A marketing data dictionary is a reference document that defines the metrics, fields, events, sources, and lifecycle stages used in analytics, CRM, dashboards, and reporting.
Why does a B2B team need one?
B2B teams need shared definitions because marketing, sales, analytics, and leadership often use the same words differently. A data dictionary prevents confusion and improves reporting quality.
What should be documented first?
Start with lead stages, conversion events, source fields, campaign naming, CRM statuses, disqualification reasons, and dashboard metrics.
Who should own the data dictionary?
Ownership usually belongs to the marketing operations, analytics, or revenue operations function. In smaller teams, the marketing owner can maintain it.
How often should it be updated?
Update it whenever tracking, CRM stages, forms, campaigns, dashboards, or qualification rules change.
Practical summary
A marketing data dictionary gives B2B teams a shared measurement language.
It helps define leads, conversions, sources, campaigns, CRM stages, and reporting metrics so that marketing and sales can make decisions from the same data.
The strongest data dictionary is simple, practical, and maintained over time. It does not exist to create documentation. It exists to make marketing measurement clearer, cleaner, and more useful.