Question

My conversion tracking stopped working after installing a new 3rd-party analytics plugin. How can I verify what broke?

Answer 1

You're likely dealing with a conflict between your Meta Pixel (or other conversion tag) and the third-party analytics plugin — very common when scripts overlap or misfire. Here’s a step-by-step process to diagnose and fix what broke:

How to Verify What Broke

1. Use Debugging Tools

Install and run:

• Meta Pixel Helper (for Facebook/Meta Ads)

• Google Tag Assistant (or Tag Assistant Companion) (for GA4/GTM)

• Microsoft Clarity, Hotjar, etc. – disable them one by one if involved

Visit your conversion/thank-you page, and:

• Check if your conversion event (e.g. Purchase, Lead) is firing

• Look for errors like:

  • fbq is not defined

  • gtag is not a function

  • Duplicate or missing tags

2. Open Browser Console (F12)

Check for JavaScript errors or script conflicts.

Look specifically for:

• JavaScript conflicts or undefined functions

• CSP (Content Security Policy) blocks

• Errors in loading scripts (404s or blocked resources)

3. Inspect Network Requests

In your browser dev tools:

• Go to Network tab → Filter by “collect”, “fbq”, or “track”

• Reload your page

• Check if requests to Meta (facebook.com/tr/) or Google Analytics (collect) are sent

No request = tag is broken or not loading at all.

4. Temporarily Disable the Plugin

Turn off the new plugin and re-test:

• If conversion tracking resumes → the plugin is the culprit.

• You may need to:

  • Change plugin settings to avoid overriding global variables (fbq, gtag, etc.)

  • Load tags manually via Google Tag Manager instead of letting both plugin and theme load them.

5. Check Tag Manager or Hardcoded Tags

If you use Google Tag Manager:

• Check if the plugin modified or paused your tag triggers

• Ensure conversion triggers are still firing on the correct URL/pageview/form submit

If tags are hardcoded:

• View page source and check if your pixel/tag code has been removed, replaced, or moved

Common Culprits in Plugin Conflicts

Issue	Result
Plugin loads a different tag version	Breaks or duplicates existing scripts
Plugin injects tracking late or async	Delays event firing or misses it completely
Plugin uses same global variables (fbq, gtag)	Overwrites Meta or Google functions
Plugin restricts scripts via CSP	Blocks tracking scripts

What to Do Next?

1. Isolate the plugin (disable and re-test)

2. Check script order – your tags should load before the plugin adds its logic

3. Use Tag Manager for all tracking to centralize control and reduce plugin risk

4. If needed, contact the plugin developer and ask if it conflicts with Meta Pixel, GA4, or GTM