Appearance
Connect Triple Whale
Connect Triple Whale so Nexus can attribute orders to the ad that drove them. The Triple Whale card sits under Settings > Integrations, in the Analytics category. Its description reads "Attribution & profit analytics."
Problem and intended user
The media buyer (the person who runs your paid ads) needs to know which ad drove which order. Some orders reach the store with no ad id in the click, so Nexus cannot tie them to an ad on its own. Unmatched orders can make an ad's revenue and profit look lower than they are. You connect Triple Whale to close that gap.
Current workflow
Without Nexus, the media buyer reads the reports in Meta Ads Manager or Google Ads. The buyer exports orders from Shopify admin or Triple Whale into a spreadsheet and matches them to ads by hand.
Prerequisites
- A Triple Whale account for this store.
- A Triple Whale API key with data read access, and your
.myshopify.comshop domain. - A connected ad platform. Nexus matches Triple Whale's ad ids to the ads it synced from Meta Ads or Google Ads. Without synced ads, there is nothing to match.
How Nexus works
Nexus asks Triple Whale for your orders and touchpoints. A touchpoint is one ad click or visit that led to an order. Nexus matches Triple Whale's ad and campaign ids to the ads in your own ad accounts. Fixed rules do this matching. AI does not. Nexus never guesses. When an ad id matches no synced ad, Nexus falls back to the campaign if it knows it. Otherwise the touchpoint counts as unresolved. An ad in a different campaign than Triple Whale names is refused and counts as campaign mismatched.
Nexus syncs Triple Whale once a day. Settings > Store Status lists Triple Whale sync with its schedule and its last run. See Store Status.
Nexus records each run in the activity log. You act at two points only: you create the key in Triple Whale, and you save the connection in Nexus.
Triple Whale data feeds these places:
- Matched revenue, and the line "% of this period's orders could be matched to a specific ad", on Performance > Ad performance. See Ad performance.
- The Match column of the Attributed orders tab on an ad. See Ad detail.
- The Attribution card of the order page. See Order detail.
- The Triple Whale card and its activity window in Settings > Integrations.
- The Triple Whale sync row in Settings > Store Status.
Without Triple Whale, orders still match through your ad link tags and the Google click id. Matched revenue exists either way. Triple Whale adds exact-ad matches.
Create the API key in Triple Whale
WARNING
Triple Whale shows the key only once, when you create it. Copy it somewhere safe before you close that screen. Neither Triple Whale nor Nexus can show it again.
- In Triple Whale, go to Data > APIs.
- Create a key with data read access.
- Copy the key.
Triple Whale ties an API key to the user who created it. If that person loses access to their Triple Whale account, the key stops working. This is the most likely cause if the connection fails later.
Connect Triple Whale
- Go to Settings > Integrations.
- Click the Triple Whale card.
- Paste the key into API Key.
- Check Shop Domain. Nexus fills in your Shopify domain when it knows it. Use the
.myshopify.comaddress of the store that the key belongs to. - Click Save Connection. The button reads Validating… while Nexus checks the key with Triple Whale.
On success, Nexus shows "Triple Whale connected to" and your domain, then closes the dialog. The card now shows View activity.
Triple Whale data does not appear right after you save. Nexus syncs once a day, so the first data arrives after the next daily run. Until then the activity window reads Not synced yet.
After you connect, the API Key field shows a masked message. Nexus never shows a saved key. To change the shop domain, or to reconnect after a failure, enter the key again and click Save Connection. Every save needs both fields.
Disconnect Triple Whale
WARNING
Disconnect Triple Whale acts at once and asks for no confirmation.
Open the card and click Disconnect Triple Whale. The button shows only while the card is connected. Nexus erases the saved API key and stops syncing. It shows "Triple Whale disconnected." and clears both fields. Nexus does not delete the key in Triple Whale. Remove the key there if you want it gone.
Exact output
Matched orders
An order that Triple Whale matched shows Matched by Triple Whale in the Match column of an ad's Attributed orders tab. The same words appear on the Attribution card of the order page. See Ad detail and Order detail.
The activity log
Click View activity on the connected card to open Triple Whale activity. It lists the runs Nexus recorded over the last 7 days. The window shows one row per day Nexus ran. It prints no schedule and no next run. A health badge sits at the top.
| Badge | Meaning |
|---|---|
| Healthy | The recorded runs are fine. |
| Degraded | Some runs failed. The badge reads, for example, "Degraded — 2 of 7 runs failed". |
| Reconnect needed | The API key no longer works. Save the connection again with a new key. |
| Not synced yet | Nexus has recorded no run yet. |
Under the badge, Ad resolution rate shows how many touchpoints from your connected ad platforms Nexus matched to an ad. Orders that came from email, direct visits or organic search are not in that count. If no ad-platform orders exist in the window, the line reads "not yet measured".
Each run is a row with a date, a status badge, the orders and touchpoints it fetched, and the counts of resolved and unresolved ads. A campaign mismatched count shows when it is not zero. Click Show details for row counts, API calls and start and end times. A run with a problem shows an error code and message under its date.
| Run status | Meaning |
|---|---|
| Pending | The run started and has not finished. |
| Success | Nexus wrote every day of the window. |
| Partial | Nexus wrote some days and failed on others. The error line reads "N of M days failed" and names the dates. |
| HTTP error | Triple Whale returned a server error. |
| Credentials invalid | Triple Whale rejected the key, or did not recognise the shop domain. |
| Rate limited | Triple Whale asked Nexus to slow down. |
| Skipped | Nexus did nothing that day: the sync is switched off, the stored key is unreadable, or no active connection exists. A skipped run counts as a healthy day. |
| Failed (permanent) | Triple Whale refused the request, the result was too large even for one day, or an unexpected error occurred. |
Nexus does not retry a failed run on the same day. The next daily run fetches the window again, so Nexus tries a failed run again once a day. Credentials invalid is the status you fix yourself: save the connection again with a new key.
What to do with it
| What you see | Decision or action | Owner |
|---|---|---|
| Matched by Triple Whale on an order | Open the order to see how Nexus matched it to the ad. | media buyer |
| Reconnect needed, or Credentials invalid on a run | Generate a new key in Triple Whale, then click Save Connection in Nexus. | ecommerce manager (the person who runs the store) |
| Degraded, Partial or Rate limited | Read the error message on the failed runs. | ecommerce manager |
| A low Ad resolution rate | Check that Meta Ads or Google Ads is connected and synced. | media buyer |
Expected value and measurement
Triple Whale can help Nexus tie more orders to the ad that drove them. That can make an ad's matched revenue more complete.
To check the effect:
- On Performance > Ad performance, compare a period that ended before you connected with a period that starts after the first Triple Whale run. Compare Matched revenue and the bottom line, which says what share of the period's orders Nexus matched to a specific ad.
- Leave the days just before you connected out of the comparison. Each run also fetches recent days from before the connection, so matches for those days can change numbers that Nexus showed earlier.
- After the first run, read Ad resolution rate under View activity on the Triple Whale card in Settings > Integrations. It covers only the last 7 days the log shows.
Seasons, promotions and ad changes run at the same time, so you cannot isolate the effect of Triple Whale alone.
Limitations and exceptions
- No ad id on the click. Orders from App campaigns, and from Performance Max rows below the asset group, arrive without an ad id. An empty Attributed orders list does not mean that the ad drove no revenue.
- A missing row means Nexus did not run that day. It does not mean Nexus ran and found nothing.
If the save fails, the dialog stays open and shows one of these messages.
| Message | What to do |
|---|---|
| Triple Whale rejected this API key. | Generate a new key in Triple Whale under Data > APIs. |
| This key is valid but cannot query Triple Whale's data API. | Generate the key again with data read access. |
| Triple Whale did not recognise that shop domain for this API key. | Check the .myshopify.com domain. Check that the key came from this store's Triple Whale account. |
| Triple Whale is temporarily unavailable. | Wait, then try again. Your key is not the problem. |
| Enter the API key generated in Triple Whale (Data > APIs). | API Key is empty or too short. Fill it in. |
| Enter your Shopify shop domain (the .myshopify.com address). | Shop Domain is empty or too short. Fill it in. |
When a connected store has no run in the window, the activity log reads "No runs in the last 7 days." If the log fails to load, it reads "Could not load Triple Whale activity. Try again shortly."
In Demo Mode, connecting and disconnecting are turned off. Nexus shows "Disable demo mode to connect Triple Whale" or "Disable demo mode to disconnect Triple Whale".