Does the Captureclicktrough functionality have Botclick protection?

General
, , , , ,
1

Dear Community,

I’m currently looking into implementing the click trough fucnctionality for our links in e-mails:
https://docs.pega.com/bundle/customer-decision-hub/page/customer-decision-hub/cdh-portal/container-captureclickthrough-api.html

I however have a question about implementing this into email specifically. For e-mails lots of spamfilters create the so called botclicks, where the spamfilter itself opens the links in the e-mail even before the end-user recieves the e-mail. This would create false positive clicks and feedback to our models which is unwanted.

Normally the click registration of an ESP has protection in place to recognize and filter out these botclicks. Because I want to implement the click trough functionality of Pega this ESP protection would not work, therefore I want to know if there is any protection for this behavour on the capture clicktrough functionality from Pega side.

Do you have implementend this feature in your e-mails or SMS messages and have any insight if all clicks are being reported or if there is an filter in place

Some info about botclicks:
https://help.klaviyo.com/hc/en-us/articles/22981852783899

Thanks in advance!

2

@RubenM17178824 The CaptureClickthrough functionality in Pega does not have built-in protection specifically designed to filter out bot clicks generated by spam filters or email scanners. When a link in an email is clicked whether by a real user or a spam filter Pega will register it as a click. This means false positives can occur, which may lead to inaccurate feedback loops in your engagement models. To reduce this, you can implement mitigation strategies such as adding a short delay before redirecting the user to the final page, checking user-agent headers to identify bots, or using JavaScript-based redirection where possible (note: JavaScript won’t work in all email clients). However, because email links are often scanned immediately after delivery, there’s currently no guaranteed way within Pega’s native features to distinguish human clicks from bot clicks. Additional filtering and click validation logic would need to be custom-built. Have you considered implementing timing or IP-based rules to reduce such false tracking?