Skip to main content

Overview

With a Snowflake Reader Account, you can access Rockerbox datasets and egress the data to the platform of your choice.
  • You do not need to be a Snowflake customer to have access to a reader account.
  • You will not pay for any storage or compute for this account; these are billed to Rockerbox as the provider of the account.
📊 Rockerbox implements monthly credit quota on the account, and will work with you to ensure that you can run the egress out of Snowflake within the monthly credit quota.

Pre-Requisites

  • An account with a data warehouse provider where you will store the data egressed from the Snowflake Reader Account.

Step 1: Access your reader account 

  • Rockerbox support will provide you with your: (1) username (2) password (3) account URL
  • Login to your Snowflake reader account

Step 2: Sync Rockerbox Data Sets

  • Choose which datasets to share and create the share tables in the Rockerbox UI:
    • Platform Data: Select the ad platforms you actively use.
    • Rockerbox Data: Select Conversion and any Log Level MTA datasets for each conversion event that you need.
  • Click Sync this dataset when ready.
📦 aggregate_mta and taxonomy_lookup tables are automatically created in the data share.

⚠️ Backfill Notes

  • Platform Performance Schemas: No data is automatically backfilled. This can be backfilled on a limited basis upon request to support@rockerbox.com.
  • Rockerbox First Party Data Schemas: For each conversion dataset, Rockerbox will backfill based on the conversion event “First Reporting Date” in Rockerbox.
    💡 If no date is set, Rockerbox backfills one day of data. This process can take up to 24 hours.

Step 3: Query your new data tables

Open a new SQL worksheet to access the query editor and confirm that you can run a query against a share table. Test setup

Step 4: Build egress pipeline

Objective: Pull Rockerbox data out of a Snowflake reader account and load it to an external destination. General Notes
  • Run this script for each table that needs to be egressed.
  • Rockerbox recommends processing updates 3 times per day for the most recent 2 days.
  • For longer lookback windows, you can ingest updates on a rolling basis depending on your integrations. Work with Rockerbox Support to determine the right update frequency and configure the lookback appropriately.

Step 1: Create python connector

Step 2: Create a list of dates to process for a given table

Step 3: Load the data to your destination