Home
Connectors
BigCommerce - Attentive

Send every BigCommerce event to Attentive, server-side

Q: How do I check that BigCommerce events are reaching Attentive?

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

Q: Can one purchase trigger the same flow twice?

No. One order produces one event, so a single purchase cannot trigger the same flow twice.

Q: How long does it take to connect BigCommerce to Attentive?

Most brands are live in under 20 minutes. Once BigCommerce is connected, every destination receives the same resolved events, Attentive included.

Each event is resolved to a person against a 750M+ device graph before it reaches Attentive, so flows trigger on a known profile rather than an anonymous session.

Request a demo Start free trial

US device IDs in the graph: 750M+
Match rate on events: 90%+
Identity window, per customer: Lifetime
Most brands are live: <20 min

How it flows

How a BigCommerce event reaches Attentive. Captured on the server, resolved to a person, then sent.

01 Capture

Captured from BigCommerce

Server-side capture of BigCommerce storefront and checkout events, resolved and forwarded downstream.

See the BigCommerce integration

BigCommerceWhat it sends

order_idBigCommerce order
email / phonecheckout contact
customer_idBigCommerce customer record
productscatalog items on the order
total_inc_taxorder value

02 Understand

Resolved to one person before it leaves

Every BigCommerce event is matched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer rather than two strangers.

How resolution works

Resolved 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.

Messaging mistakes are expensive and public. These controls exist so a flow never fires against a profile that should not have received it.

03 Activate

Delivered to Attentive

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

See the Attentive integration

AttentiveWhat it receives

phonethe subscriber key
emailsecondary identifier for cross-channel
event propertieswhat the journey triggers on

The catch

Storefront browse events and the hosted checkout are effectively two contexts.

Without resolution the same shopper appears in each as a different person.

Where to check in AttentiveSending you can audit

Attentive the subscriber's timeline

where the event appears against the profile rather than as an unattached activity.

What changes

What changes when BigCommerce feeds Attentive. Two gains on the Attentive side, two on the BigCommerce side.

Attentive

Server-side delivery

Events reach Attentive through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.

Attentive

Identity-resolved events

Events sent to Attentive carry the resolved customer whenever Upstack can identify one, matched against a 750M+ device graph.

BigCommerce

Every event, server-side

Storefront and checkout events are captured from BigCommerce on the server, independent of the browser.

BigCommerce

One setup, every destination

Connect BigCommerce once and forward to every ad platform, email tool and warehouse you run.

Setup

Live in under 20 minutes.

Connect BigCommerce once and every destination, Attentive included, is forwarded the same resolved events.

Upstack dashboardExample

BigCommerce Data source Connected

Attentive Destination Healthy

Read the full Attentive setup guide

01

Connect BigCommerce

Server-side capture of BigCommerce storefront and checkout events, resolved and forwarded downstream.
02

Add the Attentive destination

Under Destinations, add Attentive. Every resolved BigCommerce event is then forwarded to it.
03

Check delivery to Attentive

Trace any event to the profile it resolved to, and see why.