A visitor finds your pricing page through search, clicks “Start trial,” and signs up on another domain. The signup appears in GA4 under your own website as a referral. Before you use that report to judge search performance, test whether Analytics connected both sides of the trip.
Follow one signup journey in a test browser. Check the tag on both domains, verify that the cross-domain linker survives the handoff, and confirm that the completion event fires once. Each check answers a different question. A working button and a recorded signup can still leave you with broken attribution.
Map the actual path first
Write down the landing page, the destination when you click, any redirects, and the page or action that confirms signup. Use a test environment or an approved test account so you can complete the flow without creating a real lead. Record which domains you control and which belong to a provider. If you can't tag a provider's pages, ask what integration or completion data it offers before assuming you can connect the journey in GA4.
For a fictional example, Northstar's pricing page lives on example.com and account creation lives on example.net. Both are company-controlled. The button first passes through a redirect that strips query parameters. The signup itself works, which is why the marketing team missed the break.
Does the same tag run on both sides?
For Google's standard cross-domain setup, both domains need the same Google tag ID from the same web data stream. In GA4, open that stream's tag settings and check the configured domains. Compare the actual pages with the saved settings, including the signup page itself. If the app uses a subdomain, check the cookie domain and tag coverage before assuming the handoff works. Google's cross-domain measurement instructions cover the requirements and common failure points.
Use a clean browser profile and follow your normal consent flow. Record what you selected. If analytics consent is required, test the permitted flow and document how the site behaves when consent is withheld. Don't change a visitor's consent choices to improve a report.
Where does the linker disappear?
- Start on the real landing page and open your browser's Network panel. Keep the request log across navigations.
- Click the actual signup link. Look for the
_gllinker parameter on the destination URL or in the request chain. Google uses it to pass measurement identifiers between configured domains. - Inspect each redirect. If the first request contains
_gland a later one drops it before the destination can read it, ask the routing owner to preserve it. If it never appears, recheck the domain rules and how the button navigates. Google's troubleshooting guide describes script-driven navigation and other scripts that interrupt click handling.
In Northstar's fictional case, the Network panel shows _gl on the first request and no linker on the final destination. The next test is narrow: preserve the parameter through that redirect and repeat the same journey. The presence of the parameter is evidence about the handoff. You still need to verify the signup event.
Did signup complete once?
Use GA4 DebugView with a permitted test session. Confirm that the expected completion event arrives after signup. A button click can be a useful intermediate event, but the completion check should reflect what actually happened. If refreshing the success page sends the event again, investigate how the event is triggered before treating its count as completed signups.
When processed reports are available, look at the relevant session-source reporting and compare aggregate results with the signup system. Keep timing, consent and measurement coverage in mind. If you're also separating traffic from answer engines, use the GA4 guide to measuring AI referrals to keep assistant visits, tagged events and business outcomes distinct.
Put the failing step, the expected result and a redacted screenshot in the handoff. Remove linker values and account details from anything you share. A developer should be able to reproduce the break without seeing a real customer's session.



