Hey everyone. When I installed clay script for web intent on our website, Google ads marked it as compromised site and disapproved all our ads. It was only deemed clean when I removed the script. Has any other person had this problem? Secondly I'm trying to use GTM instead. But it's not receiving or activating
I understand the frustration with Google Ads flagging your site. While our sources don't specifically address Google Ads compatibility issues, this could be related to how ad blockers and security systems interpret tracking scripts.
For GTM setup, here's what might help:
In GTM, create a new tag called "Clay Visitor Tracking"
Set tag type to "Custom HTML"
Paste your Clay JavaScript snippet
Add trigger for "All Pages"
Save and publish changes [1]
Note that we actually recommend direct installation over GTM since ad blockers often disable Tag Manager, which might explain why it's not activating.
Before we dig deeper, try using Sculptor (top-right corner of Clay) to help troubleshoot your GTM setup - it's free and can guide you through the process. Let me know if that helps or if you're still having issues!
Was that helpful?
What is the JavaScript snippet
The JavaScript snippet is the tracking code you get when setting up website tracking in Clay. To find it:
Click your workspace name (bottom left) → Settings → Integrations
Find "Website Tracking" and click "Add Connection"
Copy the JavaScript snippet provided [1]
You can also get it by going to Settings → Web intent → Add connection, then copying the code under "Install tracking snippet" [2]
The snippet is unique to your workspace and contains your tracking configuration.
Did that answer your question?
I have actually done that. But I'm not receiving any new visits on the site
A few things to check:
Timing: Visitor data can be delayed up to 30 minutes, so it's not real-time. [1]
Installation: Make sure the snippet is on all pages of your site, ideally before the closing </body> tag.
GTM vs Direct: Since you mentioned GTM isn't working, try installing the snippet directly on your site instead - ad blockers often disable Tag Manager which could explain the issue.
Try using Sculptor (top-right corner) to help troubleshoot your setup - it's free and can guide you through the process. Let me know if that helps!
Is that what you were looking for?
Infact the GTM is firing but not receiving visitor details. Like I mentioned Google ads is identifying it as a malicious script
Got it - so GTM is firing the script but you're not seeing visitor data come through, and Google Ads is flagging it as malicious.
For the Google Ads issue, this might be related to how security systems interpret tracking scripts. Since you mentioned it was only resolved when you removed the script entirely, this suggests a compatibility issue with Google's security detection.
For the visitor data not appearing: even when GTM fires correctly, visitor data can take up to 30 minutes to show up in Clay - it's not real-time. [1]
Since you're having both issues with GTM, I'd recommend trying direct installation instead. We actually recommend installing the snippet directly on your site rather than through GTM because ad blockers often disable Tag Manager.
Try using Sculptor (top-right corner) to help troubleshoot your setup - it can guide you through the direct installation process. Let me know if that helps resolve both the Google Ads flagging and the visitor tracking issues.
Did that answer your question?
If you still need help resolving the Google Ads flagging and visitor tracking issues, I’m here to assist. Would you like to provide more details about your setup or any specific errors you’re encountering?
I need it sorted but we seem to be going in circles
I understand this feels repetitive and frustrating. Would you like me to connect you with a human agent? Or if you provide more details about your setup, we can try a different approach together.
I’m sorry this has been frustrating, and I’m here to help if you still need assistance with your setup. Would you like to share more details about your current configuration or any specific errors you’re seeing so we can explore other solutions?
