Common Issues
This page lists frequent problems, likely causes, and corrective actions. Identify your symptom, apply the steps, then re-test with a quick scan on iOS and Android (Wi-Fi and cellular) and confirm GA4 Real-Time when attribution is relevant.
Scans fail to open or resolve to the wrong page
• Likely causes — Code set to Inactive; incorrect destination URL; HTTP (not HTTPS); downstream redirect removing parameters; transient network conditions.
• Fix — Set status to Active; correct the destination (HTTPS); confirm redirects preserve the full URL; if downstream pages are degraded, use Dynamic Destinations to point to a lightweight interim page, then restore.
UTMs missing or attribution appears incorrect
• Likely causes — UTMs not appended; casing/typos; duplicate tags added by redirect tools; UTMs stripped during redirects.
• Fix — Add or correct UTMs in BaseQR (midstream changes are supported); standardize to lowercase; ensure only one set of UTMs appears in the final URL; verify persistence through all redirects; validate in GA4 Real-Time. See UTM tracking & attribution setup and Campaign Tracking.
Low or inconsistent scan rates
• Likely causes — Code too small for viewing distance; quiet zone blocked; low contrast; glare/curvature; insufficient dwell time.
• Fix — Increase physical size; maintain a clear quiet zone; ensure high contrast; prefer matte materials; relocate to spots with better dwell time; re-test on final media. See Accessibility & Contrast Guidelines and Print vs Digital Placement.
GA4 sessions lower than BaseQR Total Scans
• Expected behavior — BaseQR counts scan events; GA4 counts sessions after page load and may filter traffic.
• Fix — Compare trends and rates, not one-to-one totals; confirm the destination loads quickly on mobile and that UTMs persist; check consent banners and heavy scripts. See Conversion Tracking.
Scans stopped after launch
• Likely causes — Code status toggled to Inactive; destination changed to an unavailable page.
• Fix — Set status to Active; restore a valid destination or route temporarily to a lightweight status page via Dynamic Destinations; re-test.
Slow load or poor connectivity at venue
• Likely causes — Heavy destination pages; congested cellular networks; reflective/glossy substrates causing retries.
• Fix — Point to a low-bandwidth landing page; increase physical size and contrast; add a short, readable fallback URL near the code; consider venue Wi-Fi instructions. See Offline/Poor-Signal Strategies.
Bulk import/create/update errors
• Likely causes — CSV not matching the template; invalid HTTPS URLs; malformed UTMs; incorrect identifiers for updates.
• Fix — Start from the current Bulk Import Template; use CSV (UTF-8) with a single header row; validate URLs/UTMs before upload; correct only failed rows and re-import. See Bulk Creation & Edits.
Exported print asset looks blurry
• Likely causes — Raster asset exported too small; layout tool upscaling; compression artifacts.
• Fix — Export SVG for print; if using PNG/JPG, export at sufficient pixel dimensions (commonly 300 dpi at final size); avoid scaling in layout. See Exporting QR Codes.
Reports show partial or no data
• Likely causes — Date range excludes activity; wrong campaign filter; plan’s analytics visibility window.
• Fix — Adjust date range/filters; remember visibility windows by plan (Starter 14-day, Pro 90-day, Enterprise 1-year); schedule periodic exports for long-term records. See Exporting Reports and Plan Pricing.
Cannot invite teammates / invite fails
• Likely causes — No available seats; attempted invite by non-Admin.
• Fix — Check Account → Billing for seat availability; only Admins can invite; free a seat or upgrade the plan. See Roles & Permissions and Plans & Billing.
API calls failing
• Likely causes — Missing/invalid API key; malformed payload; rate limiting; wrong resource IDs.
• Fix — Verify Authorization header and environment; validate JSON and required fields; implement exponential backoff (and idempotency on creates); list resources to confirm IDs. See Error Codes & Troubleshooting and API quickstart.
Is the service down?
• Action — Check Uptime Status for live incidents and maintenance notes. During downstream issues on your site/app, temporarily route via Dynamic Destinations or set codes Inactive until resolved. See Incident Response & Status Page and SLAs.