Dynamic Destinations
This page explains how to change where a QR code sends users, update UTM parameters, and control availability—without reprinting. Dynamic destinations are a key BaseQR advantage for campaigns that evolve after launch.
What you can change
• Destination URL - Replace the current URL with a new one at any time. The QR graphic does not change.
• UTM parameters - Add or revise UTMs mid-campaign so GA4 reporting stays aligned with your tracking plan.
• Availability - Set a code to Active or Inactive to control whether it accepts new scans during and after promotions.
When to change a destination
• Error correction - Fix a broken or outdated link immediately.
• Offer or content refresh - Point to the latest landing page as creative or messaging evolves.
• Operational shifts - Redirect traffic during inventory changes, phased rollouts, or event timing updates.
• Attribution clean-up - Update UTMs to standardize tagging or add missing campaign metadata.
How to make changes
• Change the destination - Campaigns → View Details → select a code → Edit → update the destination URL → Save.
• Update UTMs - Campaigns → View Details → select a code → Edit → add or adjust UTM parameters (source, medium, campaign, content, term) → Save. Confirm that the final URL reflects your tagging plan.
• Set Active/Inactive - Campaigns → View Details → select a code → Status → choose Active or Inactive. Inactive stops new scans until reactivated.
• Bulk updates - For many codes at once, use CSV import with the Bulk Import Template (link placeholder) to replace destinations and/or UTMs across a set of codes inside a campaign.
Testing changes (recommended)
• Scan from a fresh device - Use a device that hasn’t recently scanned the code, and test on both Wi-Fi and cellular networks.
• Verify the landing page - Confirm correct content, SSL, and mobile rendering.
• Check UTMs - Ensure the URL includes the expected UTM values; validate in GA4 Real-Time to confirm event flow.
• Re-test - If the code is already placed in the real world, test on the actual print/digital artifact to confirm scannability and routing.
Analytics and attribution
• Continuity - Changing destinations or UTMs does not require a new QR; BaseQR continues recording Total Scans for the existing code.
• Attribution - Use UTMs to segment scans in GA4. Align your UTM pattern with campaign naming so BaseQR scan counts and GA4 sessions are easy to compare.
Best practices
• Plan the UTM pattern - Document source/medium/campaign (and optional content/term) before launch so edits remain consistent.
• Document context in the description - Record goals, placements, and audience/regions in the campaign description to guide collaborators.
• Use Inactive to sunset - When a campaign ends, set codes to Inactive (or apply an expiration if applicable) to prevent unintended scans.
Considerations
• Reachability - Destinations should be publicly reachable and performant on typical mobile connections.
• Consistency - Frequent UTM changes can fragment reporting. Favor a stable pattern and only adjust when necessary.zWhat you can change
• Destination URL - Replace the current URL with a new one at any time. The QR graphic does not change.
• UTM parameters - Add or revise UTMs mid-campaign so GA4 reporting stays aligned with your tracking plan.
• Availability - Set a code to Active or Inactive to control whether it accepts new scans during and after promotions.
When to change a destination
• Error correction - Fix a broken or outdated link immediately.
• Offer or content refresh - Point to the latest landing page as creative or messaging evolves.
• Operational shifts - Redirect traffic during inventory changes, phased rollouts, or event timing updates.
• Attribution clean-up - Update UTMs to standardize tagging or add missing campaign metadata.
How to make changes
• Change the destination - Campaigns → View Details → select a code → Edit → update the destination URL → Save.
• Update UTMs - Campaigns → View Details → select a code → Edit → add or adjust UTM parameters (source, medium, campaign, content, term) → Save. Confirm that the final URL reflects your tagging plan.
• Set Active/Inactive - Campaigns → View Details → select a code → Status → choose Active or Inactive. Inactive stops new scans until reactivated.
• Bulk updates - For many codes at once, use CSV import with the Bulk Import Template (link placeholder) to replace destinations and/or UTMs across a set of codes inside a campaign.
Testing changes (recommended)
• Scan from a fresh device - Use a device that hasn’t recently scanned the code, and test on both Wi-Fi and cellular networks.
• Verify the landing page - Confirm correct content, SSL, and mobile rendering.
• Check UTMs - Ensure the URL includes the expected UTM values; validate in GA4 Real-Time to confirm event flow.
• Re-test - If the code is already placed in the real world, test on the actual print/digital artifact to confirm scannability and routing.
Analytics and attribution
• Continuity - Changing destinations or UTMs does not require a new QR; BaseQR continues recording Total Scans for the existing code.
• Attribution - Use UTMs to segment scans in GA4. Align your UTM pattern with campaign naming so BaseQR scan counts and GA4 sessions are easy to compare.
Best practices
• Plan the UTM pattern - Document source/medium/campaign (and optional content/term) before launch so edits remain consistent.
• Document context in the description - Record goals, placements, and audience/regions in the campaign description to guide collaborators.
• Use Inactive to sunset - When a campaign ends, set codes to Inactive (or apply an expiration if applicable) to prevent unintended scans.
Considerations
• Reachability - Destinations should be publicly reachable and performant on typical mobile connections.
• Consistency - Frequent UTM changes can fragment reporting. Favor a stable pattern and only adjust when necessary.