Skip to content
Back to Docs Troubleshooting Quick fixes

Troubleshooting: quick fix checklist

From domain/SSL to redirect rules and analytics — fix common issues before opening a ticket.

Tip: When debugging, record the test URL + time + device + country to match logs quickly.

Quick table of contents
Contact support Read Redirect rules

60-second checklist

Before going deep, run these 6 quick checks:

  1. Open the link in two browsers (Chrome + Safari) and two devices (mobile + desktop).
  2. Check for redirect loops (URL keeps bouncing).
  3. Review rules priority order and fallback URL.
  4. Verify DNS is pointing correctly (A/CNAME) and the domain is verified.
  5. Check SSL (https) status and ensure the landing has no mixed content.
  6. Reconcile tracking using the same timezone and time range.

Link not working / 404

Common causes and fixes:

Check the dashboard: does the link still exist and is the slug correct?

Check DNS records and propagation. If using Cloudflare, confirm proxy (orange cloud) per your setup.

Review rewrite rules and try accessing the underlying route/file to isolate routing issues.

Redirect loop

Loops happen when a rule/fallback points back to the same link or to a URL that redirects back.

  • Don’t use the cloaked link as its own target_url/fallback_url.
  • Landing page scripts that redirect back to the link can cause loops.
  • Check multi-hop redirects (other shorteners) for circular paths.
Fix
  • Set fallback URL to a stable final landing.
  • Temporarily disable geo/time rules to isolate the cause.

Wrong rule match / wrong landing

Usually caused by priority order or unexpected matching behavior.

  • A broad rule is placed above a narrow rule.
  • Country code mismatch (VN vs VI) or device detection differs from expectation.
  • Time windows use a different timezone (server vs local).
Fix
  • Reorder priority: narrow first, broad later.
  • Test with VPN + real devices/user agents.
  • Show timezone clearly in your dashboard.

Tracking mismatch / empty referrer / missing UTM

Differences between your system and Ads/GA4 are common due to environment and counting logic.

App webviews/privacy may not send referrers. Multi-hop redirects can also reduce referrer visibility.

If redirect doesn’t preserve the query string, UTMs can be dropped. Check preserve-query config.

Could be preload, refresh, or bots. Check device/geo/referrer by hour.
Fix
  • Standardize UTM and naming for reconciliation.
  • Compare using the same time range/timezone.
  • Optionally count some events once per session (system-dependent).

Domain not verified

Check in this order:

  1. Correct DNS record type (A/CNAME) and correct host (root vs www).
  2. Propagation: DNS updates may take time.
  3. If using TXT verification, avoid extra whitespace.
  4. If using Cloudflare: confirm the correct zone/account.

SSL not valid / HTTPS issues

SSL depends on DNS + verification + certificate issuance.

Certificate issuance may still be pending or DNS is not pointing correctly. Recheck records and SSL status.

Landing loads http:// assets. Switch assets to https:// or fix references.

If you use www, add www records and ensure host configuration matches.

Ads preview / webview issues

Some platforms use webviews with different behavior than browsers.

  • Previews may cache heavily; test using a real click outside preview.
  • iOS webviews may limit referrer/UA.
  • If you use popups/consent screens, ensure a clear “Continue” UX.

FAQ

Likely device rules or different mobile landing behavior. Re-test device detection and rule order.

Propagation isn’t finished or the record host is wrong (root vs www). Double-check host values.

Send the link URL, test time, device, country/VPN, screenshots, and trace_id if available.

Still stuck?

Send your test details so we can check logs quickly.

Contact support Read Redirect rules