Does Adsu integrate with Stripe, and what flows?

What this connection supplies

Stripe is a payment lane, and the payment source is Adsu’s revenue authority. It supplies the transactions, the refunds and the account that received the money, which is how Adsu knows which location a member belongs to. Adsu never replaces a missing Stripe payment with an ad platform’s self-reported purchase value.

For a gym billing through Stripe that covers the first membership payment, the renewals that follow, and the refunds and chargebacks that reduce net revenue. Adsu reports revenue net of those adjustments, so a cancelled membership does not stay on the campaign’s ledger as a win.

How it connects

Stripe connects as a live OAuth connection: from Connections in Adsu choose Stripe and authorize the Stripe account used by the selected location. In a multi-account group, repeat the connection for every location so each payment account maps to exactly one Adsu location.

• The connection reads Awaiting data until the first successful payment activity, then Receiving. A quiet gym can stay Awaiting with a valid connection.
• Reconnect appears only when Adsu has concrete evidence the authorization no longer works. Reconnect the same intended account rather than a sibling, or revenue lands in the wrong location.
• Stripe supplies the payment. The lead lane (HighLevel) and the browser lane (the Adsu pixel) connect separately, and attribution needs all three.

What Stripe reports on its own, and where it stops

Stripe knows the money: who paid, how much, when, through which account, and what was refunded. That is exactly the record Adsu wants as the revenue authority, and it is why a payment record outranks any ad platform’s purchase number in the scorecard.

What a billing system was never built to know is the ad. A Stripe charge does not carry the click that started the relationship, the campaign or the ad set, the appointment the member booked before they paid, or whether they showed up. Nor does it know the ad spend that produced the member, so cost per member cannot come from billing records alone. Those dimensions live in the ad account, the CRM and the browser, and joining them to the payment is the work Adsu does.

Sources: Connect payment sources · Supported integrations · Attribution method.

What Adsu adds

Adsu resolves each Stripe payment to a person by exact email or exact phone, finds the last eligible visit inside 30 days, and credits the campaign that produced it. The first counted payment establishes acquisition; later net payments are carried as recurring value for that member rather than counted as new conversions. Spend comes from the connected Google Ads and Meta accounts over the same date range, so ROAS compares like with like.

The scorecard reads one line per campaign per location: cost per appointment, cost per show, cost per member and ROAS, each computed only from stages Adsu verified. Membership paid goes back to Google Ads and Meta as a conversion, with appointment booked and appointment showed ahead of it, so the platforms optimize for people who pay. Inbound calls are followed to the member too. If a payment cannot be matched to a person or a visit, it stays real revenue without being credited, and coverage shows the gap.

One plan covers every location and everyone on your team. See pricing.

Set it up

Connect payment sources has the Stripe step. Then Connect GoHighLevel, Connect ad platforms and install the pixel; Revenue is missing is the page to open if a payment you expected is not in a report.

Related