Triple Whale connector
Use Triple Whale attribution and profit context in Adrails
Triple Whale contributes the blended performance view that individual ad platforms do not compute. Adrails reads supported summary metrics and keeps them attributable to the connected Shopify store.
Reviewed Sep 22, 2026
- Authentication
- API key
- Required context
- One Shopify store
- Access
- Summary read
01
Add a blended measurement source
Meta reports its own attributed outcomes. Triple Whale provides a separate blended view across spend, revenue, acquisition cost and profit-related metrics. Adrails can use both while identifying which source produced each figure.
This helps teams discuss a performance change without silently treating one platform's attribution as the whole business result.
02
Bind the connection to a known store
The Triple Whale API key does not identify the store by itself in this workflow, so Adrails requires exactly one Shopify store in the workspace before connecting it. That prevents data from being attached to the wrong commerce context.
The connector verifies the key before storage and reads the summary scope required for analytics.
03
Keep the attribution model visible
An analysis should name whether it uses Meta, Shopify or Triple Whale values. Differences are evidence to investigate, not numbers to overwrite until they match.
Disconnecting removes the stored key and stops future summary synchronization.
FAQ
Common questions
Why must Shopify be connected first?
Adrails uses the single connected Shopify store to identify which shop the Triple Whale summary belongs to.
Does Adrails replace Triple Whale?
No. Triple Whale remains the attribution source; Adrails uses its supported summary metrics as agent context.
Put the workflow into one workspace.
Connect a Meta ad account, ask an agent to prepare the work and approve the exact result.