FormatsCSV / JSON / XLSX / PDF RefreshMonthly review Version1.1 VerifiedSeptember 20, 2026

Marketing exports become difficult to compare when every source uses a familiar label for a slightly different measurement. This specification keeps the platform, definition, date window, and currency beside the value.

The result is a dataset another analyst can inspect without reverse-engineering what engagement meant six months later.

Designed For

  • campaign comparisons
  • audience segment research
  • channel reporting
  • marketing model prototypes

Coverage

Record unitOne campaign, channel, and audience observation
Channel scopeStored per source platform
Time fieldStart date, end date, and last verified date
CurrencyDeclared per cost field
Field Dictionary

Schema Preview

FieldTypeDescriptionExample
campaign_namestringNormalized campaign labelspring research launch
channelenumSource channelpaid_search
audience_segmentstringDeclared or modeled audience groupdata teams
engagement_ratedecimalSource-specific engagement rate0.034
observation_enddateEnd of the measured window2026-08-31
Illustrative Rows

Illustrative Campaign Records

campaign_namechannelaudience_segmentengagement_rateobservation_end
spring research launchpaid_searchdata teams0.0342026-08-31
sample dataset releaseemailanalysts0.0812026-08-31

Rows are illustrative. Rates from different platforms require their original definitions and windows.

Collection And Preparation

  • Normalize channel and campaign labels while preserving platform source fields.
  • Keep reach, impressions, clicks, engagement, and cost as separate measurements.
  • Store currency and date windows beside every cost metric.
  • Flag derived audience and competitive labels separately from observed platform values.

Known Limits

  • Attribution rules differ across platforms and should not be merged without documentation.
  • Audience labels can describe modeled groups rather than verified individuals.
  • Engagement measures are not interchangeable across channels.
  • Illustrative rows demonstrate schema only.

Useful Applications

  • compare campaign observations
  • group audience segments
  • normalize channel labels
  • prepare performance features for analysis

Change Log

  • Added public schema, sample rows, source boundaries, coverage fields, and method notes.