Out of the total websites in the world, more than 40% are built using WordPress. That’s a huge number for any CMS platform and hence, there is a great chance that your website is built using WordPress. Also, you probably use the WordPress Contact Form 7 plugin for your website's contact us form.
So tracking of WordPress contact form 7 is extremely important.
We will show two ways to track WordPress contact form 7
- Traditional Google tag manager way that would take a lot of time.
- and Tagmate way! ( No Code set up and fast way) 😲
Adding a Facebook pixel to your website allows you to track user actions and optimize your Facebook ads. However, sometimes you may need multiple Facebook pixels on your site.This could happen when managing multiple ad accounts, tracking different websites or businesses separately, conducting testing and development, focusing on specific goals or events. Also, having multiple pixels can cause issues with tracking events accurately.
Confused how to configure it right? We’ve got your back!
In this guide by Tagmate experts, we'll explain how to properly setup and use multiple Facebook pixels to track events for each pixel separately.
Why Use Multiple Pixels?
There are a few common reasons you may need multiple Facebook pixels on your website:
- You work with different ad accounts for different business units or objectives. For example, one pixel for an ecommerce store, another for lead generation.
- You have different agencies or partners managing Facebook ads for you. Each wants their own pixel to monitor performance.
- You have both production and test/staging environments and want to test pixels before going live.
In these types cases, you'll want to initialize multiple pixels but track unique events per pixel.
Problems with Multiple Pixels
Without special setup, having multiple Facebook pixels can cause issues:
- Duplicate events: An event fired for one pixel may also fire for the other pixels. This inflates your event counts.
- Mixing data: Events and parameters meant for one pixel are also sent to the others. This makes the data messy.
This happens because the Facebook pixel script shares event data across initialized pixels by default. We need additional configuration to isolate events per pixel.
Using trackSingle to Separate Events
Luckily, the Facebook pixel provides a trackSingle method to track events for a specific pixel only.
To use it:
- Initialize multiple pixels normally with fbq('init', pixelId);
- Call fbq('trackSingle', pixelId, eventName, optionalParams);
This fires the event for that single pixel ID only.
For example:
Now the Purchase event will only be sent to Pixel 1.
You can use trackSingle for your standard events like ViewContent, AddToCart, and Purchase.
Using trackSingleCustom for Custom Events
For custom events, use the trackSingleCustom method instead. This works the same way:
This will fire the Register custom event only for Pixel 2.
Best Practices for Tracking Multiple Facebook Pixels on Your Site
When using multiple Facebook pixels, keep these best practices in mind:
- Initialize all pixels normally with fbq('init')
- Use trackSingle and trackSingleCustom to isolate events per pixel
- Fire track events that should apply to all pixels
- Consider using a tag manager to better organize your pixels
- Test thoroughly to ensure pixels receive the correct data
- Document which events fire on which pixels for your team
With some strategic setup, you can successfully use multiple Facebook pixels on your website. Segmenting the event data with trackSingle methods avoids messy overlaps.
Now you can efficiently manage multiple ad accounts, agencies, or environments while tracking accurate event data for each Facebook pixel.
Wrap Up
We hope that this guide will help you streamline your marketing efforts and manage your tags more efficiently. We have created a template-based FCAPI implementation feature in Tagmate.
Sign up now to automate FCAPI implementation on your website!
.png)
.svg)
.svg)
.svg)
.svg)
