Documentation · Integrations

Triple Whale is an analytics and attribution platform for Shopify brands. In FinityAi, you connect it with a personal API key so the assistant can read summary dashboard metrics for a date range and paginated orders with pixel attribution, optionally including customer-journey detail. FinityAi does not invent metrics beyond what Triple Whale's API returns for your key and store.

What you need in Triple Whale

• A Triple Whale account with your Shopify store linked the way you use it day to day (the store hostname in Triple Whale must match what you pass to FinityAi).
• An API key created in Triple Whale with scopes that allow the Summary and Attribution endpoints you plan to use. Their team documents which scopes apply—see Creating and managing API keys.
• Your shop identifier in the form your-brand.myshopify.com—usually the same value shown under Triple Whale Settings → Store. Typos here are a common cause of forbidden errors.

Connect in FinityAi

1. Sign in to FinityAi, open Integrations, and turn Triple Whale on using the card switch. You can return here anytime to turn access off without deleting your saved key.
2. Open Integrations → Triple Whale. You will see a recommended quick connect area when your workspace supports it, and an optional manual API key section—same idea as Notion. If quick connect is not available yet, use the manual path: paste your key and save.
3. Optionally set a default store: either pick from the list Triple Whale returns for your key (when available) or type the hostname. This saves you from repeating the shop on every assistant message.
4. Use Disconnect when you want to remove the key from FinityAi; rotate the key in Triple Whale first if it was exposed.

Assistant: enable tools

Triple Whale actions run only when the assistant is allowed to use tools.

1. Open the Assistant.
2. In the header, open Settings and ensure Connected apps & tools (or equivalent) is on so integrations can invoke tools.
3. Ask in natural language; the assistant will line up your dates and store with what Triple Whale needs. If nothing happens, confirm the Triple Whale card on Integrations is on and your key saved successfully on the Triple Whale settings page.

New to chat settings? See the Assistant user guide.

What the assistant can do

When Tools are on, the assistant can use Triple Whale in three ways. You ask in plain language—you never need to remember internal names or fill in technical fields yourself.

Default store and shop domain

• If you set a default store on the Triple Whale integration page, the assistant can omit the shop in prompts unless you want to override it for one question.
• If you do not set a default, name your shop in the question so Triple Whale knows which store to use.
• The hostname must match Triple Whale's idea of the store—copy it from their UI rather than guessing a public marketing domain.

Sample prompts

Copy and edit dates and shop names to match your store. If a default store is saved, you can often omit the shop.

• →“Validate my Triple Whale connection and show what scopes this key has.”
• →“Pull Triple Whale summary metrics for last week for my store.”
• →“Triple Whale summary for the last 30 days ending yesterday.”
• →“Compare this month vs last month using Triple Whale summary data—same store.”
• →“Summary metrics for yesterday only; use hour 18 for the same-day slot.”
• →“Get attribution orders from January 1 to January 15 this year. Paginate if there are many.”
• →“Export Triple Whale attribution orders for last 7 days with journey data.”
• →“Same date range but exclude journey data—I only need order rows and attribution, smaller payload.”
• →“Page 2 of Triple Whale attribution orders for March 1–10, 50 per page, no journeys.”
• →“What Triple Whale tools are available and what do I need to provide each time?”

Dates, time zones, and ranges

• Phrases like “last week”, “March 1–15”, or “last 30 days” work—the assistant turns them into the right start and end boundaries for Triple Whale.
• Triple Whale interprets periods in line with their API; if a range looks off, state the timezone or use explicit calendar dates in your prompt.
• For summary same-day views, you can mention a specific hour if you need a particular intraday slot (see the sample prompt about “hour 18”).

Payload size and pagination

• Very large responses may be shortened so the assistant stays within safe limits. If you see that, narrow the date range, ask for fewer orders per batch, or say you only need order rows without full journey detail.
• Attribution is paginated. Ask for page 2, page 3, and so on when there are more orders than one page holds.
• Journey arrays can be heavy; prefer excluding them unless you need path-level detail.

Privacy and your API key

• Your key is stored for your account so the hosted assistant can call Triple Whale on your behalf. Treat it like any other secret: revoke and replace in Triple Whale if it leaks.
• FinityAi only retrieves what Triple Whale allows for that key—scopes and store linkage still apply.

If something fails

• 401 / unauthorized — The key is invalid or revoked. Create a new key in Triple Whale, paste it under Integrations → Triple Whale, and try again.
• 403 / forbidden — Often a scope issue or a shop hostname that does not match the store attached to your Triple Whale workspace. Confirm the key has the right access and that the shop string matches Settings → Store.
• Tools never run — Turn on the Triple Whale card on Integrations, enable tools in the assistant settings, and confirm the key is saved (not only typed once).
• Empty or partial data — Check the date range, pagination, and whether journeys should be excluded. Very wide ranges may hit truncation; split the question into smaller periods.

Official Triple Whale docs

Use these for key rotation, scopes, and API behavior outside FinityAi.

• Creating and managing API keysHow to generate a key and choose scopes for Summary and Attribution.
• Triple Whale API referenceOfficial endpoint documentation for summary metrics and attribution data.

← All documentation