Integrations

Plugs into everything your gyms already run.

Your ad accounts, your email platform, your CRM, your calendar and the billing system at every front desk. No dev work. No new software for your staff. And we follow inbound calls and your business profiles too.

Featured

What each group contributes

Advertising

Your ad accounts are the spend lane. Google Ads and Meta connect to Adsu as live OAuth connections and supply campaign identity, account context, and spend: which campaigns, ad sets, ads and keywords exist and what each one cost over the report period. That spend is the denominator in every cost-per figure Adsu shows, so it comes from the platform, not from a number someone typed in.

The click itself is captured by the Adsu pixel on your landing pages. Keep Google auto-tagging on so the gclid travels with the visit, apply Adsu’s Final URL suffix in Google Ads and its URL parameter template at the ad-set or ad level in Meta, and the campaign, ad group, creative and keyword identifiers arrive with every visit. Campaign IDs are the durable identity; names can change and are not a safe join key, so a renamed campaign keeps its history.

An ad account can be connected without an ingest badge, because its role is identity and spend rather than CRM or payment events, and connection status is not attribution: a campaign can carry spend and still have no attributed payments until there is a tracked visit, a CRM identity and a counted payment match. Once there is, 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. TikTok, LinkedIn, Microsoft, Snapchat, Pinterest, Reddit, X and AppLovin sit in the same group.

Email

Email attribution starts with a link suffix. Append the provider-specific parameters to the links in the email platform you already use, and the Adsu pixel records those values when the recipient lands on your site. That is how a member who joined three weeks after a win-back email is credited to the email rather than filed under direct traffic.

Mailchimp, Drip and Kit go one step further: they can place a recipient token in the clicked URL, and their optional OAuth connection lets Adsu resolve that token to an email identity. The token itself is never treated as a guessed person. HighLevel Email, ActiveCampaign, Constant Contact, MailerLite, Klaviyo, AWeber, beehiiv and Omnisend use provider-specific link instructions; they do not appear as a live ingest connection merely because a suffix was added. HubSpot sits in the same group.

Verifying an email click takes four steps: send a real test email through the provider, click the link in a normal browser with the pixel installed, open Tracking → Sources and confirm the visit is classified as email, and if it is missing, inspect the final landing URL for stripped or renamed parameters. A redirect or link shortener that drops the query string is the usual culprit, and repairing it fixes new traffic rather than reconstructing old visits.

Billing & members

The billing system is Adsu’s revenue authority. It supplies the real transactions, the refunds and the location that received the money, and Adsu does not replace missing payment data with an ad platform’s self-reported purchase value. Stripe connects as a live OAuth connection; Mindbody and WellnessLiving connect with credentials and map site by site to the Adsu location; Square, Zen Planner and Naamly sit in the same group.

PushPress is the identity-enrichment connection: it supplies the member identity behind supported payment flows, so a charge resolves to a person with an email and a phone. Adsu counts a payment only when the payer resolves to an exact email or exact phone match, then credits the last eligible touch inside 30 days. The first counted payment establishes acquisition; later net payments are carried as recurring value for that member rather than counted as new conversions, and refunds and chargebacks reduce the net.

Location is owned by the payment account, never inferred from a campaign name or a landing-page label. That is what makes the per-location scorecard honest for a group: each billing account maps to exactly one Adsu location, and activity at one gym never makes another look healthy. A quiet connection reads Awaiting data until its first payment; Reconnect appears only on concrete evidence that it can no longer authenticate.

CRM

The CRM is the lead lane: the one of Adsu’s three evidence lanes that knows who raised a hand. GoHighLevel connects as a live OAuth connection, authorized through the Adsu marketplace app for the sub-account that owns a location’s contacts and calendars, and supplies contacts, appointments, source fields, and lead identity. It is the only CRM in Adsu’s docs; HighLevel Email is covered under Email.

What flows is the enquiry and the appointment booked, then the show when the appointment is kept. Adsu takes the contact’s email and phone and resolves them against the payment, which is how a lead becomes a member in the scorecard and how cost per appointment and cost per show get computed for each campaign at each location. A newly authorized account reads Awaiting data until the first contact or appointment arrives, then Receiving.

Two setup rules keep it honest. One HighLevel sub-account maps to one Adsu location, and if activity appears under the wrong location the fix is the source-to-location mapping in Adsu, never campaign names or report filters. And when a HighLevel form posts inside an iframe and redirects to a thank-you page, append the contact’s email and phone to the redirect URL so the browser visit and the contact join up.

Website & reports

The browser lane is the Adsu pixel: a small asynchronous script that captures click IDs such as gclid, UTM values, the landing URL, the referrer and supported email-link tokens, then sends beacons to Adsu. Install it in the global page template, or through Google Tag Manager as one Custom HTML tag on an All Pages trigger, so a funnel change never opens a tracking gap. Keep one install, not two.

It belongs on every page that can be the first or last touch in a member journey: paid landing pages and advertorials, embedded or standalone form pages, thank-you and booking-confirmation pages, and the main website when organic, referral, direct and email journeys should appear. Pixel status reads Live once a real, non-bot beacon has arrived in the last 24 hours; bot traffic is kept as a separate signal and never makes the pixel look live.

Google Analytics 4 sits alongside the pixel on the website, and reports can be delivered straight into Slack. Neither adds a stage to the chain; the enquiry, the appointment and the payment come from the CRM and the billing system. What the website lane adds is the click, and without it a payment stays real revenue that cannot be credited to a campaign.