When clicks are missing
Open the exact live tracking link in a clean browser and confirm the destination, status, parameters, and redirect sequence. Check whether the campaign uses the intended link, whether a custom tracking domain resolves, and whether ad-platform or email tools rewrite the URL. Compare a controlled click timestamp with the report rather than relying on aggregate totals.
If the destination works but the click is absent, document browser, device, consent state, blockers, and network conditions. Avoid changing the domain, link, and reporting filter simultaneously.
- Test the published link, not a draft copy.
- Capture the redirect chain and timestamp.
When clicks appear but conversions do not
Trace the path from landing page to the conversion trigger. Verify the correct event method, domain, script or integration, identifier continuity, value, and the page or server action that confirms completion. Test a successful and unsuccessful transaction so the distinction is visible.
For a third-party or merchant checkout, confirm what data can legally and technically return. An unavailable merchant signal is a measurement boundary, not a tag defect. Use merchant or network reporting as the outcome record when direct capture is impossible.
- Find the first handoff where identity disappears.
- Do not infer a sale from an outbound click.
When conversions duplicate or values look wrong
Repeat one conversion while watching refreshes, redirects, thank-you page loads, retries, webhook deliveries, and imports. Confirm that a stable order or event identifier prevents duplicate credit where the integration supports it. Check numeric formatting, decimal units, currency, taxes, refunds, and whether the report shows revenue or commission.
Quarantine obviously bad data before changing campaign budgets. Preserve the raw record and note the correction so later reports do not hide when or why the measurement changed.
- Test refresh and retry behavior.
- Verify value units and currency.
- Annotate corrections.
When platforms disagree
Align date range, time zone, attribution window, event definition, consent state, and conversion status before comparing totals. GA4 may use modeled key events and its own attribution rules; an ad platform may self-attribute; a merchant may approve or reverse sales later. Exact equality is not a realistic universal standard.
Set a tolerance based on the decision. Investigate abrupt or directional divergence, not every harmless count difference. Keep a discrepancy log with cause, impact, owner, and whether the issue changes a spending decision.
- Normalize definitions before totals.
- Escalate unexplained changes that affect decisions.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- ClickMagick product capabilities — MERCHANT · checked 2026-08-22
- Google Analytics cross-domain measurement — PLATFORM · checked 2026-08-22
- Google Analytics modeled key events — PLATFORM · checked 2026-08-22