Skip to main content

​
Available Datasets

The datasets available for data warehouse integration are designed to provide a comprehensive view of your marketing data. Not only do they provide an up to date view of your marketing data, but they also provide a standardized set of schemas that can be used as a your marketing data foundation.
  • First-Party Event Data: User-generated events and outcomes built on Rockerbox first party tracking.
  • Attribution Data: Modeled credit and attributed revenue.
  • Platform Data: Ad platform-reported spend, conversions, and performance metrics.
  • Normalization & Metadata: Lookup, mapping, and enrichment tables for standardized reporting across sources.

​
Schema Listing

TypeSchemaDescription
First-Party EventsConversion DataA log-level dataset with one row per conversion event occurrence, including user identifiers, timestamps, order metadata, and any additional context passed to Rockerbox.
First-Party EventsClickstreamA log-level dataset with one row per Page View and Conversion event tracked onsite, attributed to click-based marketing touchpoints with standardized tier structure and spend keys applied.
First-Party EventsClickstream Event ParametersA log-level dataset containing key-value event parameters associated with each Clickstream event, supporting detailed behavioral analysis and custom reporting.
AttributionLog Level MTAA log-level dataset with one row per marketing touchpoint in each user path to conversion, supporting user journey analysis and custom reporting based on Rockerbox attribution.
AttributionAggregate MTAAn aggregate dataset providing attributed conversions, revenue, and spend across all channels, structured as a pivot of log-level MTA and unioned with aggregate spend data
PlatformPlatform - <Platform>Platform-reported spend, conversions, and performance metrics. Supported Platforms: Google, Meta, Bing, TikTok, Snapchat, Pinterest, LinkedIn.
Normalization & MetadataTaxonomy LookupLatest reporting taxonomy for all channels with spend tracking. Used to apply mapping updates over historical data.

​
Entity Relationship Diagram

​
ER Diagram Notes

  • Each Log Level MTA record optionally maps to a Taxonomy Lookup record via spend_key → join_key
  • Each Aggregate MTA record optionally maps to a Taxonomy Lookup record via platform_join_key → join_key