How can you validate tracking links without uploading or visiting them?
Inspect supplied URL text, identify its supported format, review required and empty parameters, encoding, duplicates and campaign-name consistency, then inspect unresolved macros separately. TruthPane Link Auditor checks locally. It does not follow redirects, contact destinations, verify accounts or prove attribution after an ad is served.
- What you need: Supplied URLs or a CSV containing a URL column; campaign labels for cross-checking where available.
- What you get: Per-link findings, format and rule coverage, unresolved items and aggregate exports.
- Limits: Opaque short links, provider-side configuration, live destinations, installed-app behavior and macro substitution cannot be verified from offline text alone.
A plausible URL can lack campaign metadata. It can also pass every available text check while depending on an unverified redirect or account setting. Separate these outcomes instead of describing an offline audit as a live tracking test.
Start with the format and intended campaign
Paste URLs into Link Auditor or import a CSV and map its URL column. Supply campaign names for supported parameter comparisons. Rule sets cover recognized AppsFlyer, Adjust and generic UTM patterns; unknown or opaque formats have different evidence boundaries.
Required means required by the selected tool rule, not a universal guarantee about every analytics configuration. Review optional findings against your own reporting needs.
Illustrative example: a synthetic URL
Use https://example.invalid/landing?utm_source=network&utm_medium=cpc&utm_campaign=launch. In generic UTM mode, source, medium and campaign are present. This does not show that the hostname resolves, a redirect preserves fields or the destination consumes them.
| Example change | Inspect | Still unverified |
|---|---|---|
| Remove utm_source | Required-field finding in generic UTM mode | Actual destination attribution |
| Leave utm_campaign empty | Present-but-empty metadata | Approved campaign name |
| Repeat utm_medium | Duplicate-key ambiguity | Downstream choice of value |
| Use a recognized macro | Unresolved dynamic value | Actual serving-time substitution |
| Paste an opaque short link | Provider-side details absent from text | Resolved URL and parameters |
The example domain is deliberately non-production; TruthPane does not visit it. Do not place personal or confidential identifiers in public campaign URLs. Another site’s campaign parameters are distinct from TruthPane’s own coarse analytics metadata.
Review findings in context
- Check protocol and malformed encoding before assuming a URL is interpretable.
- Distinguish missing, empty and duplicate parameters.
- Confirm intended spelling and case; not every variation is wrong.
- Keep macros and opaque links visible as unresolved evidence.
- Compare campaign labels only where format and supplied fields support it.
Connect link checks to launch QA
For whole launch sheets, Preflight checks available names, links, dates, bids, countries and budgets together. Read the pre-launch checklist for coverage and skipped-check interpretation. The Naming Validator checks naming patterns; it does not validate live URLs or provider accounts.
After corrections, rerun and export current findings. Your team still needs separate authorized platform or device tests for redirects, store opening, consent, attribution recording and macro expansion.
Primary reference and review date
Reviewed October 26, 2026: Google Analytics’ campaign URL parameter documentation. This explains external campaign fields. Specific offline findings follow TruthPane’s visible rules; the tool does not connect to your Analytics or ad account.