Skip to main content
Request a demo
  1. Home
  2. Integrations
  3. Attentive
Upstack Data

Attentive integration: server-side events resolved to a known profile

Feed resolved customer profiles into Attentive so SMS journeys trigger on people, not sessions.

Request a demo Start free trial
Role
Destination
Category
Email & SMS
Pre-built connectors
12 sources
Plans
All plans

What Upstack sends

Every event reaches Attentive attached to a profile. Captured on the server, resolved to a person, then sent.

In: from Shopify1 of 12 sources
  • order_idShopify order and checkout token
  • email / phonecustomer contact from checkout
  • customer_idShopify customer record, if they have one
  • line_itemsproducts, variants and quantities
  • total / subtotal / discountorder economics

Storefront events from the Upstack Pixel, orders directly from Shopify.

Upstack DataResolved before it is sent
  • IdentityMatched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer.
  • customer_typeNew or returning, resolved before send.
  • DeduplicationOne order produces one event, so a single purchase cannot trigger the same flow twice.
  • Bot and fraud filteringAutomated traffic never becomes a profile, so list quality and deliverability are not paying for it.
Out: to AttentiveOn every event
  • phonethe subscriber key
  • emailsecondary identifier for cross-channel
  • event propertieswhat the journey triggers on

SMS journeys triggered on people, not sessions.

See the set-up reference See all 12 sources How resolution works

About Attentive

A subscriber is only reachable if their behavior resolves to them.

Upstack matches events to a known subscriber before they reach Attentive, so journeys trigger on the person rather than skipping the sessions that could not be tied to anyone. Email and phone resolving to one record also means cross-channel journeys act on one human instead of two.

What Attentive is

Attentive is an SMS and multi-channel messaging platform used by DTC brands for subscriber acquisition and conversational retention.

SMS journeys are triggered by behavior, so they depend on that behavior being tied to a known subscriber rather than an anonymous session.

How Attentive works

Attentive is subscriber-first: a visitor opts in through a sign-up unit, and the phone number becomes the key everything else hangs off. Journeys are triggered by events (a browse, an added cart, a purchase) evaluated against that subscriber. Attentive also supports email alongside SMS, which means the same person can be reachable on two channels but only if both identifiers resolve to one subscriber record.

What you can do with it

Three jobs this connector does inside Attentive.

01

Send complete conversions

Conversions reach Attentive through its server-side API with restored click IDs and hashed identifiers attached, so more of what you send is matched on arrival, and the conversions you never saw stop being invisible.

02

Optimize on the customer you want

Map any order attribute to the conversion Attentive receives (profit rather than revenue, new customers rather than repeat buyers, high-value orders rather than every checkout), so the platform learns from the buyers worth acquiring.

03

Journeys triggered on people

Behavioral triggers fire against a resolved subscriber rather than an anonymous session, so the journey reaches the person it was designed for.

Pre-built connectors

12 sources connect to Attentive. Whichever of these you run, Attentive is one switch away.

See all connectors

Documentation

Set-up reference.

Set-up, event schema and field mapping for Attentive as a destination, next to the Attentive developer docs.

FAQ

Attentive integration questions.

What does Upstack send to Attentive?

Feed resolved customer profiles into Attentive so SMS journeys trigger on people, not sessions.

How do I check that events are reaching Attentive?

Open Attentive › the subscriber's timeline, where the event appears against the profile rather than as an unattached activity.

Which plans include the Attentive integration?

All plans. Upstack has three plans that scale with your order volume, and the same integrations are on every plan.

Which sources can send events to Attentive?

12 sources: Shopify, WooCommerce, BigCommerce, Checkout Champ, Recharge, Custom stack, Funnelish, Lasso Commerce, Phoenix Technologies, Skio, Loop Subscriptions and Stripe. Each one has its own pre-built connector.

Will Upstack slow down my store?

Upstack’s own pixel loads asynchronously and fails silently, so it doesn’t hold up your pages. What each destination adds depends on its Tracking Method. The default, Browser + Server, loads that platform’s own tag on your store, in place of the copy you would otherwise install yourself, and also sends the same events from Upstack’s servers. Choose Server for any destination that offers it and its tag never loads, while its events still arrive from Upstack’s servers.

Similar integrations

Other destinations to send to.

See all integrations

Get Attentive tracking right.

A 15-minute walkthrough tailored to your stack and channels.

Request a demo Start free trial