Attentive Integration

Last updated: July 18, 2026

Fuego's Attentive integration connects your mobile app to Attentive so your app's shopping behavior flows into Attentive in real time. Send push through Attentive Journeys alongside the push you already send from Fuego, keep subscriber profiles in sync, trigger automations from in app activity, and build segments. Attentive sits under Marketing at fuego.io/integrations, next to Klaviyo, and uses Attentive's React Native SDK (@attentive-mobile/attentive-react-native-sdk).

With this integration, you can:

  • Send push notifications with images and deep links to in app content through Attentive Journeys, running side by side with Fuego's own push

  • Forward app shopping behavior such as product views, add to cart, purchases, searches, and wishlist actions to Attentive in real time

  • Trigger Attentive journeys and messages from what shoppers do in the app

  • Sync subscriber identity (email, phone, Shopify customer ID) from the app to Attentive and keep push opt in status current

  • Build segments from in app behavior, identity attributes, and the Shopify tags Fuego applies (fuego-user, fuego-purchase, fuego-push)

Prerequisites

  • An active Fuego account with a published app on iOS and or Android, on the Enterprise plan

  • An active Attentive account and your Attentive domain, the client specific value Attentive provides for SDK initialization

  • To send push through Attentive: your push sending credentials, an APNs certificate for iOS and an FCM key for Android, handed to Attentive so they can send on your behalf

  • A current app build that includes the Attentive SDK. Fuego ships this in your build, and on Android the module is added at build time

Set up the integration

  1. Get your Attentive domain from Attentive. This is the client specific domain used to initialize the SDK. If you run separate Attentive accounts by region, each has its own domain, so confirm the right one with Attentive support.

  2. Open fuego.io/integrations, go to Marketing, select Attentive, paste your domain, and save to connect.

  3. Ask Fuego to trigger a fresh build so your app ships with the Attentive SDK. On Android the module is added at build time, so a new build is required.

  4. To send push through Attentive, provide your push credentials (APNs certificate for iOS, FCM key for Android) to Attentive through their credential exchange form, then ask your Attentive contact to enable the push channel. New accounts often show only SMS under Create Campaign until push is turned on.

  5. Optional but recommended: ask Fuego for a CSV of your existing push tokens with identity data (email, phone) so Attentive can match them to subscriber profiles.

  6. Open the app, sign in, take a few actions such as viewing a product and adding it to cart, then confirm the events land on your Attentive profile. Test with Attentive support on a test or production account, then approve for production.

You connect Attentive in Fuego with one field, your Attentive domain. There is no API key to paste. Your push credentials go to Attentive, not into the Fuego panel.

Platform support

  • iOS is fully supported. The SDK initializes in app from your configured domain, registers the push token, and handles push opens and foreground notifications.

  • Android is supported on builds that include the native Attentive module, which Fuego injects at build time (plugins/attentive.plugin.js). Builds delivered over the air that predate the module safely skip Attentive calls, so publish a fresh build after connecting.

Capabilities

  • Commerce events use Attentive's ecommerce SDK methods. Every other app action sends as an Attentive custom event.

  • Each event carries common properties: Source set to Mobile App, the app Version, OS, and DeviceID, so you can filter app traffic in Attentive.

  • The integration identifies a visitor by email, Shopify ID, or phone once known, and keeps push opt in status current.

  • Guest sessions keep their anonymous Attentive visitor and creative fatigue state, so signing in does not reset a shopper.

  • Fuego uses an explicit event map with no fall through. An unmapped action is logged internally as UNHANDLED ATTENTIVE EVENT and not sent, so only the events below reach Attentive.

  • Even before events flow, Fuego tags app shoppers in Shopify (fuego-user for app users, fuego-purchase for app buyers, fuego-push for push enabled users) for segmentation.

Events sent to Attentive

Fuego forwards these app actions to Attentive for segments and journeys. You do not configure this list; it ships with the integration. Commerce events use Attentive's ecommerce SDK methods; the rest send as custom events.

In app action

Attentive event

Properties

Product view

recordProductViewEvent (Product View)

