Playbooks
This page provides concise, repeatable procedures for common BaseQR workflows. Each playbook lists the minimal steps and checks to complete the task reliably.
New campaign setup
1. Create campaign — Name using the standard (for example, 2025_q2_eventseries-retail-us-en) and add a description covering goals/KPIs, placements, audience/regions, and UTM plan.
2. Create first code — Add a dynamic QR with the initial destination (HTTPS).
3. Apply UTMs — Add utm_source, utm_medium, utm_campaign (optional utm_content/utm_term).
4. Export asset — SVG for print; PNG/JPG for raster.
5. Verify — Scan on iOS/Android (Wi-Fi and cellular); confirm GA4 Real-Time attribution.
Pre-flight and launch
1. Asset check — Confirm final print proof or digital placement at 100% size; quiet zone intact; strong contrast.
2. Routing — Scan to confirm destination loads quickly over HTTPS; UTMs present and persist through redirects.
3. Acceptance gates — Pass scans in normal and tougher conditions (distance, glare, dim light).
4. Launch — Publish creative; monitor early scans in Campaign Dashboard.
Mid-campaign change (no reprint)
1. Decide change — Destination or UTM correction.
2. Update — Edit the code; keep utm_campaign aligned with the campaign name.
3. Re-test — Quick scan on iOS/Android; confirm GA4 Real-Time.
4. Control — If needed, set code Inactive during change, then Active after verification.
Bulk import at scale
1. Template — Start with the current Bulk Import Template (CSV, UTF-8, single header row).
2. Prepare rows — Include campaign ID, destination URLs (HTTPS), and standardized UTM values.
3. Dry run — Import a small subset; validate results and scans.
4. Full run — Import remaining rows; fix only failed rows and re-import.
5. Spot check — Scan a sample across placements; confirm attribution.
Venue plan for poor signal
1. Low-bandwidth page — Prepare a lightweight destination.
2. Creative aid — Add a short, human-readable fallback URL near the code.
3. Placement — Favor areas with better reception; increase size/contrast on glossy or curved surfaces.
4. On-site test — Scan on cellular under realistic lighting; adjust if retries occur.
5. If congestion spikes — Temporarily redirect via Dynamic Destinations to the lightweight page; restore when conditions improve.
Weekly analytics review
1. Scope — Select the campaign and date range.
2. Trends — Review Total Scans and the time-series chart for peaks/dips.
3. Breakdowns — Check device and location for skews; compare against placements.
4. Attribution — Validate UTM consistency; spot-check GA4.
5. Actions — Record adjustments (size/contrast, placement tweaks, destination changes) and owners.
Post-campaign wrap-up
1. Stabilize — Update destination for evergreen content or set code Inactive.
2. Exports — Export reports (CSV/Excel/PDF) for the full flight window.
3. Retrospective — Compare BaseQR trends with GA4 outcomes; note lessons learned in the campaign description.
4. Archive — Store assets and exports in your shared location.
Migrate from a static QR to BaseQR
1. Assess control — If you control the static code’s server, implement a redirect to the BaseQR destination; otherwise, reprint using a BaseQR code.
2. Create campaign/code — Mirror prior naming and UTM structure where possible.
3. Test and switch — Scan-test; then update the upstream redirect or release the reprinted asset.
4. Monitor — Watch the Campaign Dashboard during the transition window.