Short answer
Open Integrations in the Linkbreakers dashboard, pick Google tag under Retargeting pixels, paste a tag ID and select Connect. With a Google Analytics 4 measurement ID (G-...), every person who scans one of your QR codes or opens one of your links sends a GA4 page_view. With a Google Ads tag (AW-...), they send a Google Ads remarketing hit, so you can show them ads on Search, YouTube and Display.
There is one Google tag field. To use GA4 and Google Ads together, put one here and the other in Google Tag Manager.
The tag adds a short page before the redirect, usually well under a second and never longer than 1.2 seconds. It is available on every plan, Free included.
For reporting in GA4 rather than ad audiences, the Google Analytics 4 integration sends scans, clicks and form submissions from Linkbreakers' servers instead, with no delay for the visitor and with the link, country and device on each event.
Quick summary
- One Google tag ID per workspace, applied to every link and QR code by default, or only to the links you select
G-sends a GA4page_view;AW-sends a Google Ads remarketing hitGT-andDC-IDs are accepted too- The page URL Google records is the Linkbreakers short link address
- Only people fire it: bots, link previews, AI agents and automated browsers are skipped
- Consent for marketing and analytics cookies is the workspace's responsibility
- Also available from the Assistant, the MCP server, the REST API and the CLI
How it works with Google
Once the Google tag is connected, a person's visit goes through a brief page in their browser. That page loads Google's standard gtag.js and runs gtag('config', '<your tag ID>'), then redirects as soon as the script has loaded and had about 300 ms to send. It never waits longer than 1.2 seconds.
What config sends depends on the ID:
G-...(Google Analytics 4): apage_viewevent in your GA4 propertyAW-...(Google Ads): a remarketing hit, which adds the visitor to Google Ads data segments built on that tagGT-...: a Google tag ID, which sends to the destinations linked to it in Google's tag settingsDC-...: a Floodlight tag for Campaign Manager 360
In both GA4 and Google Ads, the page URL is the address of the Linkbreakers link that was opened, such as your short link or your custom domain link.
What you can do in GA4
- See scans and clicks as
page_viewevents on your link domain, in reports or in an exploration filtered on the page location - Build a GA4 audience of people who viewed a page whose URL contains a given short link, and share it with a linked Google Ads account
- Compare scans per campaign by giving each campaign its own short link
GA4 treats the link domain as a different site from your own website. The visit on the link and the visit on your website can therefore count as separate users, and your link domain can show up as a referral on your website's property. If that matters for your reports, add the link domain to the unwanted referrals list of your web data stream, or use a separate GA4 property for links. UTM parameters on your destination URLs keep working as before for the visit on your website.
What you can do in Google Ads
In Google Ads, under the audience or data segment settings, create a website visitors segment based on your Google tag, with a rule that the page URL contains your short link. Use it to target or exclude the people who scanned in Search, YouTube, Display or Performance Max campaigns.
Google needs time to fill the segment, and each network needs a minimum number of active users before ads serve.
Where to find your tag ID
- Google Analytics 4: in Google Analytics, open Admin > Data streams, select your web stream, and copy the Measurement ID, which starts with
G- - Google Ads: in Google Ads, open the Google tag settings (under Tools, in the data or measurement section, depending on your account's menu) and copy the tag ID that starts with
AW-
Linkbreakers checks the shape when you save: G-, AW-, GT- or DC-, then 4 to 20 letters or digits. Any other value is refused with RETARGETING_PIXEL_INVALID, and nothing is changed.
Step-by-step in Linkbreakers
- Open the dashboard and go to Integrations
- Under Retargeting pixels, open Google tag
- Paste your
G-orAW-ID and select Connect - Read the delay notice and the consent note on the page
- Check that the tag fires
To switch to another ID, replace it and select Save. To turn it off, select Remove. When no pixel is left on the workspace, links go back to redirecting instantly.
How to check that it fires
- Open Google Tag Assistant at tagassistant.google.com, or install its Chrome extension
- Connect it to one of your Linkbreakers links and open the link in a normal browser window
- Look for your tag ID and the
page_viewor remarketing hit on the first page, before the redirect
The page redirects within about a second, so Tag Assistant may move on to your destination quickly. Check the event list for the first page rather than the current one. In GA4, the Realtime report shows the page_view within a few minutes.
Ad blockers and some browsers' tracking protection block Google tags. Visitors who use them block them on your links too, as on any website.
The short delay
A tag is JavaScript that runs in the visitor's browser, and a plain redirect runs none. So once a pixel is connected, people's visits go through the brief page described above: usually well under a second, never longer than 1.2 seconds. Workspaces without any pixel keep the instant redirect.
If you also use Advanced data collection, both share the same page, so the visit loads one page, not two.
Who fires the tag
Only visits classified as Human go through the pixel page. Crawlers, link previews (Slack, Teams, Discord, WhatsApp, Facebook, LinkedIn), AI agents and recognized automated browsers get the instant redirect, so they never inflate your GA4 page views or your remarketing segments.
See how Linkbreakers detects AI agents and automated browsers for how visits are classified.
Consent
Google tags set analytics and advertising cookies. In the EU and the UK, that usually needs the visitor's consent first. Linkbreakers does not show a consent banner. Covering the tag in your privacy policy and consent setup is the workspace's responsibility.
Set it up from an AI agent, the API or the CLI
Assistant: in the dashboard, ask "Connect my Google tag G-ABC1234 to all my links".
MCP server: an agent connected to the Linkbreakers MCP server calls retargeting_pixels_update with google_tag_id. Only the fields sent change, so the other pixels keep their value. For example:
Set my Google tag to AW-123456789 on my Linkbreakers workspace and leave the other pixels as they are.
REST API, with a token that has the integrations:write scope:
curl -X PUT https://api.linkbreakers.com/v1/retargeting-pixels \
-H "Authorization: Bearer $LINKBREAKERS_TOKEN" \
-H "Content-Type: application/json" \
-d '{"googleTagId": "G-ABC1234"}'
Send {"googleTagId": ""} to remove it.
CLI, from the next CLI release:
linkbreakers retargeting-pixels update --google-tag-id G-ABC1234
See set up every Linkbreakers integration with an AI agent for the other integrations an agent can configure.
Google tag or Google Analytics 4 integration?
The Google Analytics 4 integration also sends scans to GA4, from Linkbreakers' servers through the Measurement Protocol. It adds no delay, cannot be blocked by ad blockers, and sends leads (generate_lead) and the link, country and device with every event. It does not build Google Ads audiences.
Use the Google tag for Google Ads remarketing, and the integration for GA4 reporting. If both send to the same GA4 property, each visit is counted twice, so point the Google tag at Google Ads (AW-) or at another property.
Limits and caveats
- One Google tag field. For GA4 and Google Ads together, put one here and the other in Google Tag Manager
- Page views only. Linkbreakers sends the
configpage view. It does not send conversions, purchases or leads; the Google Analytics 4 integration sends form submissions asgenerate_lead - All links by default. The tag fires on every link and QR code of the workspace until you choose Selected links under Where it fires and pick links, directories or tags; filter on the page URL in GA4 or Google Ads to split it further
- Separate site in GA4. The link domain is not your website's domain, which affects users, sessions and referrals as described above
- Short delay on people's visits, usually well under a second, never longer than 1.2 seconds
- No consent banner. Consent is the workspace's responsibility
- Blocked like any tag by ad blockers and tracking protection
Frequently asked questions
Should I paste my GA4 ID or my Google Ads ID?
Paste the one you need most. AW- builds Google Ads remarketing segments directly; G- sends GA4 page views, from which you can build GA4 audiences for a linked Google Ads account. For both, use Google Tag Manager for the second one.
Will scans show up in my GA4 reports?
Yes, as page_view events with the Linkbreakers link address as the page location, from people's visits only.
Do I still need UTM parameters?
They do a different job. The Google tag records the visit to the link. UTM parameters on your destination URL tell your website's analytics where the visitor came from after the redirect.
Can I build a Google Ads audience for one QR code?
Yes. Create a website visitors segment with a rule that the page URL contains that QR code's short link.
Why was my tag ID refused?
The ID must start with G-, AW-, GT- or DC-, followed by 4 to 20 letters or digits. A Universal Analytics UA- ID or a GTM- container ID is refused here; put a GTM- ID in the Google Tag Manager field.
Sources
- Linkbreakers Google tag page, API and MCP tool, checked in the product on 2026-10-30.
- Retargeting pixels overview
- How to retarget people who scanned your QR code with ads
- Google tag platform, set up the Google tag with gtag.js: https://developers.google.com/tag-platform/gtagjs
- Google Analytics, measure pageviews: https://developers.google.com/analytics/devguides/collection/ga4/views
- Google Analytics Help, find your Google tag ID: https://support.google.com/analytics/answer/9539598
- Google Analytics Help, create, edit and archive audiences: https://support.google.com/analytics/answer/9267572
- Google Analytics Help, get started with Explorations: https://support.google.com/analytics/answer/7579450
- Google Ads Help, about your data segments: https://support.google.com/google-ads/answer/2453998
- Google Ads Help, tag your website using Google Ads: https://support.google.com/google-ads/answer/2476688
- Tag Assistant Help, troubleshoot with Tag Assistant: https://support.google.com/tagassistant/answer/10039345
Last reviewed
2026-10-30 by Laurent Schaffner.
About the Author

Laurent Schaffner
Laurent founded Linkbreakers and builds it, from the API behind every scan to the app and the developer tools. A software engineer with more than 15 years in SaaS, most of them on back-end architecture.
Related Articles
Retargeting pixels: Meta, Google, TikTok, LinkedIn and Google Tag Manager
Add a Meta Pixel, Google tag, TikTok Pixel, LinkedIn Insight Tag or Google Tag Manager container to every link and QR code of your workspace, or only to the links you select. Where to find each ID, why pixels add a short delay, who fires them, consent, and how to set them up from an AI agent, the API, the CLI or the SDKs.
How to retarget people who scanned your QR code with ads
Turn the people who scanned the QR code on your packaging, poster, booth or event signage into a Meta, Google, TikTok or LinkedIn audience, and show them ads afterwards. The flow, which pixel for which audience, examples and limits.
Google Tag Manager for QR codes and links
Connect a Google Tag Manager container to Linkbreakers so every person who scans your QR codes or opens your links fires the tags you choose, including Pinterest, Snap, Reddit, X and Microsoft Ads. Triggers that work, where to find the container ID, Preview mode, consent and limits.
On this page
Need more help?
Can't find what you're looking for? Get in touch with our support team.
Contact Support