scits

Hi @pixelyoursite

The above-mentioned method loads the Pixel through the PYS plugin, the deduplication seems to work.

Hi Daniel,

I had the same question and solved it like this:
https://www.ads-software.com/support/topic/use-meta-conversion-api-without-meta-pixel-id

Cheers.

I was able to solve this as follows:

1. Disable PYS and Meta Pixel cookies in functions.php:
   add_filter( 'pys_disable_all_cookie', '__return_true', 10, 2 );
add_filter( 'pys_disable_facebook_by_gdpr', '__return_true', 10, 2 );
2. Disable existing Meta Pixel code in Google Tag Manager
3. Create a new Custom HTML Tag with the following code:
   <script>
pys.Facebook.loadPixel();
</script>
   
   Under consent settings -> Additional Consent Checks -> Require additional consent for tag to fire -> ad_storage

Seems to work nicely so far ??

Great, thank you so much! Have a great week as well!

Sorry for my late reply & thank you so much for the update. I’ve just deployed it and will monitor the results. Thanks again!

Hi there,

Thank you so much for your detailed analysis and reply.

To me it is still not quite clear when exactly a submission gets added to the Flamingo spam category with reCaptcha V2. Every time the V2 challenge fails? For example, we had a false positive submission three times in the spam category and once in the Inbox category. Does that mean, the user failed the V2 challenge three times and succeeded on the fourth attempt?

For troubleshooting purposes it might be useful to log failed V2 captcha attempts in some circumstances, but in our case it just fills up the DB unnecessarily. Maybe it can be added as an option to the plug-in? E.g an option “log failed V2 captcha attempts”.

Thank you for all your efforts and happy Easter!

Just to follow up, even after removing the above mentioned customization, there are still messages flagged as SPAM in Flamingo. They are indeed spam but as mentioned above if the V2 challenge fails, the data should never be posted to the server.

Hi there,

Thanks for your prompt feedback. One important thing to note is that we’ve adjusted the CF7 reCaptcha V3 spam score in the template’s function as follows:

// Reduce reCAPTCHA v3 Spam treshold to 0.1 to avoid false positives
// 0.0 (easiest = no spam protection works) and 1.0 (strictest = every submission will be marked as spam).
add_filter( 'wpcf7_recaptcha_verify_response',
	function( $is_human, $response_body ) {
		$score = isset( $response_body['score'] ) ? $response_body['score'] : 0;
		$threshold = 0.1;
		$is_human = $threshold < $score;
		return $is_human;
	},
	10, 2
);

This was due to the fact that we had so many false positives with reCaptcha V3. Maybe this somehow clashed with your V2 plugin? In any case, we have now removed this code block from our functions.php file and will observe if there are still submissions flagged as spam.

It looks like if I just get the values through $_POST instead of $submission->get_posted_data(); I get the “raw” form values.