Connect Triple Whale to Rig

    Bring Triple Whale's pixel attribution into your warehouse: summary metrics, order-level customer journeys, and channel ad performance. Once it sits beside your Shopify orders and raw platform spend, you can interrogate the attribution rather than take it on trust.

    Requirements
    Access to Data → APIs in Triple Whale, plus your Shopify domain
    Time required
    5 mins

    Before you start

    • Access to Data → APIs in Triple Whale.
    • Your Shopify domain, the .myshopify.com one rather than your customer-facing domain. Every Triple Whale endpoint is scoped to a shop, so Rig needs it explicitly.

    Create an API key

    1. In Triple Whale, go to Data → APIs.
    2. Click Generate.
    3. Grant all three scopes listed below, then create the key and copy it.

    Grant all three scopes

    Triple Whale scopes its keys per endpoint family, and each one gates a different part of what Rig syncs:

    • Summary Page: Read, for the pre-aggregated headline metrics
    • Pixel Attribution: Read, for order-level attribution and customer journeys
    • The SQL and Data-Out scope, for the ad performance and order financial tables

    A missing scope hides only its own streams
    This is the useful part: it does not fail loudly. Leave one scope off and the rest of the sync works perfectly while those tables simply never appear. If a stream you expected is missing, check the key's scopes before anything else.

    Connect it in Rig

    1. In Rig, open Connections and go to Sources & actions.
    2. Search for Triple Whale and open the card.
    3. API key: paste the key.
    4. Shop domain: your Shopify domain, in this shape:
      example.myshopify.com
    5. API base URL: leave blank.
    6. Days of SQL-table history on first sync: defaults to 365. Ad-level daily rows get large, so raise it only if you need more than a year.
    7. Click Test, then Sync.

    What Rig pulls in

    Triple Whale lands in its own triple_whale schema:

    • Summary: the pre-aggregated Summary Page metrics
    • Orders with journeys: row-level orders carrying Triple Pixel attribution, with each order's touchpoint journey in a related table
    • Ads metrics daily: channel ad performance by day
    • Orders table: order financials

    Summary and journeys backfill roughly two years regardless of the setting above, which only governs the two SQL-derived tables.

    Reading the numbers correctly

    Two things will make Rig's figures look wrong when they are not.

    • Triple Whale works in your shop's timezone, not UTC. The Summary Page and attribution endpoints both use the timezone configured on the shop. If you compare a Triple Whale day against a warehouse table stored in UTC, the edges will not line up, and the difference shows up as a shifted day rather than a wrong total.
    • Recent days keep changing. Attribution lands late and platforms restate spend, so Rig re-pulls a trailing 14 days on every sync. Yesterday's ROAS is provisional by nature.

    Troubleshooting

    • Some streams are missing and the rest work: a scope was not granted. Check the key in Data → APIs against the three above.
    • Authentication fails: the key goes in as a bare value with no Bearer or Token prefix. If you copied it from documentation that added one, strip it.
    • The shop is not recognised: use the .myshopify.com domain, not the storefront domain your customers see.
    • Numbers disagree with the Triple Whale dashboard: check the timezone and the trailing 14 days above before treating it as a sync problem.

    Was this guide helpful?