Full Answer

Meta introduced one-click CAPI to lower the technical barrier for stores that have no server-side tracking in place. The setup provisions a server-side event pipeline managed by Meta, captures WooCommerce events through a lightweight integration, and begins sending them to the Conversions API without requiring the store owner to configure webhooks, manage API tokens, or write server-side code.

For stores starting from zero — no existing CAPI plugin, no server-side pipeline — one-click CAPI is a reasonable entry point. It provides immediate server-side event coverage with minimal setup friction.

The problem arises when a store already has a functioning CAPI integration. Whether through PixelYourSite Pro, a custom implementation, or a server-side pipeline tool, the existing setup is already sending events to Meta. Enabling one-click CAPI on top creates a second, independent event stream. The same purchase triggers two server-side events to Meta — one from the existing plugin and one from the one-click pipeline.

Meta's deduplication mechanism requires matching event_id values to recognise duplicate events. Since one-click CAPI and third-party plugins generate event IDs independently, the duplicates are not caught. The result: Meta Ads Manager reports roughly twice the actual conversion volume, cost-per-acquisition appears artificially low, and the delivery algorithm optimises toward inflated conversion signals — overspending on audiences that appear more profitable than they are.

The decision rule is straightforward. If the store has no server-side tracking: one-click CAPI is a sensible first step. If the store already runs CAPI through any other method: do not enable one-click CAPI. If switching to one-click CAPI: fully remove the existing integration first. Never run both simultaneously.