A complete Adsu setup has three independent evidence lanes: the CRM knows who raised a hand, the payment source knows who paid, and browser tracking knows which visit and campaign preceded the lead. Complete all three before judging report coverage.
1. Choose the location
Adsu is always scoped to one location in the product. Use the location switcher before connecting location-specific systems. In these docs, a signed-in user can inspect another authorized location without changing the product’s active location.
2. Connect the systems
- 01
Connect GoHighLevel
Authorize the correct HighLevel location so Adsu can receive contacts and appointments.
Open GoHighLevel setup - 02
Connect a payment source
Connect Stripe, Mindbody, or WellnessLiving for this Adsu location. Connect every location separately where the provider account is location-specific.
Open connections - 03
Connect ad accounts
Authorize Google Ads and Meta Ads, then select the account that owns this location’s campaigns.
Open ad connections
3. Install and tag
Place the snippet once in the global site template or tag manager so it loads on landing pages, form pages, and thank-you pages. Then add Adsu’s Google Final URL suffix and Meta URL parameters.
4. Verify the evidence
- Pixel status becomes Live after a real, non-bot browser beacon arrives.
- GoHighLevel moves from Awaiting data to Receiving after contacts or appointments arrive.
- Payment sources move to Receiving after their first successful data activity; a quiet gym can remain Awaiting even when authorization is valid.
- Ad accounts can be connected without an ingest badge because their role is campaign identity and spend, not CRM or payment events.