> ## Documentation Index
> Fetch the complete documentation index at: https://data-foundation.rockerbox.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Schema Overview

> Learn about the datasets available for data warehouse integration

## 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

| Type | Schema | Description |
| - | - | - |
| First-Party Events | Log Conversions | Event-level dataset with one row per conversion event occurrence, including geographic, device, and revenue information and excluding PII. |
| First-Party Events | Log Conversions User Identifiers | Event-level dataset with one row per conversion event occurrence, including only user identifiers and any PII tracked on each conversion. |
| Attribution | Log MTA | Event-level dataset with one row per marketing touchpoint in each user path to conversion, excluding all PII. |
| Attribution | Log MTA User Identifiers | Event-level dataset with one row per marketing touchpoint in each user path to conversion, including only user data associated with each marketing touchpoint. |
| Attribution | Aggregate MTA | 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 |
| Platform | Platform - `<Platform>` | Platform-reported spend, conversions, and performance metrics. Supported Platforms: Google, Meta, Bing, TikTok, Snapchat, Pinterest, LinkedIn. |
| Normalization & Metadata | Taxonomy Lookup | Latest reporting taxonomy for all channels with spend tracking. Used to apply mapping updates over historical data. |
| Normalization & Metadata | Conversion Event Metadata | Metadata of all conversion events tracked in Rockerbox.. |

***

## Entity Relationship Diagram

**Note**:
This diagram captures join keys and important fields to illustrate relationships between entities. Complete field references are documented per schema.

```mermaid theme={null}
erDiagram
   %% FIRST-PARTY EVENTS: Conversions
   LOG_CONVERSIONS {
       string log_conversion_id
       timestamp timestamp_conv
       date date
       string action
       string currency_code
   }

   LOG_CONVERSIONS_USER_IDENTIFIERS {
       string conversion_event_id
       string date
       string log_conversion_id
       string external_id
       string order_id
       string uid
   }

   %% ATTRIBUTION: Multi-Touch Attribution
   LOG_MTA {
       string conversion_event_id
       date date
       string log_mta_id
       string log_conversion_id
       string platform_join_key
       int sequence_number
       timestamp timestamp_events
       timestamp timestamp_conv
       string event_type
       string platform
       string tier_1
       string tier_2
       string tier_3
       string tier_4
       string tier_5
   }

   LOG_MTA_USER_IDENTIFIERS {
       string conversion_event_id
       date date
       string log_mta_id
       string uid_event
       string hash_ip_event
       string user_agent_event
       string base_id
   }

   AGGREGATE_MTA {
       string conversion_event_id
       string platform_join_key
       date date
       string platform
       string tier_1
       string tier_2
       string tier_3
       string tier_4
       string tier_5
       float included_spend
       float normalized
   }

   %% REFERENCE DATA
   CONVERSION_EVENT_METADATA {
       string conversion_event_id
       string conversion_event_name
       date first_reporting_date
       bool active
   }

   TAXONOMY_LOOKUP {
       string join_key
       string parent_platform
       string platform
       string tier_1
       string tier_2
       string tier_3
       string tier_4
       string tier_5
   }

   %% RELATIONSHIPS: Conversions
   LOG_CONVERSIONS ||--|| LOG_CONVERSIONS_USER_IDENTIFIERS : "date, conversion_event_id, log_conversion_id"

   %% RELATIONSHIPS: Attribution
   LOG_CONVERSIONS ||--|{ LOG_MTA : "date, conversion_event_id, log_conversion_id"
   LOG_CONVERSIONS_USER_IDENTIFIERS ||--|{ LOG_MTA : "date, conversion_event_id, log_conversion_id"
   LOG_MTA ||--|{ LOG_MTA_USER_IDENTIFIERS : "date, conversion_event_id, log_mta_id"

   %% RELATIONSHIPS: Metadata joins
   CONVERSION_EVENT_METADATA ||--o{ LOG_CONVERSIONS : "conversion_event_id"
   CONVERSION_EVENT_METADATA ||--o{ LOG_CONVERSIONS_USER_IDENTIFIERS : "conversion_event_id"
   CONVERSION_EVENT_METADATA ||--o{ LOG_MTA : "conversion_event_id"
   CONVERSION_EVENT_METADATA ||--o{ LOG_MTA_USER_IDENTIFIERS : "conversion_event_id"
   CONVERSION_EVENT_METADATA ||--o{ AGGREGATE_MTA : "conversion_event_id"

   %% RELATIONSHIPS: Taxonomy joins
   TAXONOMY_LOOKUP |o--o{ LOG_MTA : "platform_join_key -> join_key"
   TAXONOMY_LOOKUP |o--o{ AGGREGATE_MTA : "platform_join_key -> join_key"
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.