Home
Connectors
Custom stack - Sendlane

Send every Custom stack event to Sendlane, server-side

Q: What happens if a contact doesn’t exist in Sendlane?

Upstack only sends events for contacts that already exist in Sendlane. If the visitor’s email isn’t found in your account, the event is skipped, which keeps your account clean and targets only real subscribers.

Q: Which events does Sendlane receive?

ViewContent as product-viewed-upstackified, AddToCart as added-to-cart-upstackified, InitiateCheckout as checkout-started-upstackified and Purchase as order-placed-upstackified.

Q: Which customer parameters are sent to Sendlane?

Upstack looks up each contact in Sendlane by email or Sendlane contact ID, and sends the event only if the contact already exists.

Q: How do I check that Custom stack events are reaching Sendlane?

Trigger a test action on your store, such as adding a product to cart, and check the contact’s activity feed in Sendlane. Events are sent only for contacts that already exist in Sendlane.

Each event is resolved to a person against a 750M+ device graph before it reaches Sendlane, 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 Custom stack event reaches Sendlane. Captured on the server, resolved to a person, then sent.

01 Capture

Captured from Custom stack

Not on the list? Send events to Upstack from any stack over webhook or direct post, with the same schema and the same resolution.

See the Custom stack integration

Custom stackWhat it sends

event_namewhatever you choose to call it
user identifiersany of email, phone, external ID
value / currencyif the event carries revenue
custom propertiesany attribute in your own schema

02 Understand

Resolved to one person before it leaves

Every Custom stack 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 Sendlane

Forward resolved customer events to Sendlane for retention and lifecycle flows.

See the Sendlane integration

SendlaneWhat it receives

email / phonecontact key across email, SMS and reviews
event propertiesautomation triggers
order valueattribution

Which events reach Sendlane

Each Upstack event is mapped to the Sendlane event below before it is sent.

Upstack event	Sent to Sendlane as	Key data on the event
Product view	product-viewed-upstackified	product_id, product_name, product_img_url, variant_id
Add to cart	added-to-cart-upstackified	line_items, subtotal, total, currency
Checkout	checkout-started-upstackified	checkout_id, line_items, subtotal, total, currency
Purchase	order-placed-upstackified	order_id, line_items, total, currency, discounts

Upstack looks up each contact in Sendlane by email or Sendlane contact ID, and sends the event only if the contact already exists.

The catch

Custom schemas tend to carry identifiers in whatever field made sense at the time.

The profile key has to be normalized before it reaches a messaging tool or nothing matches.

Where to check in SendlaneSending you can audit

Sendlane the contact record

where the event should appear against one person rather than creating a second contact.

What changes

What changes when Custom stack feeds Sendlane. Two gains on the Sendlane side, two on the Custom stack side.

Sendlane

Server-side delivery

Upstack sends events to Sendlane from its servers only, so ad blockers and browser privacy settings can’t block delivery.

Sendlane

Identity-resolved events

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

Custom stack

Any stack, any framework

Headless, custom checkout, native app or a platform we haven’t listed: if it can make an HTTP request, it can send to Upstack.

Custom stack

The same event schema

Custom events are resolved, filtered and forwarded exactly like a Shopify order.

Setup

Post directly from your backend so nothing depends on the browser.

You need a Sendlane account where you can generate an API Access Token and create a Custom Integration.

Upstack dashboardExample

Custom stack Data source Connected

Sendlane Destination Healthy

Read the full Sendlane setup guide

01

Connect Custom stack

Not on the list? Send events to Upstack from any stack over webhook or direct post, with the same schema and the same resolution.
02

Add the Sendlane destination

Under Destinations, add Sendlane with two credentials: an API Access Token from Settings, API, and the Integration Token from a new Custom Integration under Integrations in Sendlane.
03

Check the contact’s activity feed

Trigger a test action on your store, such as adding a product to cart, and check the contact’s activity feed in Sendlane. Events are sent only for contacts that already exist in Sendlane.

FAQ

Questions about Custom stack and Sendlane.

What happens if a contact doesn’t exist in Sendlane?

Upstack only sends events for contacts that already exist in Sendlane. If the visitor’s email isn’t found in your account, the event is skipped, which keeps your account clean and targets only real subscribers.

Which events does Sendlane receive?

ViewContent as product-viewed-upstackified, AddToCart as added-to-cart-upstackified, InitiateCheckout as checkout-started-upstackified and Purchase as order-placed-upstackified.

Which customer parameters are sent to Sendlane?

Upstack looks up each contact in Sendlane by email or Sendlane contact ID, and sends the event only if the contact already exists.

How do I check that Custom stack events are reaching Sendlane?

Trigger a test action on your store, such as adding a product to cart, and check the contact’s activity feed in Sendlane. Events are sent only for contacts that already exist in Sendlane.