DNS propagation, TLS certificates, platform settings and certification status are separate issues, so diagnose them one at a time. For every problem, write down the date, the exact URL tested, each hop with its status code and Location header, what you expected and what you saw. Share those notes with your tracking provider or Google Ads support when you escalate.
Common problems
The tracking link won't open
Likely causes: DNS not resolving, server down, TLS error, a typo in the URL.
What to check: Run curl -I on the link, do a DNS lookup, try
another network.
Escalate when: the provider's endpoint is down or returns server errors.
The destination parameter is missing or malformed
Likely causes: Wrong parameter name, value dropped by a hop, template typo.
What to check: The raw URL and each hop's Location header.
Escalate when: the tracker rewrites or ignores a correct parameter.
URL encoding is wrong
Likely causes: Nested URL not encoded, or encoded twice.
What to check: Decode the nested value and compare it with the intended URL.
Escalate when: your platform encodes values in a way its own documentation doesn't describe.
Redirect loops
Likely causes: Two rules pointing at each other, such as HTTP/HTTPS or www rules.
What to check: Trace hops until a URL repeats.
Escalate when: the loop sits in the provider's configuration.
The landing page is inaccessible
Likely causes: Server errors, firewall or geo rules, bot blocking that also blocks reviewers.
What to check: Status code, response time, and access from an unfiltered network.
Escalate when: your hosting provider confirms the block.
It works in a browser but fails in an ad test
Likely causes: Timeouts, redirect limits, user-agent blocking.
What to check: Compare headers and timing, and make sure the tracker doesn't block automated checks. Never serve reviewers different content.
Escalate when: the tracker behaves differently for automated requests.
Template variables are set up wrongly
Likely causes: Typos, unsupported placeholders, the wrong field (template versus suffix).
What to check: Compare your setup with the current Google Ads Help.
Escalate when: the documentation and the behaviour disagree.
CNAME changes aren't visible yet
Likely causes: DNS caching (TTL), wrong record target, record added at the wrong host.
What to check: Query the authoritative nameserver and a public resolver.
Escalate when: the record is correct but unchanged after the TTL has passed.
HTTPS certificate errors
Likely causes: Expired certificate, hostname mismatch, missing chain, no certificate issued for your new CNAME.
What to check: Certificate expiry, covered hostnames and chain.
Escalate when: the provider must issue a certificate for your domain.
The destination changes unexpectedly
Likely causes: A rotator or rule in the tracker, a changed platform setting, edits in a shared account.
What to check: Audit tracker rules and change history.
Escalate when: changes appear that nobody on your team made.
Google Ads reports a tracking-related disapproval
Likely causes: One of the problems above, an inconsistent destination, or an unsupported setup.
What to check: Read the stated reason, re-test the whole journey and fix the configuration. Do not try to bypass review or disguise the destination.
Escalate when: the reason stays unclear after your own checks; then contact Google Ads support.
Final launch checklist
Questions people ask
Can this checklist guarantee approval?
No. It is educational only.