suhanduman

Stop losing sales to ad blockers and browser restrictions. Send accurate events to Meta CAPI & Pinterest CAPI and manage all tags with GTM. This plugin creates a direct, reliable server-side bridge between your store and the Meta (Facebook) and Pinterest Conversions APIs (CAPI), while also integrating Google Tag Manager (GTM) for your browser-side tags.
The key advantage is getting all the benefits of server-side tracking—like improved data accuracy and better ad optimization—without the cost and complexity of a separate GTM Server Container. This powerful approach helps you capture more conversions, build stronger lookalike audiences, and achieve a higher ROI on your ad campaigns.
Key Benefits:
<ul>
<li>Maximize Your Ad ROI: Feed Meta and Pinterest’s algorithms with accurate, server-side data to improve ad optimization, build higher-quality lookalike audiences, and run more profitable retargeting campaigns.</li>
<li>Eliminate Extra Cloud Costs: Get the full power of server-side tracking without the complexity and monthly fees of a Google Tag Manager Server Container or other cloud services.</li>
<li>Prevent Data Loss: By sending data directly from your server, you bypass ad blockers and browser tracking restrictions, capturing conversions that the Pixel might miss.</li>
<li>Ensure Perfect Data Integrity: Our unified dataLayer guarantees that your server (CAPI) and browser (Pixel) events use the same ID, completely eliminating duplicate conversion data.</li>
</ul>
Core Features:
<ul>
<li>Direct CAPI for Meta & Pinterest: Integrates directly with both Meta (Facebook) and Pinterest’s Conversions API, sending rich e-commerce events from your server.</li>
<li>Smart GTM Integration: Automatically injects the Google Tag Manager script and creates a comprehensive, standards-compliant dataLayer for all your browser-side tags (Meta Pixel, Pinterest, GA4, etc.).</li>
<li>Full WooCommerce Event Coverage: Tracks all critical e-commerce events right out of the box.</li>
<li>Built-in Debug Log: Easily monitor and debug every server-side event with a real-time, filterable log that shows success and failure responses from the APIs.</li>
</ul>
Please check the installation page for the recommended GTM settings for deduplication.
<h3>Our Philosophy</h3>
This plugin is completely free and fully functional. There are no hidden “pro” versions or locked features. We believe in providing powerful, accessible tools for the WordPress community. If you find this plugin useful, please consider supporting its continued development with a <a href="https://buymeacoffee.com/suhanduman" rel="nofollow ugc">donation</a>. Thank you!
<h3>External Services</h3>
This plugin connects your website to external services to send event data.
<ul>
<li>Service Used: Meta Conversion API
<ul>
<li>Purpose: To send user interaction and e-commerce event data from your server to Meta’s servers for ad performance measurement, optimization, and audience building.</li>
<li>Data Sent: Event details (product ID, price) and user parameters (IP address, user agent, hashed email/name/phone, Facebook cookies) are sent when a user performs a key action.</li>
</ul>
</li>
<li>Service Used: Pinterest Conversions API
<ul>
<li>Purpose: Same as the Meta CAPI, providing reliable tracking for ad performance and audience building on Pinterest.</li>
<li>Data Sent: Event details and hashed user parameters are sent upon user action.</li>
</ul>
</li>
<li>Service Used: Google Tag Manager
<ul>
<li>Purpose: To load a JavaScript container from Google’s servers that allows you to manage and deploy marketing and analytics tags.</li>
<li>Data Sent: The plugin provides your GTM Container ID to Google to fetch the correct script. GTM itself may collect data based on how you configure your tags.</li>
</ul>
</li>
</ul>

All-in-one CAPI for Meta & Pinterest + GTM

Short Description All-in-one server-side tracking for Meta (Facebook) CAPI, Pinterest CAPI, and Google Tag Manager (GTM)

eddr

secretchord.io

This plugin offers a way to queue Ajax calls, skipping the loading of the the bulk of WP system, saving considerable system resources in the form of CPU load and runtimes. This operation can be set for any AJAX call.
This is done by catching the AJAX calls early in the WP lifecycle, via an MU plugin. The calls are santized ( user should define fields ) and ar stored in a queue for later processing. The queue system is based on Automattic’s own Action Scheduler plugin.
Processing the calls : the calls are processed in bulk via a hook that is run by CRON.
The original motivation for this development was to handle the multitudes AJAX calls that the PixelYourSite evokes when the facebook conversation API is in use. The conversation API requires the server to send the tracking information instead of the client browser. This means possibly lots of calls even if the site is beyond walls of cache.
<h4>Who is it for</h4>
At this stage the plugin is a developer level plugin and is intended to be used as such. It requires defining fields for sanitation. 
However, it comes with a basic implementation for the latest PixelYourSite API calls and can be easily activated without further configuration for most cases.
<h4>The flow</h4>
<ul>
<li>AJAX call evoked in the client browser -></li>
<li>MU plugin catches the call if the configuration includes the specific action of the call -></li>
<li>Processor ( built-in or user defined ) checks the data and sanitizes it -></li>
<li>Data is stored in DB to be handled in queue. The data includes the call’s data and cookies -></li>
<li>Data is processed in batch via a CRON hook. The processing is done via the same “Processor”.</li>
</ul>
<h4>Basic terminogoly</h4>
Processor : A class/instance that is used to define the data map of fields for sanitation and later on, for batch processing. In many cases, the Processor will be quite simple. Please check the built-in Processor class “class-pys.php” under the “qacp/Processors” directory. 
Data Map : The map of fields and their respectable sanitation functions. There’s an example in the “qacp/qacp-how-to.txt” file.
<h4>Things to Remember</h4>
<ul>
<li>The Processor should define clearly what are the received fields and their sanitation functions.</li>
<li>The action and processor should be registerd. There’s an example in the “qacp/qacp-how-to.txt” file.</li>
</ul>
<h4>Hooks</h4>
<ul>
<li>qacp/processors/active_processors</li>
<li>qacp/processors/actions</li>
<li>qacp/processors/identify_processor</li>
<li>
qacp/processors/instance_by_action_name
</li>
<li>
qacp_before_batch_processing
</li>
<li>qacp_before_process_entry_{$_action_name}</li>
<li>qacp_before_process_entry</li>
<li>qacp_process_one_entry_{$_action_name}</li>
<li>qacp_process_one_entry</li>
<li>qacp_mark_event_finished</li>
<li>qacp_after_process_entry_{$_action_name</li>
<li>qacp_after_process_entry</li>
<li>qacp_after_batch_processing</li>
</ul>

Queue Ajax Calls Performantly

Provides a way to queue Ajax calls in a considerably more performantly via an MU plugin.  Allows processing these calls as a batch.

All-in-one CAPI for Meta & Pinterest + GTM vs Queue Ajax Calls Performantly