CAPI Suite: Meta Pixel, Pinterest & TikTok for WooCommerce
by shan 5 (2 reviews)

CAPI Suite: Meta Pixel, Pinterest & TikTok for WooCommerce

Meta Pixel, Pinterest & TikTok server-side CAPI. Recovers conversions that ad blockers and iOS hide. No monthly server, no pro tier, no limits.

CAPI Suite ranks #18,202 among WordPress.org plugins with 70+ active installations, is #2,865 of 12,463 in the E-commerce category, a 5/5 rating from 2 reviews, and was last updated Sep 4, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1
v3.11.0 Current Version v3.11.0
Updated 2 weeks ago Last Update on 04 Sep, 2026
Refreshed 10 hours ago Last Refreshed on
#2,865 of 12,463 in E-commerce Top 25% by installs Downloads -45.3% this week Actively maintained
View on WordPress.org
Rank
#18,202
No change
Active Installs
70+
+14.8%
KW Avg Position
18.4
No change
Downloads
503
+3 today
Support Resolved
100%
No change
Rating
100%
Review 5 out of 5
5 (2 reviews)

Next Milestone 80

Total Progress 10%
70+ 80+
7,046
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
Upgrade to Pro
Need 9 more installs to reach 80+

Rank Changes

17,462 17,704 17,946 18,188 18,430 16-09-2026 17-09-2026 18-09-2026 19-09-2026 20-09-2026 21-09-2026 22-09-2026 23-09-2026
17,390 17,789 18,189 18,589 18,989 08-09-2026 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026 16-09-2026 17-09-2026 18-09-2026 19-09-2026 20-09-2026 21-09-2026 22-09-2026 23-09-2026
Current #18,202
Change
Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Active Installs 0,000,000+
Growth +0.0%
Peak 0,000,000

Downloads Growth

0 10 20 16-09-2026 17-09-2026 18-09-2026 19-09-2026 20-09-2026 21-09-2026 22-09-2026 23-09-2026
0 10 20 08-09-2026 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026 16-09-2026 17-09-2026 18-09-2026 19-09-2026 20-09-2026 21-09-2026 22-09-2026 23-09-2026
Downloads
Growth
Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

5.0
2 reviews
Overall 100%
5
2 (100%)
4
0 (0%)
3
0 (0%)
2
0 (0%)
1
0 (0%)

Support Threads Overview

Resolved
Unresolved
2
Total Threads
2
Resolved
0
Unresolved
100%
Resolution Rate

Frequently Asked Questions

Common questions about CAPI Suite: Meta Pixel, Pinterest & TikTok for WooCommerce

No, it works alongside it. The plugin sends server-side (CAPI) events, while GTM handles the browser-side Pixel. Both use the same event_id, so Meta merges them automatically without counting anything twice.
A GTM Server Container runs on Google Cloud and costs money every month. This plugin does the same job directly from your WordPress server — no extra infrastructure, no extra bill.
Yes. PageView and ViewCategory events fire from JavaScript, so they work even on fully cached pages. Cart, checkout, and purchase pages are not cached by default.
WooCommerce. That's it. If another plugin on your site also manages Google Tag Manager or sends e-commerce events, turn its e-commerce tracking off so the same event is not counted twice. The Health tab tells you if it finds a pixel or measurement ID configured in two places at once.
No. Everything is included. My events aren't showing in Meta Events Manager. Open the Event Log tab. If events appear there with "Success (Meta)", the plugin is sending — anything missing on Meta's end is a Pixel ID / Access Token mismatch. If the log is empty, your JS optimizer is likely deferring the inline scripts (see next answer) or your CMP auto-blocker converted them to type="text/plain" (see the CMP question below).
Add these four IDs to your optimizer's "exclude from defer / combine" list: mcapi-pageview-init, mcapi-viewcontent-events, mcapi-viewcategory-events, mcapi-frontend-events. Cloudflare Rocket Loader is handled automatically via data-cfasync="false".
Yes. GTM Preview shows my browser tags firing, but the plugin's Event Log is empty. Your CMP's auto-blocker is converting the plugin's inline scripts to type="text/plain". The plugin already carries opt-out attributes for Cookiebot, CookieYes, and Complianz; less common CMPs (OneTrust etc.) need the mcapi_inline_script_attrs filter — see CMP Auto-Blocking in Advanced Configuration. I sell subscriptions — Meta is over-attributing renewals to old ads. The plugin auto-detects WooCommerce Subscriptions and offers three behavior modes (Default / Skip / Subscribe + SubscriptionRenewal). Pick Skip or the dedicated-events mode to keep Purchase clean. See WooCommerce Subscriptions in Advanced Configuration.
Not by default — server-side CAPI fires from PHP, doesn't see your gtag('consent', ...) signals. The Privacy & Consent section has a Strict server-side consent mode toggle: when consent is denied, hashed PII is stripped from the CAPI payload but the event still ships with its event_id, so Meta's browser↔CAPI dedup keeps working without identifying data. Recommended ON for EU stores. See Strict server-side consent mode in Advanced Configuration.
Rarely. Visitors with click IDs (fbclid / gclid / ttclid), Apple Private Relay IPs, logged-in customers, or prior-visit _fbp / _ga cookies all bypass the filter. Purchase events are never blocked. A brand-new VPN visitor with no cookies has their first PageView held; if they purchase, the full funnel is replayed so Meta sees the complete journey. Every blocked request is auditable in the Excluded Traffic tab.
TikTok's Events Manager can show you something this plugin cannot see from your server. Open Events Manager -> your Web Event Set -> Events, pick a recent Purchase (or any event the plugin sent with a customer phone on it), and look at the event's detail view: the parameters TikTok accepted are listed there, and phone appears under the user section. If phone is listed, matching is working; if the event arrived but no phone parameter is listed at all, the field is not reaching TikTok. The same view carries TikTok's own Event Match Quality score for the event set, which is the number that moves when phone matching starts working. If you use Test Events with a test event code, the same detail is visible there within a minute or two, without waiting for reporting to settle. (In 3.11.0 the plugin switched the phone and click-ID fields to the names TikTok's current Events API 2.0 reads — user.phone and user.ttclid — from the Events API 1.0 names it had been sending; if you were on an earlier version, this is the screen where the difference shows up.)

Sign In / Register

You need to sign in or register to use this feature.