by
Dominik Seitz
0 (0 reviews)
Pixel Made Simple
Meta Pixel & Conversions API, Google Ads, GA4 and TikTok tracking with event deduplication, URL events, form leads and GDPR consent detection.
Pixel Made Simple ranks #52,723 among WordPress.org plugins with 0+ active installations, and was last updated Sep 19, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.1
v0.12.7
Current Version v0.12.7
Updated 3 days ago
Last Update on 19 Sep, 2026
Refreshed 11 hours ago
Last Refreshed on
Actively maintained
Rank
#52,723
—
No change
Active Installs
0+
—
No change
KW Avg Position
110.5
1 worse
Downloads
59
+5 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
21,056
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 6 more installs to reach 10+
Rank Changes
Current
#52,723
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 0.12.7
- Last Updated
- Sep 19, 2026
- Requires WP
- 6.3+
- Tested Up To
- 7.1.1
- PHP Version
- 7.4 or higher
- Author
- Dominik Seitz
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade Now
Frequently Asked Questions
Common questions about Pixel Made Simple
Only the ones you configure yourself. With no platform set up it writes no third-party script, image or request into your pages at all. Every address it can contact, what is transmitted and when, is listed under External services below.
Enter the test event code from the Events Manager (tab Test events) in the General tab. Server events then show up there in real time. The code is removed automatically after 12 hours. For debugging you can make the request blocking, after which the raw Meta response is written to the debug log when WP_DEBUG_LOG is enabled: add_filter( 'pxms_capi_blocking', '__return_true' );
That is your decision, and the plugin lets you make it per provider. By default every privacy tracker runs through exactly the same marketing consent gate as the Meta, Google and TikTok pixels – nothing loads until the visitor accepts, and it then starts without a page reload. The Load without consent switch changes that for one provider only; the advertising platforms are never affected by it. The background: Section 25 TDDDG covers storing information on, or reading it from, a visitor’s device. A tracker that sets no cookie and uses no local storage is not covered by it; the GDPR level applies regardless. Whether that reasoning holds depends on the specific service and where it is hosted, and it is legally contested. Pixel Made Simple makes no claim about any third-party service being compliant – it only provides the setting.
The one from your own dashboard, copied verbatim – for example https://plausible.io/js/script.js, https://cloud.umami.is/script.js or https://app.rybbit.io/api/script.js. Self-hosted instances use your own domain instead. The plugin deliberately does not assemble that address from a host name. All three providers have changed their paths at least once (Umami moved from /umami.js to /script.js, Plausible issues newer accounts a per-site tracker filename, Rybbit switched from an attribute to a query parameter). A path guessed by the plugin would eventually be silently wrong: the script loads and no data arrives.
No, and that is intentional. They are not conversions, they never go through the Conversions API, and counting them would dilute exactly the numbers you use to investigate missing advertising conversions. The event log and the consent statistics keep reporting on Meta, Google and TikTok only.
The automatic cookie banner detection (on by default) checks the consent cookies of the supported banner plugins and the WP Consent API on the server. Without marketing consent the browser scripts are deferred (they listen for the banner’s consent events and start right after the click on “Accept”) and the Conversions API request is not sent. If no supported banner is installed, nothing is blocked. For unsupported banners you can provide the consent result yourself: add_filter( 'pxms_has_marketing_consent', function ( $consent ) { return my_marketing_consent(); } ); And you can suppress all tracking server-side: add_filter( 'pxms_allow_tracking', function ( $allow ) { return my_consent_check(); } );
The browser pixel: yes. The Conversions API is normally only triggered when PHP actually renders the page, so with aggressive full-page caching you should exclude your conversion pages from the cache – otherwise CAPI events are not sent at all, and every visitor shares the one event ID baked into the cached HTML. One exception, since 0.11.0: a URL event that participates in the handover to the confirmation page is sent from the browser and generates its event ID per visitor. That one works on a cached page. All other URL events still need the page to be excluded from the cache.
No. sessionStorage belongs to exactly one origin, so nothing travels to another domain or subdomain – the same applies to a form inside an iframe from a different origin. In those cases both events are counted separately, exactly as before version 0.11.0. If the confirmation page is on a subdomain, moving it to a path on the main domain (/thank-you/ instead of thanks.example.com) is enough to get the full match.
Three things have to line up. In your Google Ads account, Enhanced Conversions must be enabled for that conversion action and the customer data terms accepted – without that Google discards the data silently and still counts the conversion. In the plugin, the event needs a conversion label. And for the phone number Google requires the international format: if your form collects 0151 … without a country code, only the email address is sent. The filter pxms_normalize_phone can add the country code.
pxms_allow_tracking – allow or suppress tracking globally. pxms_has_marketing_consent – override the result of the cookie banner detection (guards the browser pixel). pxms_has_server_consent – the same for server-side signals (Conversions API, TikTok Events API). Only relevant when the consent mode is set to “Block browser pixels only”. pxms_consent_banner_active – register your own banner with the detection. pxms_consent_events – additional banner events for the frontend listener. pxms_capi_event_data – modify a single CAPI event before it is sent (e.g. add custom_data). pxms_capi_user_data – modify the user_data payload. pxms_normalize_phone – adjust the normalised phone number before hashing (e.g. add a country code). Also decides whether Google gets a phone number at all: without a country code there is no valid E.164 value, and none is sent. pxms_graph_api_version – override the Graph API version. pxms_capi_blocking – send the CAPI request blocking (debugging). pxms_tiktok_capi_blocking – the same for TikTok Events API requests (Pixel Made Simple Pro, debugging). Upgrading from “Lightweight Meta Pixel & CAPI Tracker”? These filters used to be called lmpct_*. Custom code that hooks into one of them must be updated to the pxms_* names – see the 0.6.0 changelog entry.