Allow Conversion API to be disabled

[rcstr]

WP.org thread: https://wordpress.org/support/topic/purchase-event-missing-some-deduplication-parameters-2/

Feature requests

Based on Conversions API docs the event is part of the Pixel implementation, which can be disabled via filter (facebook_for_woocommerce_integration_pixel_enabled) but this won't disable the requests to Conversion API.

It would be great to allow customers to disable Conversion API while Pixel API stills enable.

The code in charge of sending the events to Conversion API

facebook-for-woocommerce/includes/API.php

Lines 597 to 604 in 9b1a1dc

	public function send_pixel_events( $pixel_id, array $events ) {
	$request = new API\Pixel\Events\Request( $pixel_id, $events );
	$this->set_response_handler( Response::class );
	return $this->perform_request( $request );
	}

[haszari]

Just noting that this was feature request raised as a workaround for a related issue(s): duplicate events, or event deduplication not working correctly (see forum thread and possibly related issues #1668 #1722). Based on this I'm tagging as low priority for now.

[josephbonanno74]

My client forwarded this issue to me today:

Issue: Missing Purchase Value Parameter
One or more of your Purchase events is missing a value parameter. This may affect your ability to see return on ad spend calculations.

AND

Issue: InitiateCheckout Event Missing Some Deduplication Parameters
To deduplicate identical events received by both your pixel and the Conversions API, we need to identify them by cross-checking a matching deduplication key in both sources.
Some of your InitiateCheckout events don't have a deduplication key, so we're unable to cross-check whether they're duplicate events. This means they're potentially being incorrectly counted twice and leading to inaccurate ad attribution.

AND

Issue: Purchase Event Missing Some Deduplication Parameters
To deduplicate identical events received by both your pixel and the Conversions API, we need to identify them by cross-checking a matching deduplication key in both sources.
Some of your Purchase events don't have a deduplication key, so we're unable to cross-check whether they're duplicate events. This means they're potentially being incorrectly counted twice and leading to inaccurate ad attribution.