Starter+

Retargeting pixels & Conversions API

Connect Meta, Google Analytics 4, and TikTok to fire a server-side pixel event on every QR code scan — no client-side JavaScript, no cookies, and no consent banners required.

How it works

Traditional retargeting pixels work by loading a JavaScript snippet in the visitor's browser. This approach is blocked by ad blockers, iOS Intelligent Tracking Prevention, and requires cookie consent banners in many jurisdictions.

qr-manager.ai fires pixels server-sideusing each platform's server-to-server API (also called Conversions API or Measurement Protocol). When someone scans a QR code:

The scan hits the qr-manager.ai server at qr-m.app/<slug>.
The server looks up which pixels are configured for that QR code.
It fires the configured pixel events server-to-server using the visitor's IP address and user-agent.
The visitor is then redirected to the destination URL — all in under 100 ms.

Note: Because pixel events are fired from our server (not the visitor's browser), they are not affected by ad blockers, cookie preferences, or browser privacy features. No cookie consent banner is required.

Events fired per scan

Meta Conversions API

Starter

You need two values from Meta Events Manager: your Pixel ID and a Conversions API access token.

Find your Pixel ID

Go to Meta Events Manager → select your pixel → the Pixel ID is the number shown under the pixel name (e.g. 123456789012345).

Generate a Conversions API access token

In Events Manager → your pixel → Settings tab → scroll to Conversions API→ click Generate access token. Copy the token — it won't be shown again.

Warning: Store this token securely. It grants the ability to send events to your pixel on your behalf.

Enter values in qr-manager.ai

Go to Settings → Pixels (Starter) or Admin → Org Settings → Pixels (Pro+). Enter the Pixel ID in the Meta Pixel ID field and the token in the Meta Conversions API Token field.

Google Analytics 4 — Measurement Protocol

Starter

GA4 server-side events use the Measurement Protocol. You need your Measurement ID (starts with G-) and an API Secret.

Find your Measurement ID

In Google Analytics → Admin → Data Streams → your web stream. The Measurement ID is shown at the top (e.g. G-XXXXXXXXXX).

Create a Measurement Protocol API Secret

On the same Data Streams page → scroll to Measurement Protocol API secrets → click Create. Give it a nickname and copy the generated secret value.

Enter values in qr-manager.ai

Enter the Measurement ID (starting with G-) in the Google Analytics Measurement ID field, and the API secret in the Google API Secret field.

Note: qr-manager.ai generates a stable daily client ID from a hashed IP address so GA4 can attribute events without storing any personal data or setting cookies.

TikTok Events API

Starter

TikTok server-side events use the Events API. You need your Pixel ID and an Events API access token.

Find your Pixel ID

In TikTok Ads Manager → Tools → Events → Web Events → select your pixel. The Pixel ID is displayed on the pixel detail page.

Generate an Events API access token

On the pixel detail page → Settings → scroll to Generate Access Token. Copy the token.

Enter values in qr-manager.ai

Enter the Pixel ID in the TikTok Pixel ID field and the token in the TikTok Events API Token field.

Where to configure pixels

Pixel settings can be configured at two levels, and optionally overridden per individual QR code.

Where	Plan	Who	Applies to
Settings → Pixels	Starter+	Any member	All your QR codes (account default)
Admin → Org Settings → Pixels	Pro+	Owner / Admin	All QR codes across the whole organisation
QR Code detail → Retargeting Pixels	Starter+	Any member	That QR code only (overrides account default)

Note: API tokens are always stored at the account/org level. Per-QR overrides only apply to Pixel IDs — the Conversions API tokens (which grant write access to your ad accounts) are never stored on individual QR codes.

Pixel resolution hierarchy

When a QR code is scanned, qr-manager.ai resolves which pixel IDs to use in this order:

Per-QR pixel ID — if set on the individual QR code, this is used.
Account / org pixel ID — falls back to the account-level (or org-level for Pro+) setting.
Not fired — if no pixel ID is found at either level, no event is sent for that platform.

The API tokens (CAPI access token, API secret, Events API token) always come from the account or org level — they cannot be set per QR code.

Tip: To stop a specific QR code from firing a pixel that's set at the account level, open the QR code detail, expand Retargeting Pixels, and enter a space in the Pixel ID field, then save. An empty field means "use account default", while clearing it entirely restores fallthrough.

Privacy & compliance

Because qr-manager.ai fires pixels server-side using the visitor's IP address and user-agent (sent in every HTTP request):

No cookies are set on the visitor's device.
No JavaScript is injected into the redirect page.
No personal data is stored by qr-manager.ai — we only persist aggregated geo/device data.
Cookie consent banners are not required for CAPI-only tracking.

Warning: You are responsible for ensuring your use of Conversions APIs complies with Meta's, Google's, and TikTok's terms of service and applicable data protection regulations in your jurisdiction. Consult your legal team if you have questions.

← Back to docs AI integration (MCP) →