# IsPixelWorking > Independent checker for ad tracking. Paste a landing page URL; a browser in the EU visits it twice (before cookie consent, and arriving from an ad with consent accepted and clicks on the main buttons; monitoring plans add a phone visit) and reports whether the page's Meta, TikTok and OpenAI pixels work, with a grade for each: consent handling, duplicate events, event IDs, ad click ID storage (e.g. fbclid -> _fbc) and signs of server-side tracking. Other ad platforms on the page are listed but not graded yet. Free, no sign-up. It never sends tracking data to ad platforms and never submits forms. Every page listed here has a Markdown version: send `Accept: text/markdown` or append `.md` to the path (`https://ispixelworking.com/index.md` for the home page). ## Docs - [How the check works](https://ispixelworking.com/methodology): the visits, scoring, limitations - [Pricing](https://ispixelworking.com/pricing): the free check, and monitoring plans (Pro, Agency) with prices - [About](https://ispixelworking.com/about): who makes it and why it is independent - [Contact](https://ispixelworking.com/contact): report questions, corrections, opt-outs, security, press - [Agent guide](https://ispixelworking.com/AGENTS.md): what agents can do here and what they cannot - [For AI agents](https://ispixelworking.com/ai-agents): how to connect assistants to the MCP server, tools, limits, API keys - [MCP server](https://ispixelworking.com/mcp): remote MCP server (Streamable HTTP, no sign-in) with check_page, get_report, get_fix_guide and list_findings; card at https://ispixelworking.com/mcp/server-card - [Our checker, for site owners](https://ispixelworking.com/bot): user agent, behaviour, opt-out ## Fix guides - [How to set up the Meta Conversions API (with or without a developer)](https://ispixelworking.com/guides/general.server_side_not_detected/generic): How to set up the Meta Conversions API: what you need, what it costs, options with or without a developer, and how to test and fix missing or duplicate events. - [Duplicate Meta Pixel events on Framer](https://ispixelworking.com/guides/meta.duplicate_pixel/framer): Your Framer site sends the same Meta event twice. Here is where to look in Framer, GTM and plugins to find the second installation. - [Duplicate Meta Pixel events: how to find and remove them](https://ispixelworking.com/guides/meta.duplicate_pixel/generic): Events counted twice? Find the second Meta Pixel installation (theme setting, plugin, Tag Manager or a pasted snippet) and remove it, in about 20 minutes. - [Duplicate Meta Pixel events on Shopify](https://ispixelworking.com/guides/meta.duplicate_pixel/shopify): Your Shopify store sends the same Meta Pixel event twice. Find the second copy in the Facebook & Instagram app, custom pixels, theme code, app embeds or GTM. - [Duplicate Meta Pixel events on Webflow](https://ispixelworking.com/guides/meta.duplicate_pixel/webflow): Your Webflow site sends the same Meta Pixel event twice. Find the second copy in the integrations tab, custom code, Code Embeds, GTM or form events. - [Duplicate Meta Pixel events on WordPress](https://ispixelworking.com/guides/meta.duplicate_pixel/wordpress): Your WordPress or WooCommerce site sends the same Meta Pixel event twice. Find the second copy in plugins, theme settings, code snippets or GTM. - [Facebook click ID (fbclid) lost on Framer](https://ispixelworking.com/guides/meta.fbc_not_set/framer): On your Framer site the fbclid from Meta ad clicks is not saved in the _fbc cookie. Here is how to check redirects, consent and the pixel setup. - [Facebook click ID (fbclid) lost after an ad click](https://ispixelworking.com/guides/meta.fbc_not_set/generic): The fbclid from Meta ads never reaches the _fbc cookie, so Meta cannot tie the sale to the ad. Find where it gets lost: redirects, consent or the pixel. - [Facebook click ID (fbclid) lost on Shopify](https://ispixelworking.com/guides/meta.fbc_not_set/shopify): The fbclid from Meta ad clicks is not saved in the _fbc cookie on your Shopify store. Check domain and market redirects, consent and the Meta Pixel setup. - [Facebook click ID (fbclid) lost on Webflow](https://ispixelworking.com/guides/meta.fbc_not_set/webflow): The fbclid from Meta ad clicks is not saved in the _fbc cookie on your Webflow site. Check Webflow 301 redirects, consent and the Meta Pixel setup. - [Facebook click ID (fbclid) lost on WordPress](https://ispixelworking.com/guides/meta.fbc_not_set/wordpress): The fbclid from Meta ad clicks is not saved in the _fbc cookie on your WordPress site. Check redirects, SEO and language plugins, consent and the Meta Pixel. - [Meta Pixel fires before consent on Framer: how to fix](https://ispixelworking.com/guides/meta.fires_before_consent/framer): Your Framer site's Meta Pixel fires before visitors answer the cookie banner? Route it through Framer's cookie banner or Tag Manager to wait for consent. - [Meta Pixel fires before cookie consent: how to fix it](https://ispixelworking.com/guides/meta.fires_before_consent/generic): Meta Pixel sends PageView before visitors answer the cookie banner? Confirm it, then hold the pixel until consent: in GTM, your consent tool or site code. - [Meta Pixel fires before cookie consent on Shopify](https://ispixelworking.com/guides/meta.fires_before_consent/shopify): Your Shopify store's Meta Pixel sends data before visitors answer the cookie banner. Find the copy that skips Shopify's customer privacy settings and fix it. - [Meta Pixel fires before cookie consent on Webflow](https://ispixelworking.com/guides/meta.fires_before_consent/webflow): Your Webflow site's Meta Pixel sends data before visitors answer the cookie banner. Find every copy in site settings and custom code and gate it behind consent. - [Meta Pixel fires before cookie consent on WordPress](https://ispixelworking.com/guides/meta.fires_before_consent/wordpress): Your WordPress site's Meta Pixel sends data before visitors answer the cookie banner. Find the plugin or snippet that loads it and gate it behind consent. - [Meta Pixel events have no event ID on Framer: how to fix](https://ispixelworking.com/guides/meta.missing_event_id/framer): Without an event ID, Meta cannot deduplicate your Framer site's pixel and Conversions API events. When it matters, and how to send the same ID from both. - [Meta Pixel events have no event ID](https://ispixelworking.com/guides/meta.missing_event_id/generic): Your Meta Pixel events carry no event ID, so Meta cannot match them with Conversions API events. Here is when that matters and how to add one. - [Meta Pixel events have no event ID on Shopify](https://ispixelworking.com/guides/meta.missing_event_id/shopify): Your Shopify store sends Meta Pixel events without an event ID, so Meta cannot deduplicate them with Conversions API events. When it matters and how to fix it. - [Meta Pixel events have no event ID on Webflow](https://ispixelworking.com/guides/meta.missing_event_id/webflow): Your Webflow site sends Meta Pixel events without an event ID, so Meta cannot deduplicate them with Conversions API events. When it matters and how to add one. - [Meta Pixel events have no event ID on WordPress](https://ispixelworking.com/guides/meta.missing_event_id/wordpress): WordPress and WooCommerce Meta Pixel events without an event ID cannot be deduplicated with Conversions API events. Here is how to fix it with a plugin or GTM. - [Meta Pixel not firing after consent on Framer: how to fix](https://ispixelworking.com/guides/meta.not_firing_after_consent/framer): Visitors accept the cookie banner on your Framer site, but the Meta Pixel sends nothing? Check the banner settings, Tag Manager consent and your tags. - [Meta Pixel not firing after cookie consent: how to fix it](https://ispixelworking.com/guides/meta.not_firing_after_consent/generic): Visitors accept cookies but Events Manager stays empty? Find where the consent signal gets lost: the banner, Consent Mode, GTM triggers or the pixel code. - [Meta Pixel not firing after cookie consent on Shopify](https://ispixelworking.com/guides/meta.not_firing_after_consent/shopify): The Meta Pixel is on your Shopify store but sends nothing after visitors accept cookies. Check the banner, Shopify's Customer Privacy API and the pixel itself. - [Meta Pixel not firing after cookie consent on Webflow](https://ispixelworking.com/guides/meta.not_firing_after_consent/webflow): The Meta Pixel is on your Webflow site but sends nothing after visitors accept cookies. Check the built-in integration, your consent tool, custom code and GTM. - [Meta Pixel not firing after cookie consent on WordPress](https://ispixelworking.com/guides/meta.not_firing_after_consent/wordpress): The Meta Pixel is on your WordPress site but sends nothing after visitors accept cookies. Check the consent plugin, caching and optimization plugins, and GTM. - [Meta CAPI events without a matching event ID: how to fix](https://ispixelworking.com/guides/meta.server_copy_without_event_id/generic): Your server copy of a Meta event has no event_id or a different one, so Meta may count the conversion twice. How to pass one ID from the pixel to the server. - [ChatGPT Ads click ID (oppref) lost on Framer: how to fix](https://ispixelworking.com/guides/openai.click_id_not_set/framer): On your Framer site the oppref from ChatGPT ad clicks does not end up in the __oppref cookie. Check redirects, the consent setup and your form's server events. - [ChatGPT Ads click ID (oppref) lost after an ad click](https://ispixelworking.com/guides/openai.click_id_not_set/generic): ChatGPT ads add oppref to your links and the OpenAI Pixel keeps it in __oppref. Find where it gets lost: redirects, consent, a late pixel or server events. - [ChatGPT Ads click ID (oppref) lost on Shopify](https://ispixelworking.com/guides/openai.click_id_not_set/shopify): The oppref from ChatGPT ad clicks doesn't reach the __oppref cookie on your Shopify store. Check redirects, consent and where the OpenAI Pixel runs. - [ChatGPT Ads click ID (oppref) lost on Webflow](https://ispixelworking.com/guides/openai.click_id_not_set/webflow): The oppref click ID from ChatGPT ads is not saved in the __oppref cookie on your Webflow site. Check Webflow 301 redirects, consent and the OpenAI Pixel setup. - [ChatGPT Ads click ID (oppref) lost on WordPress](https://ispixelworking.com/guides/openai.click_id_not_set/wordpress): The oppref from ChatGPT ad clicks is not saved in the __oppref cookie on your WordPress site. Check redirects, SEO and language plugins, consent and the pixel. - [How to set up the OpenAI Conversions API for ChatGPT Ads](https://ispixelworking.com/guides/openai.conversions_api_setup/generic): OpenAI Conversions API setup: Pixel ID and API key, the event payload, oppref and obref, deduplication with the pixel, testing, and fixing doubled events. - [Duplicate OpenAI Pixel events on Framer: how to fix](https://ispixelworking.com/guides/openai.duplicate_pixel/framer): Your Framer site sends the same ChatGPT Ads event twice. Where to look in Framer's custom code, Tag Manager and form scripts for the second copy. - [Duplicate OpenAI Pixel events: how to find and remove them](https://ispixelworking.com/guides/openai.duplicate_pixel/generic): ChatGPT Ads events sent twice? Find the second OpenAI Pixel installation (site code, Tag Manager, plugin or app), keep one, and check your measure calls. - [Duplicate OpenAI Pixel events on Shopify](https://ispixelworking.com/guides/openai.duplicate_pixel/shopify): Your Shopify store sends the same ChatGPT Ads event twice. Find the second OpenAI Pixel in Customer events, ChatGPT Ads apps, theme code, app embeds or GTM. - [Duplicate OpenAI Pixel events on Webflow](https://ispixelworking.com/guides/openai.duplicate_pixel/webflow): Your Webflow site sends the same ChatGPT Ads event twice. Find the second OpenAI Pixel copy in custom code, Code Embeds, GTM or form code, and keep one. - [Duplicate OpenAI Pixel events on WordPress and WooCommerce](https://ispixelworking.com/guides/openai.duplicate_pixel/wordpress): Your WordPress or WooCommerce site sends ChatGPT Ads events twice. Find the second OpenAI Pixel in plugins, WPCode, Elementor, theme code or GTM, and keep one. - [Repeated OpenAI event IDs drop ChatGPT Ads conversions](https://ispixelworking.com/guides/openai.event_id_reused/generic): OpenAI keeps only the first event with a given event_id. If every visit sends the same ID, real conversions are dropped. Find the fixed or cached ID. - [OpenAI Pixel fires before consent on Framer: how to fix](https://ispixelworking.com/guides/openai.fires_before_consent/framer): The ChatGPT Ads pixel on your Framer site measures before the cookie banner is answered? Move it into Tag Manager behind Framer's Cookie Banner. - [OpenAI Pixel fires before cookie consent: how to fix it](https://ispixelworking.com/guides/openai.fires_before_consent/generic): The ChatGPT Ads pixel assumes consent unless told otherwise. Confirm it fires before the banner is answered, then gate it with oaiq consent, GTM or your CMP. - [OpenAI Pixel fires before cookie consent on Shopify](https://ispixelworking.com/guides/openai.fires_before_consent/shopify): Your Shopify store's ChatGPT Ads pixel sends events before visitors answer the cookie banner. Find the copy that skips Shopify's privacy settings and fix it. - [OpenAI Pixel fires before cookie consent on Webflow](https://ispixelworking.com/guides/openai.fires_before_consent/webflow): The ChatGPT Ads pixel on your Webflow site measures before visitors answer the banner. Find every copy in custom code, embeds and GTM, and gate it. - [OpenAI Pixel fires before cookie consent on WordPress](https://ispixelworking.com/guides/openai.fires_before_consent/wordpress): The ChatGPT Ads pixel on your WordPress site measures before visitors answer the cookie banner. Find what loads it and put it behind your consent plugin. - [OpenAI Pixel event_id missing on Framer: fix deduplication](https://ispixelworking.com/guides/openai.missing_event_id/framer): Your Framer site sends ChatGPT Ads events without its own event_id. When that matters, and how to share one ID between the pixel and server events. - [OpenAI Pixel event_id missing: fix ChatGPT Ads deduplication](https://ispixelworking.com/guides/openai.missing_event_id/generic): Without your own event_id, the ChatGPT Ads pixel makes up a random ID your server never sees, so pixel and Conversions API events can't be deduplicated. - [OpenAI Pixel events have no event ID on Shopify](https://ispixelworking.com/guides/openai.missing_event_id/shopify): Your Shopify store sends ChatGPT Ads pixel events without its own event_id, so they can't be matched with Conversions API events. When it matters and the fix. - [OpenAI Pixel events have no event ID on Webflow](https://ispixelworking.com/guides/openai.missing_event_id/webflow): Your Webflow site sends ChatGPT Ads events without its own event_id, so they can't be matched with Conversions API events. When it matters and how to add one. - [OpenAI Pixel event_id missing on WordPress and WooCommerce](https://ispixelworking.com/guides/openai.missing_event_id/wordpress): WordPress sends ChatGPT Ads events without your own event ID, so pixel and Conversions API events can't be deduplicated. Fix it with a plugin, GTM or code. - [OpenAI Pixel tracks a button on desktop but not on mobile](https://ispixelworking.com/guides/openai.mobile_cta_tracking_mismatch/generic): A button sends a ChatGPT Ads event on desktop but not on mobile, or the reverse. Usually the mobile layout has its own copy of the button. How to fix it. - [Two OpenAI Pixel IDs on one site: when it's fine, how to fix](https://ispixelworking.com/guides/openai.multiple_pixels/generic): Two ChatGPT Ads Pixel IDs split your conversions unless that's the plan. Find where each comes from, remove the stray one, or use measureSingle. - [OpenAI Pixel not firing after consent on Framer: how to fix](https://ispixelworking.com/guides/openai.not_firing_after_consent/framer): Visitors accept the cookie banner on your Framer site, but the ChatGPT Ads pixel sends nothing? Check the banner, Tag Manager consent, triggers and the tag. - [OpenAI Pixel not firing after cookie consent: how to fix it](https://ispixelworking.com/guides/openai.not_firing_after_consent/generic): Visitors accept cookies but the ChatGPT Ads pixel stays silent? Find the break: the banner, oaiq consent, GTM triggers, or a page view sent too early. - [OpenAI Pixel not firing after cookie consent on Shopify](https://ispixelworking.com/guides/openai.not_firing_after_consent/shopify): The ChatGPT Ads pixel is on your Shopify store but sends nothing after visitors accept cookies. Check the banner, Customer events permissions and pixel code. - [OpenAI Pixel not firing after cookie consent on Webflow](https://ispixelworking.com/guides/openai.not_firing_after_consent/webflow): The ChatGPT Ads pixel is on your Webflow site but sends nothing after visitors accept cookies. Check the consent tool, oaiq consent calls, custom code and GTM. - [OpenAI Pixel not firing after cookie consent on WordPress](https://ispixelworking.com/guides/openai.not_firing_after_consent/wordpress): The ChatGPT Ads pixel is on your WordPress site but sends nothing after visitors accept cookies. Check the consent plugin, oaiq consent, optimizers and GTM. - [OpenAI Pixel setup for ChatGPT Ads conversion tracking](https://ispixelworking.com/guides/openai.pixel_setup/generic): Install the OpenAI Pixel (the ChatGPT Ads Measurement Pixel) step by step: the oaiq snippet, conversion events, event IDs, cookie consent, Tag Manager and testing. - [OpenAI Conversions API deduplication: match the pixel event_id](https://ispixelworking.com/guides/openai.server_copy_without_event_id/generic): Your server copy of a ChatGPT Ads event has no event ID or a different one, so OpenAI may count the conversion twice. How to pass one ID from browser to server. - [ttclid (TikTok click ID) lost on Framer: how to fix](https://ispixelworking.com/guides/tiktok.click_id_not_set/framer): On your Framer site the ttclid from TikTok ad clicks is not stored in the ttclid cookie. Check redirects, Auto Locale, consent and the pixel setup. - [ttclid (TikTok click ID) lost after an ad click: how to fix](https://ispixelworking.com/guides/tiktok.click_id_not_set/generic): TikTok ads add ttclid to your links and the pixel keeps it in a ttclid cookie. Find where it gets lost: redirects, consent, cookie settings or server events. - [ttclid (TikTok click ID) lost on Shopify](https://ispixelworking.com/guides/tiktok.click_id_not_set/shopify): The ttclid from TikTok ad clicks is not saved in the ttclid cookie on your Shopify store. Check redirects, consent, custom pixels and the TikTok Pixel settings. - [ttclid (TikTok click ID) lost on Webflow](https://ispixelworking.com/guides/tiktok.click_id_not_set/webflow): The ttclid from TikTok ad clicks is not saved in the ttclid cookie on your Webflow site. Check Webflow 301 redirects, locales, consent and the pixel setup. - [ttclid (TikTok click ID) lost on WordPress](https://ispixelworking.com/guides/tiktok.click_id_not_set/wordpress): The ttclid from TikTok ad clicks is not saved on your WordPress site. Check redirects, SEO and language plugins, consent, caching and the TikTok Pixel. - [Duplicate TikTok Pixel events on Framer: how to fix](https://ispixelworking.com/guides/tiktok.duplicate_pixel/framer): Your Framer site sends the same TikTok event twice. Where to look in Framer's custom code, plugins and Tag Manager, and how to stop double page views. - [Duplicate TikTok Pixel events: how to find and remove them](https://ispixelworking.com/guides/tiktok.duplicate_pixel/generic): TikTok events counted twice? Find the second TikTok Pixel installation (theme code, app, plugin or Tag Manager), keep one, and stop double page views. - [Duplicate TikTok Pixel events on Shopify](https://ispixelworking.com/guides/tiktok.duplicate_pixel/shopify): Your Shopify store sends the same TikTok Pixel event twice. Find the second copy in the TikTok app, custom pixels, theme code, app embeds or GTM, and keep one. - [Duplicate TikTok Pixel events on Webflow](https://ispixelworking.com/guides/tiktok.duplicate_pixel/webflow): Your Webflow site sends the same TikTok Pixel event twice. Find the second copy in custom code, Code Embeds, GTM, Apps or form events, and keep one. - [Duplicate TikTok Pixel events on WordPress](https://ispixelworking.com/guides/tiktok.duplicate_pixel/wordpress): Your WordPress or WooCommerce site sends the same TikTok Pixel event twice. Find the second copy in plugins, theme settings, code snippets or GTM. - [Repeated TikTok event IDs drop real conversions: how to fix](https://ispixelworking.com/guides/tiktok.event_id_reused/generic): TikTok drops events that repeat an event name and event_id within 48 hours. If every visit sends the same ID, real conversions vanish. Find and fix it. - [How to set up the TikTok Events API (with deduplication)](https://ispixelworking.com/guides/tiktok.events_api_setup/generic): TikTok Events API setup: partner apps, Events API Gateway, server-side GTM or direct code. Access token, payload, event_id deduplication, testing and fixes. - [TikTok Pixel fires before consent on Framer: how to fix](https://ispixelworking.com/guides/tiktok.fires_before_consent/framer): Your Framer site's TikTok Pixel sends events before visitors answer the cookie banner? Move it into Google Tag Manager behind Framer's Cookie Banner. - [TikTok Pixel fires before cookie consent: how to fix it](https://ispixelworking.com/guides/tiktok.fires_before_consent/generic): TikTok Pixel sends events before visitors answer the cookie banner? Confirm it, then hold the pixel with TikTok's consent mode, Google Tag Manager or your CMP. - [TikTok Pixel fires before cookie consent on Shopify](https://ispixelworking.com/guides/tiktok.fires_before_consent/shopify): Your Shopify store's TikTok Pixel sends data before visitors answer the cookie banner. Find the copy that skips Shopify's privacy settings and fix it. - [TikTok Pixel fires before cookie consent on Webflow](https://ispixelworking.com/guides/tiktok.fires_before_consent/webflow): Your Webflow site's TikTok Pixel sends data before visitors answer the cookie banner. Find every copy in custom code, embeds, GTM and apps, then gate it. - [TikTok Pixel fires before cookie consent on WordPress](https://ispixelworking.com/guides/tiktok.fires_before_consent/wordpress): Your WordPress site's TikTok Pixel sends data before visitors answer the cookie banner. Find the plugin or snippet that loads it and gate it behind consent. - [TikTok Pixel event_id missing on Framer: how to add it](https://ispixelworking.com/guides/tiktok.missing_event_id/framer): Your Framer site's TikTok events have an empty event_id, so they can't be matched with Events API events. When it matters, and how to add one shared ID. - [TikTok Pixel event_id missing: how to add it for deduplication](https://ispixelworking.com/guides/tiktok.missing_event_id/generic): TikTok Pixel events with an empty event_id can't be matched with Events API events, so conversions may count twice. When it matters and how to add the ID. - [TikTok Pixel events have no event ID on Shopify](https://ispixelworking.com/guides/tiktok.missing_event_id/shopify): Your Shopify store sends TikTok Pixel events with an empty event_id, so TikTok can't match them with Events API events. When it matters and how to fix it. - [TikTok Pixel event_id missing on Webflow](https://ispixelworking.com/guides/tiktok.missing_event_id/webflow): Your Webflow site sends TikTok Pixel events with an empty event_id, so TikTok can't match them with Events API events. When it matters and how to add one. - [TikTok Pixel event_id missing on WordPress and WooCommerce](https://ispixelworking.com/guides/tiktok.missing_event_id/wordpress): WordPress and WooCommerce TikTok Pixel events without an event_id can't be matched with Events API events. Fix it with one plugin for both, GTM or code. - [TikTok Pixel tracks a button on desktop but not on mobile](https://ispixelworking.com/guides/tiktok.mobile_cta_tracking_mismatch/generic): A button sends a TikTok event on desktop but not on mobile, or the reverse. Usually the mobile layout has its own copy of the button. How to track both. - [Two TikTok Pixels on one site: when it's fine, how to fix](https://ispixelworking.com/guides/tiktok.multiple_pixels/generic): Two TikTok pixel codes on one page split your data unless that's the plan. Find where each comes from, remove the stray one, or use ttq.instance. - [TikTok Pixel not firing after consent on Framer: how to fix](https://ispixelworking.com/guides/tiktok.not_firing_after_consent/framer): Visitors accept the cookie banner on your Framer site, but the TikTok Pixel sends nothing? Check the Cookie Banner, Tag Manager consent and triggers. - [TikTok Pixel not firing after cookie consent: how to fix it](https://ispixelworking.com/guides/tiktok.not_firing_after_consent/generic): Visitors accept cookies but the TikTok Pixel stays silent? Find the break: the banner, holdConsent and grantConsent, GTM triggers or the pixel code itself. - [TikTok Pixel not firing after cookie consent on Shopify](https://ispixelworking.com/guides/tiktok.not_firing_after_consent/shopify): The TikTok Pixel is on your Shopify store but sends nothing after visitors accept cookies. Check the banner, Shopify's Customer Privacy API and the pixel setup. - [TikTok Pixel not firing after cookie consent on Webflow](https://ispixelworking.com/guides/tiktok.not_firing_after_consent/webflow): The TikTok Pixel is on your Webflow site but sends nothing after visitors accept cookies. Check grantConsent, your consent tool, custom code order and GTM. - [TikTok Pixel not firing after cookie consent on WordPress](https://ispixelworking.com/guides/tiktok.not_firing_after_consent/wordpress): The TikTok Pixel is on your WordPress site but sends nothing after visitors accept cookies. Check TikTok's plugin, the consent plugin, caching plugins and GTM. - [TikTok Events API deduplication: match the pixel's event_id](https://ispixelworking.com/guides/tiktok.server_copy_without_event_id/generic): Your server copy of a TikTok event has no event_id or a different one, so TikTok may count the conversion twice. How to pass one ID through to the Events API. - [Meta Pixel and Complianz: fire only after cookie consent](https://ispixelworking.com/guides/consent/complianz): Make Meta, TikTok and OpenAI pixels wait for Complianz marketing consent on WordPress and fire on the same page: Tag Manager, Script Center or a plugin. - [Meta Pixel and Cookiebot: fire only after cookie consent](https://ispixelworking.com/guides/consent/cookiebot): Make Meta, TikTok and OpenAI pixels wait for Cookiebot marketing consent and fire on the same page once accepted: Tag Manager, code or auto-blocking. - [Meta Pixel and CookieYes: fire only after cookie consent](https://ispixelworking.com/guides/consent/cookieyes): Make Meta, TikTok and OpenAI pixels wait for CookieYes Advertisement consent and fire on the same page: Tag Manager, script blocking or consent APIs. - [Meta Pixel and OneTrust: fire only after cookie consent](https://ispixelworking.com/guides/consent/onetrust): Make Meta, TikTok and OpenAI pixels wait for OneTrust targeting consent and fire on the same page: Google Tag Manager, script rewriting or auto-blocking. - [Meta Pixel and Usercentrics: fire only after cookie consent](https://ispixelworking.com/guides/consent/usercentrics): Link Meta, TikTok and OpenAI pixels to Usercentrics services so they wait for consent and fire on the same page: Tag Manager, markup or auto-blocking. ## Blog - [What is ob3_plugin-set_ in Meta Pixel event IDs?](https://ispixelworking.com/blog/ob3-plugin-set-event-id): Event IDs that start with ob3_plugin-set_ are made by the Meta Pixel itself when a Conversions API Gateway is connected. What they mean and when they matter. - [How to check if your Meta Pixel is working](https://ispixelworking.com/blog/check-meta-pixel-working): A green icon in Meta's extension is not proof. How to check your Meta Pixel with Events Manager, Data Advisor and your browser, and fix what you find. - [Facebook Pixel not tracking purchases? Why Meta shows fewer sales](https://ispixelworking.com/blog/events-manager-fewer-events): Your shop shows 200 orders, Meta shows 140 purchases. Which part of the gap is normal, which is a tracking problem, and how to find and fix it. - [What is fbclid? The Facebook click ID and the _fbc cookie, explained](https://ispixelworking.com/blog/fbclid-fbc-cookie-explained): fbclid is the click ID Meta adds to links from Facebook and Instagram. What it means, how it differs from UTM tags, whether to remove it, and how to keep it. - [Meta Pixel event deduplication: why every event needs an event ID](https://ispixelworking.com/blog/pixel-and-conversions-api-event-ids): How Meta deduplicates Pixel and Conversions API events, how to set up matching event IDs on Shopify, GTM or custom code, and how to test it in Events Manager. ## What the report can contain - No Meta Pixel found (meta.pixel_missing, info) - Meta Pixel fires before cookie consent (meta.fires_before_consent, critical) - Meta Pixel does not fire after consent (meta.not_firing_after_consent, critical) - Meta blocks this pixel on this website (meta.pixel_blocked, critical) - Meta event IDs repeat across visits (meta.event_id_reused, high) - Duplicate Meta events (meta.duplicate_pixel, high) - Meta events have no event ID (meta.missing_event_id, high) - Click ID from Meta ads is not stored (meta.fbc_not_set, high) - Mobile buttons are tracked differently from desktop (meta.mobile_cta_tracking_mismatch, medium) - Click ID saved by your site code in a non-standard format (meta.custom_fbc_format, medium) - Two different browser IDs (_fbp) (meta.conflicting_fbp, medium) - More than one Meta Pixel (meta.multiple_pixels, low) - No advanced matching (meta.no_advanced_matching, low) - No ad pixel found (general.no_pixel, info) - No server-side tracking detected (general.server_side_not_detected, info) - Server-side tracking detected (general.server_side_detected, info) - The site blocked our checker (general.blocked_by_site, n/a) - Cookie banner could not be operated automatically (general.cmp_not_operable, info) - Purchase events were not tested (general.purchase_events_not_tested, info) - Button testing stopped early (general.cta_coverage_partial, info) - Tracking through the site's own domain (general.first_party_tracking_detected, info) - Meta server events have no event ID (meta.server_copy_without_event_id, high) - Meta server events carry a different event ID (meta.server_event_id_mismatch, high) - TikTok Pixel fires before cookie consent (tiktok.fires_before_consent, critical) - TikTok Pixel does not fire after consent (tiktok.not_firing_after_consent, critical) - TikTok event IDs repeat across visits (tiktok.event_id_reused, high) - Duplicate TikTok events (tiktok.duplicate_pixel, high) - TikTok events have no event ID (tiktok.missing_event_id, high) - Click ID from TikTok ads is not stored (tiktok.click_id_not_set, high) - Mobile buttons are tracked differently from desktop (tiktok.mobile_cta_tracking_mismatch, medium) - More than one TikTok Pixel (tiktok.multiple_pixels, low) - TikTok server events have no event ID (tiktok.server_copy_without_event_id, high) - TikTok server events carry a different event ID (tiktok.server_event_id_mismatch, high) - OpenAI Pixel fires before cookie consent (openai.fires_before_consent, critical) - OpenAI Pixel does not fire after consent (openai.not_firing_after_consent, critical) - OpenAI event IDs repeat across visits (openai.event_id_reused, high) - Duplicate OpenAI events (openai.duplicate_pixel, high) - OpenAI events have no event ID (openai.missing_event_id, high) - Click ID from OpenAI ads is not stored (openai.click_id_not_set, high) - Mobile buttons are tracked differently from desktop (openai.mobile_cta_tracking_mismatch, medium) - More than one OpenAI Pixel (openai.multiple_pixels, low) - OpenAI server events have no event ID (openai.server_copy_without_event_id, high) - OpenAI server events carry a different event ID (openai.server_event_id_mismatch, high)