Browse all topics
Marketing Operations Glossary

31 terms

Web, tracking, and consent

TagA small piece of tracking or marketing code.
Tag managerA controlled system for deploying and managing tags.
Data layerA structured object exposing page and user events to tracking tools.
EventA defined user or system action recorded for analysis.
Event parameter / propertyContext attached to an event.
PixelA browser-based tracking request, usually used by ad platforms.
CookieBrowser storage used for sessions, preferences, and identifiers.
First-party dataData collected directly through the company's own relationships.
Third-party dataData obtained from an outside provider without a direct user relationship.
Zero-party dataInformation a person intentionally provides about preferences or needs.
First-party cookieA cookie set under the visited site's domain context.
Third-party cookieA cookie associated with a different domain, historically used for cross-site tracking.
Client-side trackingThe browser sends tracking data.
Server-side trackingA server sends data directly to another system.
Conversion API / CAPIA server-to-server method for sending conversion events to an ad platform.
Consent management platform / CMPCollect and enforce visitor consent choices.
Consent modeAdjust tag behavior based on stored consent state.
PIIPersonally identifiable information.
Sensitive dataData requiring stronger protection due to harm, regulation, or company policy.
Data minimizationCollect only what is needed for a defined purpose.
Purpose limitationUse collected data only for the disclosed and legitimate purpose.
Retention policyRules defining how long data is kept.
Opt-inA person affirmatively agrees to receive or allow something.
Opt-outA person withdraws or refuses participation.
Double opt-inRequire confirmation after the initial signup.
Preference centerLet people choose communication topics and frequency.
Do not contact / DNCA system-level restriction against outreach.
Email authenticationTechnical proof that sending domains and systems are authorized.
SPFDNS policy identifying permitted sending infrastructure.
DKIMCryptographic signature proving message integrity and domain authorization.
DMARCDomain policy and reporting built on SPF/DKIM alignment.

Quick answers

Web, tracking, and consent FAQs

What is included in the web, tracking, and consent topic?

The web, tracking, and consent topic is a collection of 31 marketing operations concepts used to plan, operate, govern, or evaluate this area of work. The grouping helps readers understand related language as a connected operating system rather than a list of isolated definitions.

For example, the topic includes Tag, Tag manager, Data layer, Event, Event parameter / property. A professional can open those entries together when preparing a project, documenting a process, or aligning terminology with another team.

Which web, tracking, and consent terms should I learn first?

Useful starting terms for web, tracking, and consent include Tag, Tag manager, Data layer, Event, Event parameter / property. These concepts provide an entry point, but the best sequence depends on the workflow, system, or decision you are responsible for.

For example, someone beginning a project in this area can read the five starting terms, compare their examples with the organization’s current process, and then follow the related-concept links to fill specific knowledge gaps.

How should I use these web, tracking, and consent definitions?

Use these definitions as a shared starting point, then document the exact rules, owners, systems, thresholds, and exceptions used by your organization. A glossary creates common language, but operational agreement determines how the concept behaves in practice.

For example, a team can begin with the glossary definition of Tag, then add its own entry criteria, responsible role, source system, reporting field, and escalation path before using the term in automation or executive reporting.