Overview
The Fuego integration sends mobile app activity to Triple Whale through the Triple Pixel Mobile SDK. Once you connect and publish it, Mobile App Analytics shows how shoppers browse and engage in your app. Your app activity appears separately from Web Analytics on the Summary page.
Before you begin
Get your Triple Whale Shop ID from your Triple Whale Account Manager. This is the ID Fuego needs to activate the integration. It is not your storefront or myshopify.com domain, and you do not need to look it up yourself.
Warning: Without a valid Shop ID, the Fuego integration stays inactive and sends no events. Entering the ID and publishing the change are both required.
Connect Fuego
Go to Fuego’s integrations page. You can also open the integrations section at
fuego.io/#integrationsFind the Triple Whale Integration card.
Enter the Shop ID provided by your Triple Whale Account Manager.
Click Connect.
Click Publish to make the change live.
Fuego already includes the Triple Pixel Mobile SDK in its app builds. Activating the integration does not require a new app build or an Apple or Google app-store review. You do not need to configure anything else inside Triple Whale. A later SDK update is different: Fuego must release a new app build, which must pass Apple and Google review before that update reaches shoppers.
Check your app activity in Triple Whale
After you publish, open your Summary page and select a date range that includes app activity after activation. Look for Mobile App Analytics, separate from Web Analytics. Events begin flowing when shoppers use the connected app; publishing alone does not create a visit.
What you'll see in Triple Whale today:
Metric | What it means |
Sessions | App visits. A shopper’s activity counts as one visit until they are inactive for 30 minutes. Their next action after that starts a new session. This uses the same 30-minute inactivity approach as GA4 and Shopify, although totals across platforms may differ. |
Users | The total number of unique visitors. |
New Users | Shoppers seen for the first time by Triple Whale’s tracking. This is not a count of app installs. |
New Users % | The share of your app visitors during the selected period who are New Users, as defined above. |
Avg. Session Duration | The average time spent per session. |
Sessions per User | The average number of sessions per unique visitor. |
Bounce Rate | The share of sessions where the shopper viewed only a single screen before leaving. |
Sessions with Add to Cart | The number of sessions in which a shopper added at least one item to their cart. |
Add to Cart % | Sessions with Add to Carts as a percentage of total sessions. |
(Example: TLF Apparel showed 207 sessions, 200 users, 27 new users, 13.50% new user rate, ~3:39 avg session duration, 25% bounce rate, and a 0.94% add-to-cart rate over the observed window. These illustrate the available metrics, not results another store should expect.)
How the integration works
Fuego embeds the Triple Pixel Mobile SDK (@triplewhale/react-native-triple-pixel) in its app builds. The SDK remains inactive until you connect a Shop ID. Once you publish the connection, TriplePixel.init() runs when the app starts and sends the events Fuego has mapped to Triple Whale.
Those mapped events include screen views, product views, add-to-cart activity, the full checkout funnel, and sign-in or identification activity. Checkout-funnel events require both line items and an email address or phone number. Events without that information are not sent as checkout steps.
Only mapped events are sent. App launches, wishlist activity, search, notifications, loyalty activity, and reviews are not tracked through this integration.
How app orders and attribution work
Note: Triple Whale attribution uses Triple Pixel events, not Shopify order tags. Fuego app orders appear with “Fuego mobile app” as their Shopify source, but that source label does not determine Triple Whale attribution.
If you want to filter or label app orders in Shopify, you can optionally use Shopify Flow to tag orders with source 13085343745. This is for your Shopify-side reporting; the tag is not needed for Triple Whale attribution.
The SDK sends mapped app events, including purchase events, into Triple Whale’s pixel-driven attribution. It does not, by itself, reliably identify the same shopper across every ad click, app visit, and checkout. If you need deterministic cross-channel identity, use a measurement partner such as AppsFlyer.
What to expect from app traffic
According to Fuego, a typical mobile app traffic mix is approximately 70% organic app opens, largely driven by push notifications, and 30% campaign- or UTM-driven visits. A UTM parameter is information added to a campaign link to identify its source. App activity without a UTM parameter is still app engagement that the SDK can track; it may not carry the information needed to connect that activity to a campaign.
The integration includes consent management for GDPR consent. Confirm that your store’s consent setup reflects the choices you present to shoppers.
If setup does not finish or events are not flowing
Confirm that you entered the Shop ID supplied by your Triple Whale Account Manager and clicked Publish in Fuego. Then check a Summary date range that includes activity after activation. If you still do not see app events, share the Shop ID with Fuego so they can check the connection.
Do not use Shopify order tags to troubleshoot missing Triple Pixel events. Tags do not activate the SDK or drive Triple Whale attribution. For more about where app activity appears, see Mobile App Analytics in the Web Analytics guide.
Frequently asked questions
Does Triple Whale need to manually set anything up for my store?
No engineering work is required on Triple Whale’s side. Your Triple Whale Account Manager provides your Shop ID, and you connect and publish the integration in Fuego.
Where does my Shop ID come from?
Your Triple Whale Account Manager provides the Shop ID to enter in Fuego. Do not enter your storefront or myshopify.com domain in its place.
How long does it take to go live after I get my Shop ID?
Enter your Shop ID in Fuego, click Connect, then click Publish. Mapped events begin flowing when shoppers use the connected app. Initial activation does not require a new app build or app-store review.
Will mobile app revenue attribute correctly automatically?
Fuego sends mapped purchase events through the Triple Pixel Mobile SDK. Shopify tags are not required for Triple Whale attribution. Whether a purchase can be matched to an earlier ad interaction depends on the available touchpoints and shopper identity information.
Can this reliably connect one shopper from an ad click through checkout?
Not on its own. Matching is best-effort, not deterministic. If you need deterministic cross-channel identity, use a measurement partner such as AppsFlyer.
Does this integration handle GDPR consent?
Yes. The integration includes consent management. Confirm that your store’s consent setup reflects the choices you present to shoppers and your privacy requirements.