Docs / LinkQR

UTM Presets

Standardize campaign source, medium, and campaign tags.

Estimated reading: 2 minutes

UTM Presets

UTM Presets keep attribution consistent across QR campaigns, Bio page links, and Short URLs. Instead of typing UTM values repeatedly, users can apply a saved preset.

Good naming

  • Use campaign names such as summer_sale_2026.
  • Keep source and medium consistent across teams.
  • Create separate presets for print, social, email, events, and partner campaigns.

UTM Presets - Detailed Feature Guide

Feature Purpose

Standardize campaign source, medium, and campaign tags. 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 UTM Presets 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.