Skip to main content

🚨 Required Action

All usage of the Buckets Breakdown schema must be migrated to the aggregate_mta table by April 30, 2026. After this date, Buckets Breakdown tables will stop receiving updates (historical data will remain queryable).

What’s Changing

  • New table: aggregate_mta replaces all Buckets Breakdown tables in your data share.
  • Rolled out alongside existing tables so you can build and test without impacting production.
  • aggregate_mtaΒ is fully backfilled to your first clean reporting date in Rockerbox.

Key Benefits

  • Significantly faster and more reliable delivery of aggregate attribution and spend β€” KPIs are available before your stakeholders start their day.
  • Fewer tables to query and manage with all aggregate attribution data across all conversion events available in one streamlined reporting table.

Migration Timeline

  • Deprecation date: April 30, 2026 β€” Buckets Breakdown tables stop receiving updates.
πŸ“œ Historical Access:Β Historical data in Buckets Breakdown tables will still be available after the deprecation date. We do not intend to remove these tables at this point in time.

Migration Guidance

General Notes

  • Rockerbox will not drop or rename existing Buckets Breakdown tables so as to not break your production reporting.
  • Create views to replicate Buckets Breakdown tables, suffixed with _v2.Β 
  • Change the table reference in all queries to point to the view.
  • If you don’t want to create backwards compatible views, then review the Schema Differences section below for a full accounting of the changes.
⚠️ Important: If merging aggregate_mta with historical data sourced from Buckets Breakdown schema, then lowercase all platform_join_key and taxonomy columns (tier_1–tier_5) in the historical data from the Buckets Breakdown source table to ensure consistency. Example:

Snowflake Instructions

Pre-Requisites

  • Local database and schema where you can define views.
Note:Β Rockerbox shares data via Secure Data Sharing. The shared database is read-only.

SQL Statement

SQL Parameters


BigQuery Instructions

Pre-Requisites

  • A project created with BigQuery resource enabled.
  • A dataset within the aforementioned project.
Note: these are the same pre-requisites for connecting Rockerbox with BigQuery, so there is no need to create a new project and for the specific purpose of creating these compatibility views.

SQL Statement

SQL Parameters


Redshift Instructions

Pre-Requisites

  • Local database and schema where you can define views.
  • USAGE permissions on Rockerbox external schema (Glue + S3).
Note: External schema used to share data is read-only.

SQL Statement

SQL Parameters


Schema Differences

Full Schema Diff

Many Tables > One Table

  • Before: One table per conversion event.
    • N tables: buckets_breakdown_add_to_cart, buckets_breakdown_purchase
  • After: One unified table includes conversion_event_id and conversion_event_name for segmentation.
    • One new table: aggregate_mta
  • Guidance: Add a filter to replicate current table behavior.
    • WHERE conversion_event_name = <name>

Partitioned Rows

  • Before: Spend and attributed conversions/revenue in the same row.
  • After: Attribute conversions/revenue in row whereΒ partition=mta; spend in separate row whereΒ partition=included_spend.
  • Guidance: Aggregate (SUM) metrics across relevant dimension columns (date, tier_1, tier_2, etc.) to compute KPIs such as CPA and ROAS.
🚨 Rows may look duplicated compared to the Buckets Breakdown schema because attribution and spend data are now split across separate rows. This is expected behavior.
Sample SQL (works in Redshift, BigQuery, Snowflake):

Case Differences

  • Issue: platform_join_key and tier_1Β throughΒ tier_5 may have inconsistent case vs. legacy tables in certain instances.
  • Guidance: Apply LOWER() in queries before joining or merging data from aggregate_mtaΒ with ANY of the legacy schemas.Β