What does Rig sync from Triple Whale?

Summary Page metrics, orders carrying Triple Pixel attribution with each order's customer journey, daily channel ad performance, and order financials. Summary and journey data backfills around two years; the SQL-derived tables default to a year on first sync.

Does Rig need every Triple Whale API scope?

It needs three: Summary Page Read, Pixel Attribution Read, and the SQL or Data-Out scope. Each one gates only its own streams, so a missing scope does not fail the sync, it just means those tables never appear.

Why do Triple Whale numbers in the warehouse keep changing for recent days?

Attribution lands late and ad platforms restate spend, so Rig re-pulls a trailing 14 days on every sync. Recent figures are provisional by nature, in Triple Whale as much as in Rig.

Can I compare Triple Whale attribution with my other sources?

That is the main reason to sync it. Once Triple Whale, Shopify and your ad platforms are in one warehouse, Rig can answer questions across all three, and the discrepancies between them become something you can quantify rather than argue about.

Analytics & product Supported

Triple Whale integration for Rig

The easiest way to connect Triple Whale to Claude and other AI tools

Triple Whale is an ecommerce analytics platform that uses its own tracking pixel to attribute orders back to the ads and channels that drove them.

Try Rig Book a demo

What Rig syncs from Triple Whale

Once connected, Rig models these objects so questions resolve to the right tables and joins:

Summary metrics
Orders with attribution
Customer journeys
Ads metrics daily
Order financials

How Triple Whale connects to Rig

Generate an API key in Triple Whale under Data then APIs, granting Summary Page, Pixel Attribution and SQL Data-Out access, and give Rig that key plus your Shopify domain. Rig syncs summary metrics, order-level attribution with each order's touchpoint journey, and channel ad performance, re-pulling a trailing window so late-attributing conversions and restated spend land correctly.

Read the step-by-step Triple Whale setup guide

Check attribution against what actually happened

Attributed revenue is the revenue a model assigns to a channel, which is not the same as the revenue that channel caused. Rig puts Triple Whale's attributed orders next to your Shopify orders and your raw platform spend in one warehouse, so you can compare what the pixel claims against what landed, per channel and per campaign, instead of comparing two dashboards by eye.

Ask Rig

Where does Triple Whale attributed revenue diverge most from Shopify orders?
Which channels does the pixel credit that our platform reporting does not?
How does blended ROAS compare with platform-reported ROAS by month?

Analyse the full customer journey, not the last click

Rig lands each attributed order alongside its touchpoint journey, so a journey is a table you can query rather than a diagram you can look at. That makes it possible to count how many touches precede a first order, see which channels open journeys versus close them, and price assisting channels honestly.

Ask Rig

How many touchpoints precede a first order, and does that differ by channel?
Which channels most often start a journey that converts later?
What is the average time from first touch to purchase this quarter?

Track ad performance beyond the retention window

Ad platforms and attribution tools keep a limited reporting history. Rig syncs Triple Whale's daily channel performance into your warehouse and keeps it, so year-on-year comparisons stay possible after the source has aged the data out, and spend is joinable to margin rather than to revenue alone.

Ask Rig

Show daily spend and attributed revenue by channel versus the same period last year
Which campaigns have the worst contribution margin once COGS is included?
How has cost per acquisition moved by channel over the last year?

Ask your Triple Whale data in Claude, ChatGPT or Cursor

Rig serves your Triple Whale data to AI assistants over MCP. Once Triple Whale is synced into your warehouse, you can ask questions in plain English from the tool you already use, and every answer is backed by validated, governed SQL.

Frequently asked questions

What does Rig sync from Triple Whale?: Summary Page metrics, orders carrying Triple Pixel attribution with each order's customer journey, daily channel ad performance, and order financials. Summary and journey data backfills around two years; the SQL-derived tables default to a year on first sync.
Does Rig need every Triple Whale API scope?: It needs three: Summary Page Read, Pixel Attribution Read, and the SQL or Data-Out scope. Each one gates only its own streams, so a missing scope does not fail the sync, it just means those tables never appear.
Why do Triple Whale numbers in the warehouse keep changing for recent days?: Attribution lands late and ad platforms restate spend, so Rig re-pulls a trailing 14 days on every sync. Recent figures are provisional by nature, in Triple Whale as much as in Rig.
Can I compare Triple Whale attribution with my other sources?: That is the main reason to sync it. Once Triple Whale, Shopify and your ad platforms are in one warehouse, Rig can answer questions across all three, and the discrepancies between them become something you can quantify rather than argue about.