UniPixel: Google Analytics and Meta Pixel Plugin with Server-side Sending (CAPI)

User-friendly approach to Facebook Conversion API tracking and Google Server-side Tagging for improved event sending, by-passing 3rd party cookie limitations. Eliminate Conversion API setup frustrations and send accurate, reliable events to drive smarter advertising decisions. Gets you instantly setup with Facebook Conversion API (Facebook CAPI / Meta CAPI) and Google server side tagging.

Features:
– Easy setup of common WooCommerce events
– Setup your own custom events
– Handles “click” and “shown” triggers, for any event you can think of
– Sends events using client side and server side methods for extra reliability (recommended by the platforms)
– Comes with ‘deduplication’ support to match the same client side and server side events
– Testing logs to verify events being sent
– Clean interface and simple setup

Why Use UniPixel?

UniPixel provides a structured and reliable approach to conversion tracking, offering easy integration with both the Facebook Conversion API and Google server-side tracking. By supporting server-side event reporting, UniPixel helps overcome challenges related to third-party cookie restrictions and browser privacy changes, ensuring more accurate and consistent event tracking.

Setup

How do I configure Meta (Facebook) Conversion API tracking?

To enable Meta (Facebook) Conversion API tracking, you need:
– Facebook Pixel ID
– Access Token

Getting Your Facebook Pixel ID

Log in to Facebook Business Manager: https://business.facebook.com/
Go to Events Manager.
Select your Pixel.
Copy the Pixel ID from the top-right corner.

Generating an Access Token

Go to Business Settings in Facebook Business Manager.
Navigate to System Users and click Add System User.
Assign Admin permissions and select your Business Account.
In the Permissions tab, ensure access to “Manage Ads”.
Click Generate Access Token.
Copy and save the token securely.

Enter these details in WordPress Admin > UniPixel Settings > Meta.

How do I configure Google Server-Side Tracking?

To enable Google Analytics (GA4) and Google Ads server-side tracking, you need:
– GA4 Measurement ID
– Google Tag Manager (GTM) Container ID (if using GTM)
– Google API Secret

Getting Your GA4 Measurement ID

Log in to Google Analytics: https://analytics.google.com/
Click Admin > Data Streams.
Select your website data stream.
Copy the Measurement ID (format: G-XXXXXXXXXX).

Getting Your Google Tag Manager (GTM) Container ID

Log in to Google Tag Manager: https://tagmanager.google.com/
Select your container.
Copy the Container ID (format: GTM-XXXXXX).

Getting Your Google API Secret

Go to Google Analytics Admin.
Under Data Streams, select your website stream.
Scroll down to Measurement Protocol API Secret.
Click Create, name it (e.g., “Server-Side Tracking”), and copy the API Secret.

Enter these details in WordPress Admin > UniPixel Settings > Google.

How do I enable tracking in UniPixel?

Go to WordPress Admin > UniPixel Settings.
Enable Meta or Google tracking.
Select:
- “Include Pixel for Me” – if you want UniPixel to add the tracking script.
- “Pixel Already Included” – if your site already includes tracking scripts.
Enter your Pixel ID, Access Token, or Google API details.
Click Save Changes.

What if I already have Meta or Google tracking installed?

If your site already includes tracking via another plugin or manually, select “Pixel Already Included” in UniPixel settings. This prevents duplicate tracking scripts but still allows UniPixel to send custom events.

How does server-side event tracking work?

UniPixel supports both client-side and server-side event tracking:
– Client-side events are sent directly from the browser.
– Server-side events use API calls to prevent ad blockers from blocking conversions.

To enable server-side tracking for Meta, enter your Access Token.
For Google, enter your API Secret.

How does UniPixel prevent duplicate events?

UniPixel uses event deduplication by assigning a unique event ID to each event. This ensures that events sent via both client-side and server-side are not counted twice.

Where can I find more documentation or support?

For additional setup guides and troubleshooting, visit our support page:
Support & Documentation

Tips

Deduplication

To ensure events tracked by both the Facebook Pixel and the Conversion API are not counted twice, use deduplication. This involves sending an event ID with each event tracked by the pixel and the API. Facebook uses this ID to identify and merge identical events, providing accurate tracking and reporting. Configure this in your Facebook Business Manager settings under Events Manager.

Privacy and 3rd Party Services

This plugin uses external services provided by Meta (Facebook) and Google to track and log user events for analytics and advertising purposes. The plugin interacts with the following services:

Meta (Facebook) Pixel: Sends user event data (e.g., PageView, Purchase) to Facebook for tracking purposes.
Meta’s Graph API: Sends user event data server-side for tracking and logging purposes.
Google Analytics: Sends user event data to Google for analytics and tracking via the Measurement Protocol and Google Tag Manager.

Domains

This plugin communicates with the following domains:
– Meta (Facebook):
– https://www.facebook.com
– https://graph.facebook.com
– Google:
– https://www.google-analytics.com
– https://www.googletagmanager.com
– Buildio:
– https://buildio.dev

Data Sent

Data sent to these domains may include:
– User interactions (e.g., clicks, page views, purchases)
– IP address and user agent (collected by tracking mechanisms)
– Custom event data such as purchase amount, currency, and transaction ID (depending on how the plugin is configured)
– Diagnostic information may be sent to Buildio to assist with plugin performance and bug fixes, including site url, ip address and basic interactions. No sensitive information or keys are sent.

Privacy and Terms

For more details on Meta’s and Google’s privacy policies and terms of use, please visit the following links:

License

This plugin is licensed under the GPLv2 or later.