Docs / LinkQR
Signup

Dynamic Redirects and Tracking

How dynamic rules, UTM presets, pixels, and scan events work together.

Estimated reading: 2 minutes

Dynamic redirects

Dynamic QR campaigns use a short public URL. When scanned, LinkQR can record analytics, apply tracking metadata, evaluate rules, and redirect the visitor to the final destination.

Rule fields

  • Name: internal rule label.
  • Priority: controls evaluation order.
  • Enabled: active or disabled rule.
  • URL: destination if the rule matches.
  • Countries: comma-separated country targets.
  • Devices: mobile, desktop, or tablet.
  • Hour range: route by time of day.
  • Start and end dates: route during campaign windows.

Tracking data

Scan events can include IP, user agent, referer, source, country/city metadata, browser, OS, device, language, custom domain ID, UTM preset ID, and tracking pixel IDs.

Use cases

  • Send mobile scans to a mobile landing page and desktop scans to a full website.
  • Send specific countries to localized pages.
  • Route a QR to a temporary sale page during campaign dates.
  • Attach UTM presets and pixels to keep paid campaign attribution consistent.

Dynamic Redirects and Tracking - Detailed Feature Guide

Feature Purpose

How dynamic rules, UTM presets, pixels, and scan events work together. This feature is part of the LinkQR workflow and should be documented as an operational tool, not just a menu item.

Main Capabilities

  • Standardizes source, medium, campaign, term, and content labels.
  • Helps compare print, social, email, event, partner, and paid campaigns.
  • Reduces messy reporting caused by manually typed UTM values across QR campaigns, Bio links, and Short URLs.
  • Best created before launching recurring marketing campaigns.

Typical Workflow

  1. Open the Dynamic Redirects and Tracking page from the sidebar.
  2. Review the existing records, settings, or campaign state.
  3. Create or update the required item.
  4. Validate important fields before saving.
  5. Preview or test the public/user-facing result when applicable.
  6. Use analytics, logs, or reports to confirm the feature is working as expected.

Admin Configuration Notes

  • Confirm the feature is enabled in the correct plan.
  • Check workspace ownership when users work inside a team.
  • Review related limits such as credits, storage, QR count, scan count, or team members.
  • Clear cache and test again after changing global settings.

Customer-Facing Benefits

  • Reduces manual work and makes campaign setup faster.
  • Keeps campaign assets organized and easier to maintain.
  • Improves reliability by keeping important setup steps inside one workflow.
  • Supports better reporting and troubleshooting after launch.

Troubleshooting Checklist

  • If the feature is not visible, check plan permission and user role first.
  • If saved data does not appear publicly, verify publish/status settings.
  • If a public URL is involved, test the URL in a private browser session.
  • If team workspaces are involved, confirm the item belongs to the correct owner workspace.
  • If tracking or analytics is involved, confirm the visitor action uses the tracked dynamic URL.