Integrations

This section explains how BaseQR works with your analytics and automation stack. It provides high-level guidance and links to detailed subpages.

What this section covers

• Google Analytics — How to attribute QR-driven traffic in GA4 using UTM parameters on your destination URLs.

• API Keys — How to create and manage API credentials for automation and system-to-system workflows.

Core concepts

• Data flow — BaseQR records scans (Total Scans). Downstream behavior (sessions, engagement, conversions) is measured by your analytics on the destination pages (for example, GA4). UTMs connect these views.

• UTM alignment — A simple, consistent UTM convention ensures GA4 reporting lines up with BaseQR scans by campaign and channel.

• Privacy — BaseQR analytics are anonymous; no PII is collected. GA4 configuration and consent are managed on your site.

How integrations are set up

• Google Analytics — Implement GA4 (optionally via GTM) on the destination pages your QR codes resolve to. Append UTMs to your URLs in BaseQR so GA4 can attribute traffic correctly. No reprinting is required for mid-campaign UTM adjustments.

• API Keys — Create API credentials in Settings to enable programmatic tasks such as creating codes, updating destinations, or exporting data. Store keys securely and rotate when team membership changes.

Best practices

• Document the plan — Add your UTM convention and measurement goals to the campaign description so collaborators tag links consistently.

• Validate end-to-end — After creating a code, scan it and confirm: the destination loads, UTMs are present, and GA4 Real-Time shows the expected source/medium/campaign.

• Secure automation — Limit API key distribution, prefer per-system keys, and revoke credentials that are no longer needed.