Add Clixtell as a native data source connector#1845

Hi Windsor.ai team,

I would like to request adding Clixtell as a native data source connector in Windsor.ai.

Clixtell is a click fraud protection, PPC monitoring, call tracking, and visitor/session monitoring platform used by advertisers to protect Google Ads and Microsoft/Bing Ads budgets. It helps detect suspicious and fraudulent ad clicks, monitor PPC traffic, block fraudulent IPs/devices, track phone calls, and analyze user sessions.

This integration would be very valuable for advertisers and agencies who want to combine Clixtell data with Google Ads, Google Analytics 4, Google Search Console, CRM, call tracking, and SEO data inside Windsor.ai dashboards, spreadsheets, BigQuery, Looker Studio, and other BI destinations.

Suggested data fields and reports to support:

1. Click fraud protection data
2. total ad clicks
3. suspicious clicks
4. fraudulent clicks
5. blocked clicks
6. blocked IPs
7. blocked devices
8. repeated clicks
9. click timestamp
10. source / medium / campaign
11. Google Ads account
12. campaign name
13. ad group name
14. keyword
15. match type
16. landing page URL
17. IP address
18. country
19. city
20. device
21. browser
22. operating system
23. fraud rule triggered
24. fraud reason
25. estimated wasted spend

26. estimated saved budget

27. IP blocking and protection data

28. blocked IP list
29. IP block reason
30. block date
31. unblock date
32. campaign-level IP exclusions
33. number of times each IP clicked

34. number of blocked attempts after exclusion

35. Call tracking data

36. total calls
37. answered calls
38. missed calls
39. call duration
40. call source
41. campaign
42. keyword
43. caller number, if available and privacy-compliant
44. call recording URL, if available and privacy-compliant
45. first-time caller vs returning caller

46. call conversion status

47. Visitor and session monitoring data

48. session ID
49. traffic source
50. landing page
51. pages viewed
52. session duration
53. device
54. browser
55. location
56. suspicious behavior flags

57. session recording URL, if available

58. Account and summary metrics

59. protected ad spend
60. fraudulent click rate
61. blocked click rate
62. saved budget estimate
63. trend over time
64. campaign-level fraud risk
65. keyword-level fraud risk
66. device-level fraud risk
67. geo-level fraud risk

Important use cases:

• Build a unified paid media protection dashboard.
• Compare Google Ads spend, conversions, and invalid/fraudulent clicks.
• Identify campaigns and keywords with high fraud risk.
• Report monthly wasted spend and saved budget to clients.
• Combine Clixtell data with Google Ads, GA4, GSC, CRM, and call tracking data.
• Monitor call quality and click quality in one reporting layer.

Ideally, the connector should support scheduled data refreshes and allow users to pull Clixtell data by account, campaign, date range, traffic source, device, country, and fraud status.

This would be especially useful for service businesses and agencies that rely heavily on Google Ads calls and lead generation, where click fraud and low-quality paid traffic directly affect ROI.

Thank you.