Pixel Cat – Conversion Pixel Manager
Facebook Pixel For WordPress Made Easy
Pixel Cat – Conversion Pixel Manager (formerly known as “Facebook Conversion Pixel”) lets you add a Facebook(Meta) Pixel and Conversions API or Google Analytics Pixel to your site in a matter of minutes.
From Facebook Retargeting to conversion tracking, this free plugin makes setting up your Facebook and Google Analytics Pixel a breeze.
Run Better Facebook Ad Campaigns
Using Pixel Cat, you can track Facebook and Google Conversions and build powerful retargeting audiences.
Track Facebook Conversions
Send conversion events (including the exact amount and currency) to Facebook to Google, so you can track, improve and automatically optimize your ad campaigns.
Build Powerful Retargeting Audiences
Pixel Cat lets you send granular events (blog posts read, products viewed, …) to Facebook and Google, so you can build insanely effective retargeting audiences.
Conversions API
Pixel Cat has a quick and easy Conversions API that will have you running server side tracking in no time.
Upgrading from the Old Facebook Conversion pixel?
This plugin used to be called Facebook Conversion Pixel and was updated to work with the new Facebook Pixel. Facebook has deprecated the old Facebook Conversion Pixel in favor of the new pixel, so we highly recommend migrating.
Wondering how to migrate from the old Facebook Conversion Pixel to the new Facebook Pixel? Read this blog post:
How to Migrate to the new Facebook Pixel
How Pixel Cat helps you run better ads
Our Facebook Pixel manager – Pixel Cat – comes with everything you need to run successful Facebook and Google ads. This plugin lets you easily add the new Facebook Pixel, Conversions API or Google Analytics Pixel to your WordPress site with ease, so you can track conversions and create retargeting audiences.
>> For more details & screnshots, head over to our website <<
- Create Standard Events. Standard Events let you track conversions, optimize your ads and build retargeting audiences. Pixel Cat’s point & click builder makes the cumbersome process of setting up Standard Events easy.
- Customize Pixel Event Parameters, so you can track ad ROI. Customize your Facebook Pixel event parameters (eg. price, currency, …) on with our easy interface.
- Segment Visitors By Pages Viewed. Trigger Facebook Pixel Events & set up Custom Audiences based on which Pages, Posts, Categories and/or Tags your visitors have viewed.
- Powerful Facebook Pixel Event Builder. Our easy-to-use, powerful Facebook Pixel WordPress event builder includes everything you need, without touching a line of code.
- Search event. Automatically track searches on your WordPress site.
- Exclude Team Members. Make sure you don’t pollute your Pixel data by excluding members of your team. You can exclude specific WordPress user levels, such as Admins, Editors & Contributors.
- No Coding Required. Our 1-click setup takes the pain out of setting up the Facebook Pixel for WordPress, no coding required.
- Completely Free. Pixel Cat Lite is completely free, and includes everything you need to get started with the Facebook and Google Analytics Pixel. Experienced advertiser? We also offer a powerful paid version that will help you boost your Ad ROI.
>> For more details & screnshots, head over to our website <<
Advanced Advertiser? Build Better, More Profitable Ad Campaigns With Pixel Cat Premium
Pixel Cat Lite has everything you need to get started, but Pixel Cat Premium lets you take your ads to the next level.
In addition to supporting Standard Events, you’ll be able to set up Custom Events & Dynamic Events.
Dynamic Events – a key part of many advanced Facebook marketer’s toolkits – are insanely effective. These events trigger based on user behavior, such as time on site, or specific buttons or links clicked. Using this information, you’ll be able to exclude bouncing visitors, build better Custom Audiences and ultimately boost your Ad ROI.
- Trigger Dynamic Events. Pixel Cat lets you build insanely powerful dynamic Facebook pixel events for WordPress. Create Custom Audiences based on which links & buttons visitors click.
- Exclude Bouncing Visitors. Using our Time delay setting, you can exclude bouncing visitors by only firing a Facebook Pixel event after your visitor has spent some time on your site.
- Track Valuable User Info. Automatically send HTTP referrer, post categories, post tags and even Google Analytics UTM tags as event parameters, so you can build more effective custom audiences.
- Create Custom Events. Want to create your own custom events, so you can track behavior on your site more accurately? Building custom events is a breeze with Pixel Cat.
- Phenomenal Email Support. Need help? You’re in great hands – our fast & friendly support team is ready to help.
- WooCommerce integration. Personalize your Facebook ads without doing manual work, and retarget shoppers to complete the sale. Using Pixel Cat’s WooCommerce Event Tracking and WooCommerce Product Feed features you’ll be able to create highly effective Dynamic Product Ads & Custom Audiences.
- Easy Digital Downloads integration. Set up the Facebook Pixel for Easy Digital Downloads with a single click. Personalize your ads, retarget prospects and grow your sales. Using Pixel Cat’s Easy Digital Downloads Event Tracking and Easy Digital Downloads Product Feed features you’ll be creating Dynamic Product Ads & Custom Audiences in minutes.
>> Learn more about Pixel Cat Premium here <<
Why use Pixel Cat – Conversion Pixel Manager?
There are multiple ways to add a Facebook Pixel to your WordPress site.
1. Pasting your Facebook Pixel into your theme
This approach isn’t great for two reasons:
a) If you edit your live site and make a mistake when pasting your Facebook Pixel script into your theme, you could take down your website.
b) If your theme is updated with new features or security fixes, your Facebook Pixel code will be overwritten.
2. Pasting the new Facebook Pixel script into a header/footer script plugin
This is a valid approach, but has some disadvantages. General purposes “header script plugins” aren’t built from the ground-up to support Facebook’s Pixel.
What this means is that :
a) These plugins lack Facebook-specific functionality. There’s no easy way to add Standard Events, Custom Events or Dynamic Events.
b) These plugins will not adapt if Facebook changes their pixel again in the future. Since Pixel Cat is a dedicated Facebook Pixel plugin, we’ll make sure make sure to stay compatible with future changes by Facebook.
c) These plugins usually don’t support hiding your Facebook Pixel from logged-in users.
And, most importantly: with Pixel Cat you can set up Facebook Pixel standard events, without having to write a single line of code.
The bottom line is that Pixel Cat is the best way to add a Facebook Pixel to your WordPress site.
Does Pixel Cat – Conversion Pixel Manager support the new Facebook Pixel?
Yes. Pixel Cat is built from the ground up to support the new Facebook Pixel.
If you’re currently using v1.3.5, or later, for the old deprecated Facebook Pixel, and would like to continue doing so, no worries. Pixel Cat – Conversion Pixel Manager will automatically detect your old settings, and will let you continue using the old version of the plugin for this purpose. You can then upgrade to the new pixel at any time.
Can I hide my Facebook Pixel form logged in users?
Yes. You can hide your Facebook Pixels from logged in users by going to Settings -> Facebook Pixel Manager.
Is Pixel Cat – Conversion Pixel Manager easy to translate?
Yes. Pixel Cat – Facebook Pixel Cat is fully translateable. Please let us know if you’re interested in contributing.
Do you integrate with WooCommerce
Yes, our our pro plugin makes setting up a Facebook Pixel WooCommerce integration a breeze. Not only that, Pixel Cat Premium lets you create a Facebook Product Catalog for WooCommerce. Click here to learn more.
What is a Facebook Pixel and how does it help my business?
Please read this guide: Facebook Pixel WordPress Installation & Best Practices: The Definitive Guide. Selling on Amazon? Read this.
| Domain | Exposures | Headers | Last Checked |
|---|---|---|---|
| a*r*l*e*l*m*a*.com (WP 7.0.2) | F | Jul 30, 2026 | |
| u*b*n*a*p*s.com (WP 7.0) | F | Jul 30, 2026 | |
| f*r*a*m*n*d.com (WP 7.0.2) | F | Jul 30, 2026 | |
| f*r*a*l*e.com | C | Jul 30, 2026 | |
| m*s*i*b*q.com (WP 5.0.3) | F | Jul 30, 2026 | |
| t*e*i*d*r*i*e*l*g.com (WP 7.0.2) | F | Jul 30, 2026 | |
| c*m*i*g*e*7*a*x.fr (WP 7.0.2) | F | Jul 30, 2026 | |
| c*r*i*g*h*l*i*s*r*n*e.com (WP 7.0.2) | C | Jul 30, 2026 | |
| f*r*m*s*o*n*e.com (WP 5.7.15) | B | Jul 30, 2026 | |
| k*m*o*y*o*n*a.pl (WP 6.9.4) | F | Jul 30, 2026 | |
| s*k*r*-*u*e*o*s*.com (WP 6.4.3) | F | Jul 30, 2026 | |
| l*y*n*b*r*o*.com (WP 6.9.5) | D | Jul 30, 2026 | |
| h*g*t*a*k.com (WP 7.0.2) | F | Jul 30, 2026 | |
| m*s*i*m*n*g*m*n*l*d.com (WP 6.5.5) | F | Jul 30, 2026 | |
| t*e*u*c*i*n*l*.com | F | Jul 30, 2026 | |
| s*l*e*c*m*a*i*n*g*.com (WP 6.9.5) | F | Jul 30, 2026 | |
| s*l*e*c*m*a*i*n*.com (WP 6.9.5) | F | Jul 30, 2026 | |
| p*a*-*.com | F | Jul 30, 2026 | |
| n*f*a*.com | F | Jul 30, 2026 | |
| t*e*a*c*h*l*.sn (WP 7.0.2) | F | Jul 30, 2026 | |
| l*w*c*e*t*v*m*d*a.com (WP 7.0.2) | F | Jul 30, 2026 | |
| f*r*x*a*i*u*a*i*n.com (WP 6.6.5) | F | Jul 30, 2026 | |
| g*k*p*a*e*.nl | B | Jul 30, 2026 | |
| m*r*g*g*-*v*n*e.com | F | Jul 30, 2026 | |
| f*r*v*r*o*n*a*t*b*o*r*p*i*s.com (WP 7.0.2) | F | Jul 30, 2026 | |
| n*p*1*5*s*o*e.com | F | Jul 30, 2026 | |
| a*g*s*u*a*d*a*o*i*a.com (WP 7.0.2) | F | Jul 30, 2026 | |
| l*w*e*c*b*a*e.com (WP 7.0.2) | F | Jul 30, 2026 | |
| s*m*e*h*u*e*o*s*o*.org (WP 6.8.6) | F | Jul 30, 2026 | |
| d*e*m*d*a*n*s*i*s.com (WP 7.0.2) | F | Jul 30, 2026 | |
| l*v*n*l*u*g*h*s*e*.com (WP 7.0.2) | F | Jul 30, 2026 | |
| s*m*l*m*d*l*n*.com (WP 6.7) | F | Jul 30, 2026 | |
| c*l*i*c*u*t*h*m*n*s*c*e*y.org | F | Jul 30, 2026 | |
| d*e*k*o*s*e*t.com (WP 5.4.19) | F | Jul 30, 2026 | |
| w*o*s*o*e*o*p.com | C | Jul 30, 2026 | |
| w*o*s*o*e*c*r*.com | C | Jul 30, 2026 | |
| m*r*i*o*f*s*n.com (WP 7.0.2) | C | Jul 30, 2026 | |
| t*a*l*f*n*a*n*-*e*-*n*s.fr | F | Jul 30, 2026 | |
| d*d*a*g*n.com | F | Jul 30, 2026 | |
| s*l*t*i*b*e.com | B | Jul 30, 2026 | |
| w*l*-*a*t*r*n*.de (WP 5.8.13) | F | Jul 30, 2026 | |
| l*w*b*t*e*.com (WP 7.0.2) | D | Jul 30, 2026 | |
| t*e*r*o*e*g*a*s.com | F | Jul 30, 2026 | |
| l*w*e*i*s*r*n*e.com (WP 7.0.2) | C | Jul 30, 2026 | |
| d*d*v*d*o*h*g.com | F | Jul 30, 2026 | |
| p*i*c*o*-*z.com (WP 7.0.2) | D | Jul 30, 2026 | |
| f*l*o*i.c*m.br | F | Jul 30, 2026 | |
| m*r*c*o*l*r*c*s.com (WP 7.0.2) | F | Jul 30, 2026 | |
| d*c*n*l*n*a*a*.com | F | Jul 30, 2026 | |
| w*o*g*i*.com | D | Jul 30, 2026 | |
| w*o*f*r*r*n*a*s.com (WP 6.9.5) | F | Jul 30, 2026 | |
| w*o*f*r*h*m*s*r*u*.com (WP 6.8.6) | F | Jul 30, 2026 | |
| t*e*n*u*a*c*a*t*s*.com (WP 7.0.2) | C | Jul 30, 2026 | |
| d*c*r*s*a*k*r.com | F | Jul 30, 2026 | |
| d*c*i*i*.com | F | Jul 30, 2026 | |
| d*c*i*i*l*.com | F | Jul 30, 2026 | |
| s*i*a*s*c*e*.com | F | Jul 30, 2026 | |
| p*i*a*e*r*c*i*e*k*l*s.com | F | Jul 30, 2026 | |
| d*c*r*c*n*e*.com (WP 6.9.5) | F | Jul 30, 2026 | |
| t*e*n*l*e*t*a*v*i*e*o*k.com | F | Jul 30, 2026 | |
| c*r*l*n*p*r*o*a*.com | F | Jul 30, 2026 | |
| w*o*b*i*g*n*t*r*p*t*.com (WP 7.0.2) | F | Jul 30, 2026 | |
| c*r*l*n*p*t*o*n*l*s*r*s.com | F | Jul 30, 2026 | |
| p*i*a*e*h*f*o*a*o.com (WP 7.0.2) | F | Jul 30, 2026 | |
| d*g*t*l*h*m*s.in (WP 7.0.2) | F | Jul 30, 2026 | |
| w*o*a*h.com | D | Jul 30, 2026 | |
| c*r*l*n*h*m*e*t*r*o*s.com | F | Jul 30, 2026 | |
| d*b*o*k*s*u*r*.com | F | Jul 30, 2026 | |
| a*d*o*n*.com (WP 6.9.5) | B | Jul 30, 2026 | |
| e*r*n*l*n*c*i*a*o.it (WP 7.0.2) | F | Jul 30, 2026 | |
| w*n*e*s*r*c*b*o*s.com (WP 7.0.2) | F | Jul 30, 2026 | |
| c*r*l*-*e*e*.com (WP 6.6.2) | F | Jul 30, 2026 | |
| m*r*n*a*n*e*t*r*u*.com (WP 7.0.2) | F | Jul 30, 2026 | |
| d*b*3.com | F | Jul 30, 2026 | |
| d*a*i*-*r*r*h*a*.com (WP 6.6.2) | F | Jul 30, 2026 | |
| p*r*o*a*e*i*n.ie | F | Jul 30, 2026 | |
| j*s*w*e*.net (WP 5.8.13) | F | Jul 30, 2026 | |
| a*d*l*d*b*u*o*.com (WP 7.0.2) | F | Jul 30, 2026 | |
| 1*k*r*w.com | F | Jul 30, 2026 | |
| 1*f*b*.com | F | Jul 30, 2026 | |
| l*n*o*d*n*u*e*.com (WP 7.0.2) | C | Jul 30, 2026 | |
| l*n*o*d*n*u*a*c*.com (WP 7.0.2) | C | Jul 30, 2026 | |
| l*n*c*s*o*e.com | F | Jul 30, 2026 | |
| m*c*i*e*e*h.c*.za (WP 6.9.5) | F | Jul 30, 2026 | |
| h*t*h*s*n*t.com (WP 6.7.5) | F | Jul 30, 2026 | |
| a*c*i*n*r*u*s.com (WP 7.0.2) | F | Jul 30, 2026 | |
| s*h*r*r*s*t*a*e*s.com (WP 7.0.2) | D | Jul 30, 2026 | |
| l*v*n*u*e*a*t*s*i*u*.com (WP 7.0.2) | F | Jul 30, 2026 | |
| t*e*u*t*x*h*n*e.com | F | Jul 30, 2026 | |
| d*a*i*d*a*s.com | F | Jul 30, 2026 | |
| c*r*i*e*i*e*i*i*m*r*d*.com (WP 7.0.2) | F | Jul 30, 2026 | |
| a*c*l*m*i*r.com | C | Jul 30, 2026 | |
| a*c*c*o*s*n*f*o*t*e*e.com (WP 7.0.2) | F | Jul 29, 2026 | |
| c*r*e*s*a*u*r*l*e.com | F | Jul 29, 2026 | |
| s*g*w*s*o*b*t*n*c*l*.com (WP 7.0.2) | B | Jul 29, 2026 | |
| t*a*h*n*s*i*n*e.us (WP 7.0.2) | B | Jul 29, 2026 | |
| w*m*n*s*r*n*t*n*t*o*.com | C | Jul 29, 2026 | |
| p*i*o*n*-*r*i*v*d*.com (WP 6.8.6) | F | Jul 29, 2026 | |
| a*u*-*t*r.c*.jp (WP 5.8.13) | F | Jul 29, 2026 | |
| a*b*r*e*a*q*e.com (WP 7.0.2) | F | Jul 29, 2026 |