Does Adsu integrate with Square, and what flows?

What this connection supplies

Square is where the card gets tapped. In Adsu the billing system is the revenue authority: it supplies the transactions, the refunds and the location that received the money, and Adsu does not replace a missing payment with an ad platform’s self-reported purchase value. For a Square gym that is the first membership payment, the renewals after it, and the refunds that reduce net revenue.

Because the payment account determines the Adsu location, a group with a Square account per gym gets one scorecard per gym. Nobody reads campaign names or landing-page labels to guess where a member joined; the money says where.

How it connects

Billing systems connect inside Adsu, under Connections, and map to one Adsu location each; connect every location separately where the account is location-specific. A connection reads Awaiting data until the first successful payment activity, then Receiving, and Reconnect appears only on concrete evidence that the connection cannot authenticate or ingest. Setup is done for you: tell us what runs your front desk when you book a demo.

Square supplies the payment. HighLevel supplies the enquiry and the appointment, and the Adsu pixel on your landing, form and thank-you pages supplies the click. Attribution needs all three, and a payment with no matching contact or visit stays real revenue that is not credited to any campaign.

What Square reports on its own, and where it stops

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

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

Sources: Connect payment sources · Attribution method · Confidence and coverage.

What Adsu adds

Adsu resolves each 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. 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. Appointment booked, appointment showed and membership paid go back to Google Ads and Meta as the conversions to optimize for, so the platforms learn who pays. Inbound calls are followed to the member too. If a stage cannot be verified it is not counted, and coverage shows the remainder.

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

Related