PixelPair – Marketing Tracking

PixelPair brings your WordPress tracking into one workspace. Connect Meta, Google Analytics, Google Tag Manager and TikTok, choose what to track, and inspect server delivery results from your dashboard. https://www.youtube.com/watch?v=uRdT0o2IcUc A skippable setup wizard helps you choose connections, paste IDs, check configuration and exclude your own visits. Paste a Meta or Google code snippet and PixelPair extracts the supported ID for you. Tracking starts disabled. You choose which connections and events to enable. PixelPair is independently developed by Arif Hasnat. It integrates with Meta, Google Analytics, Google Tag Manager, TikTok, WooCommerce and Easy Digital Downloads. It is not affiliated with or endorsed by those services or their owners. Connections

• Meta Pixel and Conversions API.
• Google Analytics 4 and Google Tag Manager.
• TikTok Pixel and Events API.
• Shared event IDs for supported browser/server events.
• Encrypted credentials, retries and redacted logs.

Events and stores

• Automatic event controls for pages, search, forms, accounts and engagement.
• Custom rules for button clicks, page visits, scroll depth and other supported triggers.
• Per-platform event mappings and payload previews.
• WooCommerce product, cart, checkout and paid purchase tracking, including supported Blocks flows and HPOS.
• Easy Digital Downloads tracking for supported download, cart, checkout and purchase flows.
• Configurable product identifiers and purchase values.

WooCommerce and Easy Digital Downloads are optional. Their own WordPress and PHP requirements also apply. See the store guide for supported combinations and delivery limits. Privacy and administration

• Consent integrations and a setting to wait for explicit marketing consent.
• Role, IP address, CIDR and bot exclusions.
• Fast cache mode and optional strict visitor eligibility checks.
• Configuration import and export that never includes secrets.
• Per-site settings on WordPress multisite.
• Optional authenticated access for external AI tools through the WordPress MCP Adapter.

PixelPair has no telemetry, advertisements or upsells. Enabled tracking connections communicate with the external services described below. It does not guarantee platform acceptance, attribution accuracy or compliance with privacy laws. Getting started | Documentation | Screenshots Connect your AI tools with MCP Connect compatible external AI tools to inspect settings, custom events and redacted logs, and manage settings and events through authenticated MCP access. PixelPair does not include an AI chat or contact an AI provider itself. Requires WordPress 6.9 or later, the official WordPress MCP Adapter, HTTPS and a WordPress Application Password for an account with the manage_pixelpair capability. Open Settings > Manage AI access to find your endpoint and site ID. Access tokens and role grants are not exposed through MCP. AI access setup guide Consent and personal data When no consent tool is detected, marketing consent is granted by default. Enable "Wait for marketing consent" and configure a supported consent integration if you need visitors to opt in. When a consent tool is detected, unresolved or denied consent blocks the relevant tracking. Depending on enabled settings, event data can include page URLs and titles, referrers, search strings, product identifiers, cart or order totals, IP addresses, user agents, browser identifiers and attribution. Optional advanced matching uses hashed contact fields. Hashing does not make contact data anonymous. Consented collection uses first-party browser, click and visitor identifiers. PixelPair's Meta and visitor cookies expire after 90 days, and its TikTok click identifier after 30 days. Vendor scripts manage their own cookies. Session storage can hold attribution and event counters. See the bundled documentation for queue/log retention and deletion controls. External services Meta When enabled and marketing consent allows, the browser loads the official Meta Pixel script from connect.facebook.net. Server events are sent to graph.facebook.com using your Pixel ID and access token. Meta can receive event names, page and product details, values, IP addresses, user agents, browser/click identifiers and optional hashed matching fields. Requests occur for permitted tracked actions, authorized connection tests and queued retries. Meta terms | Meta privacy policy Google Analytics and Google Tag Manager When enabled and the required consent is granted, Google scripts load from googletagmanager.com or your configured HTTPS tagging domain. Google Analytics receives page/event data and consent signals. Tag Manager executes your published container, which can contact additional services according to the tags you configure. Review those tags separately. PixelPair uses basic consent mode and does not load Google scripts before the required grant. Google Analytics terms | Google Tag Manager terms | Google privacy policy TikTok When enabled and marketing consent allows, the browser loads the TikTok Pixel script from analytics.tiktok.com. Server events are sent to business-api.tiktok.com using your credentials. TikTok can receive page, product and event details, values, IP addresses, user agents, browser/click identifiers and optional hashed contact fields. Requests occur for permitted tracked actions, authorized connection tests and queued retries. TikTok advertiser terms overview | TikTok privacy policy Optional AI access PixelPair does not contact an AI provider itself. External clients connect to your site using WordPress Application Passwords over HTTPS and require the manage_pixelpair capability. Optional AI access requires WordPress 6.9 or later and the official WordPress MCP Adapter.

1. Download the built pixelpair.zip release.
2. In WordPress, open Plugins > Add New > Upload Plugin.
3. Select pixelpair.zip, choose Install Now, then activate PixelPair.
4. Open PixelPair and follow the setup wizard.
5. Choose your connections, paste IDs and add server credentials if needed.
6. Configure Privacy, enable your desired tracking and clear your page cache.
7. Visit your site and verify events with the platform's tools.

To update, upload the newer built ZIP and choose to replace the installed version. Replacement preserves settings. Composer and Node.js are not required on your WordPress host.

0.9.4

• Publish illustrated documentation on a dedicated public site and update documentation links.
• Check documentation pages, images and internal links automatically before publishing.

0.9.3

• Use PixelPair – Marketing Tracking as the product name without a personal-name prefix.
• Update the plugin title, directory banners, documentation and translation source.

0.9.2

• Clarify the independent project name and third-party service integrations.
• Limit consent recommendations to PixelPair screens and hide resolved recommendations.
• Limit migration errors to relevant management screens.
• Update documentation, translation source and directory graphics.

0.9.1

• Remove arbitrary script insertion and execution for the WordPress.org distribution.
• Add WooCommerce and Easy Digital Downloads tracking and TikTok browser/server events.
• Include the finalized WordPress.org readme and automatic translation loading.
• Add setup, secret-free configuration transfer, privacy tools and optional authenticated MCP access.
• Introduce focused connection screens, a sentence-style event builder and unsaved-change protection.
• Add store controls and HPOS-safe purchase attribution with persistent purchase claims.