Connect QR Scans to Your Marketing Tags
Add a Meta Pixel ID, Google Tag Manager container, GA4 measurement ID, or any combination to an eligible dynamic QR. QRLynx loads the configured browser tags during a brief redirect, then sends the scanner to the destination.
Selected QR Code Type
What QRLynx Retargeting Pixels Do
QRLynx Retargeting Pixels add browser-based marketing tags to the redirect step of an eligible dynamic QR code. Enterprise teams can save a Meta Pixel ID, a Google Tag Manager container ID, and a Google Analytics 4 measurement ID on each QR. When a qualifying human browser scans the code, QRLynx loads the configured tags on a short noindex page and then continues to the saved destination.
The tags measure the redirect-page visit. They do not install code on the destination website, identify a person inside QRLynx, create an advertising campaign, or guarantee that an advertising platform will add the scanner to an audience. Audience eligibility, attribution, consent behavior, ad blockers, and reporting remain controlled by the configured platform and campaign setup.
Choose the Right Tag for the QR Campaign
Each field has a different role, and all three can be saved on the same eligible QR.
| QRLynx field | Use it for | What QRLynx loads |
|---|---|---|
| Meta Pixel | A browser PageView that can contribute to Meta measurement or audience workflows | The base Meta Pixel with the saved numeric Pixel ID |
| Google Tag Manager | A container whose published tags and consent settings you manage in GTM | The saved GTM container ID |
| Google Analytics 4 | A GA4 page-view signal for the short redirect page | The Google tag with the saved GA4 measurement ID |
How to Add Retargeting Pixels to a QRLynx QR Code
Configure the marketing platform first, then connect its identifier to a saved QR.
Prepare the platform identifier
Create or select the Meta Pixel, GTM web container, or GA4 web data stream that should receive the redirect-page signal. Copy only the identifier shown by that platform.
Create or open an eligible dynamic QR
Use the QRLynx generator or open a saved dynamic QR from your account. Retargeting Pixels require the Enterprise plan and are not supported on GS1 Digital Link QR codes.
Open Retargeting Pixels
From the QR edit page, open the Retargeting control. Enter a 10 to 20 digit Meta Pixel ID, a GTM container in GTM-XXXXX format, or a GA4 measurement ID in G-XXXXXXXX format.
Set consent behavior for the campaign
Review the laws, platform terms, and audience expectations that apply to the campaign. When an access gate is appropriate, configure QRLynx Access Consent on the same QR so the gate is completed before the tag handoff.
Save and review the Retargeting dashboard
Save the QR, then use the Retargeting Pixels page to find configured codes and review which Meta, GTM, and GA4 identifiers are attached to each one.
Run a real browser test
Scan the final QR with a normal mobile browser and use the platform's testing or debugging tools to confirm the expected signal. Programmatic clients and likely automation bypass the browser-pixel page.
What Happens During a Qualifying Scan
The measurement handoff sits between QRLynx access checks and the destination.
Access checks run first
Password, consent, and lead-form gates are resolved before QRLynx counts the successful human scan or loads configured tags.
QRLynx records the scan
A qualifying human GET follows the normal QRLynx scan-analytics path before the marketing-tag response is returned.
Configured tags load
The noindex redirect page loads the saved Meta Pixel, GTM container, GA4 tag, or their supported combination.
The destination opens
The browser continues to the selected destination after the short handoff. The printed QR and saved destination remain editable as a dynamic QR.
Campaigns Where a Scan Signal Adds Context
Use one QR per meaningful placement when the campaign needs placement-level measurement.
Direct mail
Attach a campaign-specific tag setup to a QR printed on a postcard or catalog, then compare the platform signal with QRLynx scan analytics.
Product packaging
Measure visits that begin on a package QR before the customer reaches instructions, registration, or a product page.
Events and booths
Use separate QRs for a booth, handout, or session so each placement can carry its own saved tag identifiers.
Print promotions
Connect a poster or flyer scan to the browser measurement tools already used by the campaign team.
Consent, Testing, and Reporting Boundaries
Retargeting tags can transmit browser and device information to third-party platforms. The QR owner remains responsible for the campaign's notices, lawful basis, consent configuration, platform terms, audience rules, retention choices, and advertising settings. Google documents that consent mode works with a consent banner rather than replacing one. QRLynx Access Consent can provide a QR access gate, while the behavior of tags inside GTM remains controlled by the published container.
Browser-based tags can also be affected by ad blockers, browser restrictions, network timing, and platform processing. Use Meta Events Manager, Google Tag Assistant, or GA4 debugging tools to verify the configured signal. Compare those results with QRLynx scan analytics, but do not expect the systems to report identical numbers because they apply different client, consent, and filtering rules.
Prepare the campaign QR
Create the dynamic QR before connecting its tags
Set the destination and design, save the QR, then add the campaign's Meta, GTM, or GA4 identifier from the edit page.
Retargeting Pixel QR Code Questions
Which retargeting and analytics tags does QRLynx support directly?
QRLynx has direct fields for Meta Pixel, Google Tag Manager, and Google Analytics 4. It does not have direct LinkedIn, TikTok, Snapchat, Pinterest, or arbitrary script fields. A GTM container can run the tags you publish inside that container, subject to the container's own configuration and platform support.
Which QRLynx plan includes Retargeting Pixels?
Retargeting Pixels are included with Enterprise. Business and lower plans can use QRLynx scan analytics, but saving Meta, GTM, or GA4 identifiers on a QR requires Enterprise access.
Can one QR code use Meta Pixel, GTM, and GA4 together?
Yes. An eligible Enterprise dynamic QR can store one Meta Pixel ID, one GTM container ID, and one GA4 measurement ID at the same time. You can also configure only the field or fields the campaign needs.
Where do the tags load?
They load on a short QRLynx redirect page before the browser continues to the QR destination. QRLynx does not inject these tags into the destination website, and the redirect page is marked noindex.
Does QRLynx send server-side conversion events?
No. The current Retargeting Pixels feature is browser-based. It does not send Meta Conversions API events, perform identity matching, or provide server-side GTM. Programmatic clients and likely automation bypass the browser tag page.
Does every scan become a retargeting audience member?
No. QRLynx loads the configured browser tag for a qualifying scan, but the external platform decides whether the event is received, attributed, eligible, retained, or usable for an audience. Consent choices, browser restrictions, ad blockers, account configuration, and platform rules can all affect the result.
Can I require consent before the marketing tags load?
QRLynx processes an enabled Access Consent gate before the retargeting handoff. The QR owner must still choose wording and configuration appropriate for the campaign and ensure the connected platforms and GTM tags honor the required consent state.
How do I verify a retargeting QR setup?
Scan the final QR in a normal mobile browser, then use the connected platform's event-testing or debugging tools. Meta Events Manager, Google Tag Assistant, and GA4 debugging tools are the appropriate places to confirm their respective signals. Also verify that the intended destination opens.
Can I change or remove the tags later?
Yes. Open the saved QR, return to Retargeting Pixels, change an identifier or disable the configured fields, and save. QRLynx refreshes the QR's redirect data, so the printed QR does not need to change.