How do I install the Adsu pixel through Google Tag Manager?

Create a Custom HTML tag, paste the GTM snippet from your Adsu workspace unmodified, attach an All Pages trigger, preview on a real public page to confirm it fires once, then publish and check Pixel status in Adsu. Remove any theme-level copy of the snippet so it is not installed twice.

Why is the GTM snippet different from the normal one?

Because tag-manager rendering can strip custom data attributes from a script tag. The GTM-safe snippet moves the site key and beacon endpoint into the script URL’s query string so nothing is lost when the container injects it.

Does GTM change which stages Adsu can verify?

No. GTM delivers the pixel; the pixel captures the click, landing page and campaign parameters. Enquiry, appointment and payment come from HighLevel and your billing system. A page the container does not cover is a visit Adsu cannot see, so use a trigger that covers every acquisition and conversion page.

Integrations · Website & reports

Does Adsu integrate with Google Tag Manager, and what flows?

Yes. Google Tag Manager sits in Adsu’s Website & reports group. Its role is pixel deployment — Custom HTML install: the Adsu pixel goes into your container as one Custom HTML tag on an All Pages trigger, and from then on every landing page, form page and thank-you page sends click evidence to Adsu without touching the site’s code.

Updated September 12, 2026

Book a demo

What this connection supplies

GTM does not add a stage to the chain. It is the delivery vehicle for the browser lane: the Adsu pixel, which captures click IDs such as gclid, UTM values, the landing URL, the referrer and supported email-link tokens, then sends beacons to Adsu. Installed through GTM, the pixel loads on every page the container covers, so a funnel change does not create a tracking gap.

The website lane is one of three. The CRM knows who raised a hand, the payment source knows who paid, and the browser lane knows which visit and campaign preceded the lead. GTM is simply the cleanest way to put that third lane on a site your team already manages through a container.

How it connects

Use Adsu’s GTM-safe snippet. It carries the site key and endpoint in the script URL, because tag-manager rendering can strip custom data attributes from a script tag.

01
In Google Tag Manager, create a new Custom HTML tag.
02
Paste the GTM snippet from your Adsu workspace without modifying its query parameters.
03
Attach an All Pages trigger, or an equivalent trigger that covers every acquisition and conversion page.
04
Preview the container, visit a real public page, and confirm the tag fires once.
05
Publish the container and verify Pixel status in Adsu; Live means a real, non-bot beacon arrived within 24 hours.

Do not keep both a theme-level snippet and a GTM snippet on the same page. One global install is enough; duplicate loaders create redundant network work and make page-level coverage harder to debug.

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 appointment, cost per show, cost per member and ROAS, one line per campaign per location. Verified stages go back to Google Ads and Meta as conversions. If the pixel was not on the page a member landed on, that visit is not counted, and coverage shows it.

One plan covers every location and everyone on your team. See pricing.

Set it up

Install with Google Tag Manager has the snippet and the steps; Verify tracking is the check afterwards, and Pixel is not live is where to go if the badge stays Idle.

Questions, answered.

Yes. The Adsu pixel installs through GTM as one Custom HTML tag on an All Pages trigger, using the GTM-safe snippet that carries the site key and endpoint in the script URL. Publish the container, then confirm Pixel status reads Live in Adsu.
Create a Custom HTML tag, paste the GTM snippet from your Adsu workspace unmodified, attach an All Pages trigger, preview on a real public page to confirm it fires once, then publish and check Pixel status in Adsu. Remove any theme-level copy of the snippet so it is not installed twice.
Because tag-manager rendering can strip custom data attributes from a script tag. The GTM-safe snippet moves the site key and beacon endpoint into the script URL’s query string so nothing is lost when the container injects it.
No. GTM delivers the pixel; the pixel captures the click, landing page and campaign parameters. Enquiry, appointment and payment come from HighLevel and your billing system. A page the container does not cover is a visit Adsu cannot see, so use a trigger that covers every acquisition and conversion page.

Google Ads

Google Ads + Adsu: Campaign identity, account context, and spend. How it connects, where its reports stop, what Adsu adds per location.

Meta

Meta + Adsu: Campaign identity, account context, and spend. How it connects, where its reports stop, what Adsu adds per location.

HighLevel

HighLevel + Adsu: Contacts, appointments, source fields, and lead identity. 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

Read the full story

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.