Fireshift / Guides

Ads signup conversion on app.example.com

By the Fireshift team · Updated 2026-11-16

Short answer

A Google Ads signup conversion has to fire on the host where the signup finishes. If people sign up on app.yoursite.com and your conversion tag lives in the container of www.yoursite.com, it never runs. On 16 Nov 2026 we read the public GTM containers of the 886 study sites with Google Ads conversions. 883 were readable. 36 of them (4.1%) fire a Google Ads conversion only on a product host such as app., signup., auth. or my. 25 of those 36 also set cross-domain linking.

Check this on your own site

Free. Public tags only. Your result opens on the scan page.

Why does the host matter?

A tag only runs on pages that load its container. The visitor reads your ads landing page on www.example.com, clicks "Start free" and creates the account on app.example.com. The page that confirms the account is on the app host. If the Ads conversion tag sits in the marketing site's container and the app host does not load that container, nothing fires when the account exists.

The second problem is the ad click ID. Google Ads stores it in a first-party cookie on the host where the visitor landed. The Conversion Linker passes it to the next host in the URL (Google Tag Manager Help). Without it, the app host may not know which ad click brought the visitor.

How many sites fire on a product host?

We read the public GTM containers of the 886 study sites with Google Ads conversions. 883 had a readable container, 683 of them SaaS. For each Google Ads Conversion Tracking tag we read the firing rules for a Page Hostname or Page URL condition that names a host. Conditions with "does not" were skipped. We did not request any page of any site.

Where Google Ads conversion tags are allowed to fire, 883 sites, public GTM containers read 16 Nov 2026.
What we countedCount
Sites with an Ads conversion rule that names a host252 of 883 (28.5%)
...naming a subdomain of the site96
...naming a product host (app., signup., auth., my., account., login. and similar)36 of 883 (4.1%); 35 of 683 SaaS sites (5.1%)
Product-host sites that also set cross-domain linking25 of 36
All sites with cross-domain linking on in a Conversion Linker386 of 883 (43.7%)

The 36 are the sites where the conversion rule names the app side. 11 of them have no cross-domain linking, so how the click ID reaches the app host is not visible from outside.

One of them counts a click on a buy button whose URL contains the app's pricing path. That is a click on a link to the app, not an account. See login and trial conversions for why the confirmed account is the event to count.

What does the linker do across hosts?

With cross-domain linking on, the Conversion Linker adds the click ID to links that point to the listed domains, so the app host can store it too. The list needs the app host. A linker that lists only the marketing site does nothing for app.example.com if the two hosts do not share a cookie domain. GA4 has its own cross-domain setting for session continuity (Google Analytics Help). Setting one does not set the other. See GA4 key events vs Google Ads conversions.

How do I check both hosts in GTM Preview?

  1. Open GTM, Preview (Preview and debug) and enter your marketing page, with the ad click ID in the URL if you have a test one.
  2. Click your signup button. Tag Assistant should follow the link and keep the same debug session on the app host. If it shows a new session, the app host does not load the same container.
  3. Complete a test signup. On the confirmation page, check that the Google Ads Conversion Tracking tag shows "Fired" on the app host, once.
  4. In DevTools, Network, filter on AW- and your conversion label. You want one request, sent from the app host.
  5. Check the URL after the click: a _gl= parameter means the linker passed the click ID. None means it did not.
  6. Repeat from a clean private window so an old cookie does not hide the gap.

What is the fix?

  • Load the container on the app host. If the product has a separate container, put the conversion tag there. A tag in the wrong container is the usual gap.
  • Fire on the account created, not the signup button click. The click comes before the account exists.
  • Add the app host to the Conversion Linker's cross-domain list and check _gl= in step 5 above.
  • Send a transaction ID, the user ID or account ID, so a reload counts once.
  • Want it done and tested on both hosts? That is part of the Fix Sprint.

Or run the free scan. It lists every Google Ads conversion your public containers send, and the trigger behind each.

What can't we see from outside?

  • Whether it fired. A static read shows where a tag is allowed to fire. It does not show a real signup.
  • Whether the app host loads the same container. We read the marketing site's public container, and the app sits behind a login we do not enter.
  • Primary or secondary. That is set in the Ads account and can't be seen from outside.
  • Tags outside GTM. A gtag call in the app's own code is not in a public container. 3 of the 886 sites had no readable container.
  • The sample: our study sites, built from lists, not random. It leans B2B SaaS.

Published 16 Nov 2026. Data: public GTM containers of the 886 study sites with Google Ads conversions (study scanned 5 Nov 2026), read 16 Nov 2026 by our own script. Product host = a Page Hostname or URL condition naming app., signup., auth., my., account., login., dashboard., admin., portal. or similar on the site's own domain. Method.

FAQ

Where should the Google Ads conversion tag fire if signup happens on app.example.com?

On the host where the account is confirmed. Load your container on the app, fire the tag on the account created event, and pass the click ID across with the Conversion Linker's cross-domain setting.

Does the free Fireshift scan check my app subdomain?

It reads the public GTM containers on your site and lists every Google Ads conversion with its trigger. It does not log in or create an account, so it can't see what runs behind your signup, and it can't see whether an Ads action is primary or secondary.

Run the free scan on your site.

Fireshift reads what your site tells Google Ads, GA4 and Meta from the outside. No install, takes seconds.

See a sample reportOr have us fix it: Fix Sprint, €1,500