Home
Connectors
Recharge - Gorgias

Gorgias

Send every Recharge event to Gorgias, server-side

Q: How do I check that Recharge events are reaching Gorgias?

Open Gorgias › open any ticket. The customer sidebar should show the full order history rather than a single order.

Q: Will a customer be asked twice about one order?

No. One purchase, one request, even when the order is amended.

Q: How long does it take to connect Recharge to Gorgias?

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

Each event is resolved to a person against a 750M+ device graph before it reaches Gorgias, so every touchpoint lands against one customer, not a fragment of one.

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 Recharge event reaches Gorgias. Captured on the server, resolved to a person, then sent.

01 Capture

Captured from Recharge

Bring subscription events into the same resolved customer: new subscriptions, renewals, churn and reactivation.

See the Recharge integration

RechargeWhat it sends

subscription_idthe subscription, not the order
charge_ideach recurring charge
email / phonesubscriber contact
statusactive, cancelled, paused, reactivated
is_first_chargenew subscription versus renewal
product / frequencywhat they subscribed to and how often

02 Understand

Resolved to one person before it leaves

Every Recharge 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 purchase, one request, even when the order is amended.
Bot and fraud filteringFraudulent orders never enter the request queue.

Post-purchase timing is the whole product. These controls exist so requests go to the right person at the right point.

03 Activate

Delivered to Gorgias

Give support the resolved customer: every order and touchpoint attached to one profile.

See the Gorgias integration

GorgiasWhat it receives

email / phonematch the ticket to a customer
order historygive the agent context
external_idone profile, not three

The catch

A subscriber has many charges and one relationship.

Keying post-purchase messaging off charges rather than the subscription means asking the same person for a review every month.

Where to check in GorgiasDelivery you can audit

Gorgias open any ticket

The customer sidebar should show the full order history rather than a single order.

What changes

What changes when Recharge feeds Gorgias. Two gains on the Gorgias side, two on the Recharge side.

Gorgias

Server-side delivery

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

Gorgias

Identity-resolved events

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

Recharge

Subscriptions as their own conversion

Send new subscriptions to the ad platforms as a distinct event, not lumped in with one-time orders.

Recharge

Renewals counted properly

Recurring charges are forwarded as real revenue, so LTV reporting reflects what the customer is actually worth.

Setup

Live in under 20 minutes.

Connect Recharge once and every destination, Gorgias included, is forwarded the same resolved events.

Upstack dashboardExample

Recharge Data source Connected

Gorgias Destination Healthy

Read the full Gorgias setup guide

01

Connect Recharge

Bring subscription events into the same resolved customer: new subscriptions, renewals, churn and reactivation.
02

Add the Gorgias destination

Under Destinations, add Gorgias. Every resolved Recharge event is then forwarded to it.
03

Check delivery to Gorgias

Trace any request back to the order and customer it came from.