Does Adsu integrate with Meta, and what flows?
Yes. Meta Ads connects to Adsu as a live OAuth connection: authorize the Meta identity with access to the intended ad account. It contributes campaign identity, account context, and spend, the click and the spend end of the chain, and receives appointment booked, appointment showed and membership paid back as the conversions Meta optimizes for.
Updated
What this connection supplies
Meta is the spend lane for Facebook and Instagram. It tells Adsu which campaigns, ad sets and ads exist and what they cost over the report period, the denominator in cost per appointment, cost per show and cost per member. The click reaches Adsu through the pixel: Adsu’s URL parameter template, added at the ad-set or ad level, preserves readable campaign fields alongside the durable platform IDs, so a renamed ad set keeps its history.
Meta’s report and Google’s are added up separately by their owners. Adsu counts each member once, against the last eligible touch inside 30 days, so the two accounts stop claiming the same person.
How it connects
Meta Ads connects as a live OAuth connection. From Connections in Adsu, authorize the Meta identity with access to the intended ad account and select it. If the token expires or Meta revokes access, Adsu reports Expired or Reconnect instead of silently carrying the last good state forward; an expired Meta grant outranks Awaiting data.
- Add Adsu’s URL parameter template at the ad-set or ad level, then visit a tagged landing page and check Tracking → Sources for the visit.
- Use campaign IDs as the durable identity; names can change.
- Compare spend and attributed revenue over the same date range before reading ROAS.
What Meta reports on its own, and where it stops
Meta reports what it saw: reach, clicks, cost and the events you send it, and it optimizes toward those events. Feed it leads and it finds more leads. In this site’s words, Meta counts the leads Meta thinks it produced.
What it cannot see is the front desk: whether the lead booked, showed, paid, renewed, or which location took the payment. A browser pixel event captures what happened in the browser, not the membership that cleared weeks later. Sending Meta a verified paid-member event is the difference between an audience that looks like your leads and one that looks like your members.
Sources: Connect ad platforms · Tag ad URLs · Attribution method.
What Adsu adds
Adsu joins the Meta click to the enquiry in HighLevel and the payment in your billing system, resolves the member by exact email or exact phone, and credits the last eligible touch inside 30 days. Spend from Meta and net revenue from the payment source meet in one scorecard: cost per appointment, cost per show, cost per member and ROAS, one line per campaign per location, each computed only from stages Adsu verified.
Appointment booked, appointment showed and membership paid go back to Meta as the conversions to optimize for, so its targeting goes looking for more people like the ones who booked and paid. Inbound calls are followed to the member as well as clicks. If a stage cannot be verified, it is not counted and not sent; coverage shows the remainder.
One plan covers every location and everyone on your team. See pricing.
Set it up
Connect ad platforms has the Meta authorization; Tag ad URLs has the URL parameter template; Reconnect an integration covers an expired Meta grant.
Questions, answered.
Yes. Meta Ads is a live OAuth connection. It supplies campaign identity, account context and spend; the click arrives through the Adsu pixel from your tagged ad URLs; and Adsu sends appointment booked, appointment showed and membership paid back to Meta as conversions.
Adsu does. It verifies the membership payment against your billing system and the member against your CRM, then sends membership paid, with appointment booked and appointment showed ahead of it, back to Meta and Google Ads as the conversions to optimize for, one location at a time.
Yes. Meta supplies campaign identity and spend, the Adsu pixel captures the click from your tagged ad, HighLevel supplies the contact, and Stripe supplies the payment. Adsu matches the payer to the contact by exact email or phone, credits the last eligible touch inside 30 days, and sends membership paid back to Meta.
It changes what Meta is told to find. Today it is told a form fill is the win. Adsu tells it which leads booked, showed and paid, verified against your CRM and billing records, so Meta optimizes for members. You also see cost per show and cost per member per campaign, so the campaigns producing no-shows are visible.
Adsu reports Expired or Reconnect rather than carrying the last good state forward. Open the Meta connection in Adsu and reauthorize the same ad account; spend for the gap is not invented. Payments and CRM activity keep flowing because they arrive on their own lanes.
Related
Google Ads + Adsu: Campaign identity, account context, and spend. How it connects, where its reports stop, what Adsu adds per location.
HighLevelHighLevel + Adsu: Contacts, appointments, source fields, and lead identity. How it connects, where its reports stop, what Adsu adds per location.
StripeStripe + Adsu: Real transactions, refunds, and the revenue-bearing location. How it connects, where its reports stop, what Adsu adds per location.
The proof
- Net members
- +21
- Lifetime value added
- $67,000+
Bobby & Maria Gasdia, Big Day Fitness, 2 locations
Stop paying for leads. Start paying for members.
Early access is opening in small groups. Applying takes two minutes, and we’ll tell you straight whether your stack is ready to connect.