Name, ProductID, ImageURL, URL, Brand, Price, CompareAtPrice

Add to cart

recordAddToCartEvent (Add to Cart)

Items: Name, ProductID, ImageURL, URL, Brand, Price, CompareAtPrice, Quantity

Order placed

recordPurchaseEvent (Purchase)

Items: Name, ProductID, ImageURL, URL, Brand, Price, CompareAtPrice, Quantity

App launch

custom Launched App

Common properties only

Screen view

custom Viewed Screen

Screen Name

Collection view

custom Viewed Collection

CollectionID, Name, URL

Begin checkout

custom Started Checkout

Items: Name, ProductID, ImageURL, URL, Brand, Price, CompareAtPrice, Quantity

Remove from cart

custom Removed from Cart

Items: Name, ProductID, ImageURL, URL, Brand, Price, CompareAtPrice, Quantity

Search

custom Searched

Search Term

Add to wishlist

custom Added to Wishlist

Name, ProductID, ImageURL, URL, Brand, Price, CompareAtPrice

Remove from wishlist

custom Removed from Wishlist

Name, ProductID, ImageURL, URL, Brand, Price, CompareAtPrice

Notification tapped

custom Clicked Notification

NotificationID, Title, Body, URL

Apply discount code

custom Applied Discount Code

DiscountCode

Open webpage or external URL

custom Opened Webpage

URL

Submit product review

custom Submitted Product Review

ProductID, Name, Rating, Title, Body

Redeem loyalty points

custom Redeemed Points

RewardID, Name, Details, DiscountCode

Earn loyalty reward

custom Earned Reward

RewardID, Name, Details, URL

Add birthday

custom Added Birthday

Day, Month

Build segments

You can segment app shoppers in Attentive two ways:

  • By the identity attributes Fuego syncs: email address, phone number, Shopify customer ID, and push opt in status

  • By the Shopify customer tags Fuego applies: fuego-user for app users, fuego-purchase for app buyers, and fuego-push for push enabled users

Known limitations

  • Push through Attentive needs the push channel enabled and your APNs certificate and FCM key on file with Attentive. New accounts may show only SMS under Create Campaign until Attentive turns on push.

  • The first push token can take up to 60 minutes to appear in the Attentive UI, then updates run near real time. This is an Attentive platform delay, not a Fuego setting.

  • On Android, only builds that include the native Attentive module send events. Older builds delivered over the air skip Attentive calls, so publish a fresh build.

  • App events are separate from your website and Shopify events. SMS or email journeys built on web events do not fire for app actions unless you add the app events as triggers.

  • The app does not present Attentive SMS or email sign up units. It forwards behavior for shoppers whose email or phone are already known, so use Fuego content or push to capture app users.

  • Attentive is newer than Fuego's Klaviyo integration for push. Brands that only need push have historically used Klaviyo or Fuego's own push, so confirm current push availability with your Fuego contact.

Troubleshooting

  • I only see SMS under Create Campaign in Attentive, where is push? The push channel is not enabled on your Attentive account yet. Confirm your APNs certificate and FCM key are on file with Attentive, then ask your Attentive contact to turn on push. Once enabled, push appears as a campaign channel.

  • My push tokens are not showing in Attentive right after connecting. The first token can take up to 60 minutes to appear in the Attentive UI. After that, updates run near real time. If tokens still do not appear after an hour, contact support@fuego.io.

  • Android app users are not sending events. Confirm the app is running a build that includes the Attentive module. Older builds delivered over the air skip Attentive calls. Publishing a fresh build resolves it.

  • I want an Attentive segment of customers who ordered in the app. Fuego tags those shoppers in Shopify with fuego-purchase (app users get fuego-user, push enabled users get fuego-push). Build the Attentive segment on those tags, or on the synced Shopify customer ID.

  • Which Attentive domain do I enter if I run multiple regions? Each regional Attentive account has its own domain. Confirm the correct one with Attentive support, then enter it in the Attentive panel.

Questions

Questions about the Attentive and Fuego integration? Contact support@fuego.io and we will help you get connected.