Does Adsu integrate with Google Analytics 4, and what flows?

What this connection supplies

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.

What Adsu adds

With the pixel live, Adsu joins each visit to the enquiry in HighLevel and the payment in your billing system, credits the last eligible touch inside 30 days, and reports cost per member per campaign per location. A visit the pixel did not see is not counted, and coverage shows it. One plan covers every location. See pricing.

Related