--- title: "Retargeting pixels: Meta, Google, TikTok, LinkedIn and Google Tag Manager" description: "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. 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." canonical: "https://linkbreakers.com/help/article/retargeting-pixels-meta-google-tiktok-linkedin-and-google-tag-manager" last-updated: 2026-10-30 --- # 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. 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. :::try-ai-prompt {"prompt":"Add my Meta pixel 123456789012345 and my Google tag G-ABC1234 to all my links","description":"Set up retargeting pixels with the Assistant.","target":"assistant"}::: ## Short answer Open **Integrations > Retargeting pixels** in the dashboard, paste the ID of each pixel you use and save. From then on, every person who opens one of your links or scans one of your QR codes fires those pixels, and the ad platforms add them to your audiences so you can show them ads later. Five pixels are supported: **Meta Pixel**, **Google tag** (Google Analytics 4 or Google Ads), **TikTok Pixel**, **LinkedIn Insight Tag** and **Google Tag Manager**, which covers any other platform you put in your container. Pixels add a short delay to every visit. A pixel has to run in the visitor's browser, so a brief page loads before the redirect. It is usually well under a second and never longer than 1.2 seconds. Without pixels, links redirect instantly. Retargeting pixels are available on every plan, Free included. ## Quick summary - One page, five ID fields: Meta, Google tag, TikTok, LinkedIn, Google Tag Manager - Pixels apply to every link and QR code of the workspace; there is no per-link choice yet - An empty field removes that pixel; a malformed ID is refused - Each pixel sends a page view for the visit - Only people fire pixels: bots, link previews, AI agents and automated browsers get the instant redirect - A short page before the redirect, usually well under a second, at most 1.2 seconds - Consent for marketing cookies is the workspace's responsibility - Everything works without the dashboard: MCP tools, REST API, CLI, SDKs and the Assistant ## The five pixels | Pixel | Field | Format | What it feeds | |---|---|---|---| | Meta Pixel | Pixel ID | Digits only, such as `123456789012345` | Facebook and Instagram audiences | | Google tag | Tag ID | `G-...` (Google Analytics 4 measurement ID) or `AW-...` (Google Ads tag) | Google Ads remarketing audiences and GA4 page views | | TikTok Pixel | Pixel ID | Letters and digits, such as `C4ABCDEFGHIJKLMNOPQR` | TikTok audiences | | LinkedIn Insight Tag | Partner ID | Digits only | LinkedIn audiences | | Google Tag Manager | Container ID | `GTM-...` | Whatever the container holds | Google Tag Manager fires the tags you set up in your container, so it is the way to reach platforms that have no field of their own, such as Pinterest, Snap, Reddit, X or Microsoft Ads. ## Step-by-step 1. Open the Linkbreakers dashboard and go to **Integrations** 2. Choose **Retargeting pixels** 3. Paste the ID of each pixel you use. Leave the others empty 4. Read the delay notice on the page, then save 5. [Check that the pixels fire](#how-to-check-that-it-works) To change a pixel, replace its ID and save. To remove one, empty its field and save. When every field is empty, links go back to redirecting instantly. Each ID is checked for the right shape when you save. An ID that does not match, for example a Meta Pixel ID with letters in it or a Google tag that does not start with `G-` or `AW-`, is refused with the error `RETARGETING_PIXEL_INVALID`, and nothing is changed. ## Where to find each ID Ad platforms rename their menus from time to time. If a path below has moved, search the platform's help for the name of the ID. ### Meta Pixel ID In **Meta Events Manager**, select your pixel (also called a dataset) under data sources. The Pixel ID is the number shown with it. Copy the digits only. ### Google tag: G- or AW- - **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 **Tools**, then **Audience manager** or the **Google tag** settings, and copy the tag ID, which starts with `AW-` Paste one of the two. If you need both GA4 and Google Ads, use one here and add the other through Google Tag Manager. ### TikTok pixel ID In **TikTok Ads Manager**, open **Assets > Events**, then your web events. The pixel ID is shown next to the pixel's name. ### LinkedIn partner ID In **LinkedIn Campaign Manager**, open **Data > Insight Tag**. The partner ID is the number shown in the tag setup. ### Google Tag Manager container ID In **Google Tag Manager**, open your container. The container ID, starting with `GTM-`, is in the workspace header at the top. Publish the container in Google Tag Manager so the tags inside it are live. ## How it works A retargeting pixel is a piece of JavaScript from the ad platform. It runs in the visitor's browser, sets the platform's cookie and tells the platform "this person visited". That is how the person ends up in your audience. A plain redirect never runs any JavaScript: the browser asks for the link, gets told where to go and goes there. So once any pixel is set, a person's visit goes through a brief page instead: 1. The page loads each platform's standard base code for the pixels you set 2. Each pixel sends a page view 3. The page redirects to the destination The visitor leaves as soon as the scripts have loaded and had a moment to send the page view, and never later than 1.2 seconds. It is usually well under a second. This is the same short page that Advanced data collection uses. A link can use both: the visit goes through one page, which fires the pixels and records the device details. See [what data you can collect from QR code scans](/help/article/what-data-you-can-collect-from-qr-code-scans-location-device-behavior) for what Advanced records. ### Why every link tool needs a page There is no way to fire a browser pixel without running code in the browser, and there is no way to run code in the browser during a plain redirect. Every link tool that offers retargeting pixels loads a page before sending the visitor on: - Rebrandly runs retargeting scripts at redirect time - Linkly documents a short delay for links with pixels - Cuttly switches a link with a pixel to a page that redirects with a meta refresh The difference between tools is how long that page waits and which visits go through it. Linkbreakers leaves as soon as the pixels have had a moment to send, caps it at 1.2 seconds, and sends only people's visits through it. ## Who fires the pixels Only visits that Linkbreakers classifies as **Human** go through the pixel page. Everything else gets the instant redirect and never reaches your audiences: - Crawlers and other bots - Link previews, such as Slack, Teams, Discord, WhatsApp, Facebook and LinkedIn fetching a link to show its card - AI agents that name themselves, such as ChatGPT or Claude reading a link - Automated browsers that are recognized, such as headless Chrome This keeps your audiences made of people, and keeps previews and agents fast. See [how Linkbreakers detects AI agents and automated browsers](/help/article/how-linkbreakers-detects-ai-agents-and-automated-browsers) for how each visit is classified and what cannot be detected. ## Consent and privacy Pixels set marketing cookies from the ad platforms. In the EU and the UK, that usually needs the visitor's consent before the cookies are set. Linkbreakers does not show a consent banner. Deciding whether pixels are right for your audience, and covering them in your privacy policy and consent setup, is the workspace's responsibility. If your visitors are mostly in the EU or the UK, check with whoever handles privacy for you before turning pixels on. ## How to check that it works 1. Install the browser extension of the platform you set up: **Meta Pixel Helper**, Google **Tag Assistant** or **TikTok Pixel Helper** 2. Open one of your links in a normal browser window, not a private window with tracking blocked and not an automated browser 3. Watch the extension: it shows the pixel loading and the page view being sent before the redirect For Google Tag Manager, use Tag Assistant to see which of your container's tags fired. In the ad platforms, events can take a few minutes to appear, and audiences take longer to fill. Meta mentions about 24 to 72 hours before an audience is ready to use. Ad blockers and some browsers' tracking protection block pixels. Visitors with those block them on your links too, as they do on any website. ## Set it up from an AI agent, the API, the CLI or the SDKs Everything on the Pixels page can be done without the dashboard. Every interface works the same way: an update sends only the pixels to change, an empty string removes one, and the pixels you leave out keep their value. An agent can set up the other integrations the same way, including Slack, Google Forms, webhooks and the data collection level. See [set up every Linkbreakers integration with an AI agent](/help/article/set-up-linkbreakers-integrations-with-an-ai-agent-mcp). ### MCP server The [Linkbreakers MCP server](/help/article/mcp-server-setup) has two tools: - `retargeting_pixels_get` returns the workspace's pixels - `retargeting_pixels_update` sets, changes or removes them An AI agent connected to the MCP server, such as Claude or Cursor, can take a prompt like this one: > Check which retargeting pixels my Linkbreakers workspace has. Set my Meta pixel to 123456789012345 and my Google tag to G-ABC1234, remove the TikTok pixel, and leave LinkedIn and Google Tag Manager as they are. The agent reads the current pixels, sends one update with `metaPixelId`, `googleTagId` and an empty `tiktokPixelId`, and leaves the other two out. ### Assistant In the dashboard, ask the Assistant in plain words, for example "Add my Meta pixel 123456789012345 to all my links" or "Which pixels are set up on my workspace?" ### REST API Read the pixels with the `integrations:read` scope: ```bash curl https://api.linkbreakers.com/v1/retargeting-pixels \ -H "Authorization: Bearer $LINKBREAKERS_TOKEN" ``` Change them with the `integrations:write` scope: ```bash curl -X PUT https://api.linkbreakers.com/v1/retargeting-pixels \ -H "Authorization: Bearer $LINKBREAKERS_TOKEN" \ -H "Content-Type: application/json" \ -d '{"metaPixelId": "123456789012345", "googleTagId": "G-ABC1234"}' ``` The body accepts `metaPixelId`, `googleTagId`, `tiktokPixelId`, `linkedinPartnerId` and `gtmContainerId`. To remove a pixel, send its field as an empty string, for example `{"tiktokPixelId": ""}`. Both calls answer with the workspace's pixels after the change. See [API token scopes](/help/article/api-token-scopes) to create a token limited to what it needs. ### CLI The `retargeting-pixels` commands arrive with the next CLI release: ```bash linkbreakers retargeting-pixels get linkbreakers retargeting-pixels update --meta-pixel-id 123456789012345 --google-tag-id G-ABC1234 ``` The flags follow the body fields: `--meta-pixel-id`, `--google-tag-id`, `--tiktok-pixel-id`, `--linkedin-partner-id` and `--gtm-container-id`. See [CLI setup](/help/article/linkbreakers-cli-setup) to install it and sign in. ### SDKs The TypeScript, Python, Go, Java and Rust SDKs have the same two operations, get and update, with the same fields. ## Limits and caveats - **Pixels add a short delay to every visit by a person.** Usually well under a second, never longer than 1.2 seconds. Remove every pixel to go back to instant redirects - **Workspace-wide only.** Pixels apply to every link and QR code of the workspace. There is no per-link choice yet - **Page views only.** Each pixel sends a page view for the visit. Conversion events such as purchases or leads are not sent from Linkbreakers, and there is no server-side Conversions API connection - **One Google tag.** The Google tag field takes one ID. Use Google Tag Manager for more Google tags or other platforms - **No consent banner.** Consent for marketing cookies is the workspace's responsibility - **Blocked like any pixel.** Ad blockers and tracking protection block pixels on your links as they do everywhere else - **Audiences fill on the platform's schedule.** Meta mentions about 24 to 72 hours ## Frequently asked questions ### Which plans include retargeting pixels? Every plan, Free included. ### Will my links be slower? Only after you set a pixel, and only for people's visits. A short page loads before the redirect, usually well under a second and never longer than 1.2 seconds. Bots, link previews and AI agents keep the instant redirect. ### Can I add a pixel to one link and not the others? Not yet. Pixels apply to every link and QR code of the workspace. ### Can I use Pinterest, Snap, Reddit, X or Microsoft Ads? Yes, through Google Tag Manager. Add their tags to your container, publish it, and paste the container ID in the Google Tag Manager field. ### Does it work with Advanced data collection? Yes. Both use the same short page, so a link with both loads one page that fires the pixels and records the device details. ### Will link previews in Slack or WhatsApp end up in my audiences? No. Link previews, bots, AI agents and recognized automated browsers never load the pixel page. ### Does Linkbreakers send purchases or leads to the ad platforms? No. Each pixel sends a page view for the visit. Keep conversion tracking on your own website. ### Why was my ID refused? It does not have the shape that platform uses, and the save answers `RETARGETING_PIXEL_INVALID`. Check that a Meta Pixel ID or LinkedIn partner ID is digits only, that a Google tag starts with `G-` or `AW-`, and that a container ID starts with `GTM-`. ## Sources - Linkbreakers Retargeting pixels page, API and MCP tools, checked in the product on 2026-10-30. - Rebrandly, retargeting scripts: https://developers.rebrandly.com/docs/retargeting-scripts - Linkly, slow redirects: https://linklyhq.com/support/slow-redirects - Cuttly, retargeting pixels: https://cutt.ly/resources/encyclopedia/retargeting-pixels/ - Meta for Developers, Meta Pixel: https://developers.facebook.com/docs/meta-pixel/ - Google tag platform, the Google tag: https://developers.google.com/tag-platform/gtagjs - ICO, guidance on cookies and similar technologies: https://ico.org.uk/for-organisations/direct-marketing-and-privacy-and-electronic-communications/guide-to-pecr/cookies-and-similar-technologies/ ## Last reviewed 2026-10-30 by Laurent Schaffner.