Check whether redirects are losing your advertising click identifiers

Recognize an attribution-path problem

If ads produce confirmed inquiries while imported conversions seem missing, the click path deserves review alongside consent and conversion settings. A redirect may remove useful parameters even though the page looks normal to a customer. Google's Analytics-to-Ads guidance specifically calls for preserving the Google click identifier. Do not jump from a reporting discrepancy to a bid change; first verify whether the configured measurement path can connect the visit to its outcome.

Source checks: Create conversions from Google Analytics events in Google Ads · Destination requirements

List every step to the actual landing page

Collect the final URL, any mobile URL, tracking template, and final URL suffix from the campaign. Then identify site redirects, domain normalization, old service URLs, and third-party booking links. Note whether navigation remains on the expected domain and content. Keep the diagnostic copy free of real customer identifiers. A route that works at the homepage may fail on a particular service page, so test the exact advertised destination.

Run a controlled parameter-preservation test

Use a clearly designated test query parameter to check how the redirect chain treats additional URL values, then use approved tag diagnostics for attribution identifiers. Inspect the destination after each hop with the developer or account manager. Do not invent a live ad click ID or submit test leads as real sales. Record which step removes, rewrites, or preserves the parameter. Test common desktop and mobile paths, including the www and non-www versions actually used.

Repair the redirect with the site owner

Give the developer the specific starting URL, final page, redirect step, and parameter behavior. The correction should preserve required query information without sending customers to unrelated content. Review caching and canonical behavior with the implementation owner; a measurement fix should not create a loop or duplicate destination. Google destination policies also require functional, accurate ad destinations, so do not use cloaking or crawler exceptions to hide an inconsistent path.

Check consent and conversion settings separately

A preserved identifier does not prove every conversion will appear. Consent choices, blocked tags, counting settings, processing delay, and attribution rules can also affect reports. Verify them in a separate checklist so one repaired redirect is not announced as the complete explanation for all missing data. Keep the inquiry system as the record of delivered requests, and distinguish confirmed business outcomes from platform-attributed outcomes in the reconciliation.

Re-test after future URL changes

Document the approved landing route and add a parameter check to website migration and campaign URL updates. After the fix, inspect normal diagnostic traffic and compare reporting with delivered inquiries over a suitable period. Label the implementation date in the report because earlier missing attribution is not necessarily repaired retroactively. The outcome is a reliable current measurement path, not a promise to recover every historical conversion.

Worked example: illustrative figures

For example, the advertised path is /repair-old?test_source=ads-check. It redirects to /repair and loses test_source, while /repair?test_source=ads-check retains it. The developer identifies the old-page redirect as the first parameter-loss step and changes its query handling. A later diagnostic confirms preservation across that path. If 12 delivered inquiries previously had 8 attributed events, the four-event gap should not automatically be assigned to the redirect; consent, scope, and counting also need review. Test traffic is excluded from customer outcome totals.

Questions about this task