FrequentlyAsked Question / Exact Problem
“The ‘Clicks’ count in campaign analytics is much higher than the number of customers who
actually opened the message.”
“Short link click count seems to be doubling — reporting more clicks than messages sent.”
Affected Tenant / Context
Pothys (reported as recurring), but can affect any tenant using short links in SMS campaigns.
Root Cause
Google’s Safe Browsing / link-scanning service automatically scans URLs received in SMS
messages. The scanner uses a browser-like UserAgent ( Mozilla/5.0 ), making it
indistinguishable from a real click. Requests were coming from Google infrastructure IPs
( 64.233.x.x , 74.125.x.x ). CASA’s trackClick() function was triggering for every scan,
inflating click counts
Common Debugging Steps (For CS Team)
1. If click count exceeds delivered count, or open rate seems suspiciously high (>100%), flag for investigation.
2. Note the campaign ID and the ratio of clicks to delivered.
3. This is a known recurring issue — tag @Kumaresan for context, and dev team will verify IP logs.
️Fix Made & Developer Conclusion
Ashwitha deployed a fix to filter out bot/crawler clicks:
- IP range check (Google infra IPs blocked from trackClick)
- UserAgent validation (known crawler/headless browser UAs filtered)
- All events go through the filter before being published to Kafka
Exact Dev to Reach Out To
Ashwitha — Bot click filter fix
Dineshr — Campaign analytics, click tracking pipeline