Does Adsu integrate with X Ads, and what flows?

What this connection supplies

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.

What Adsu adds

Adsu joins the click to the enquiry in HighLevel and the payment in your billing system, resolves the member by exact email or exact phone, and reports cost per appointment, cost per show, cost per member and ROAS, one line per campaign per location, computed only from stages it verified. Verified stages go back to Google Ads and Meta as conversions. One plan covers every location. See pricing.

Related