[nana_gb]

Browser fingerprinting is generally frowned upon by many major browser vendors and ad blockers.

It also goes against user’s rights for privacy and tracking prevention that they have control over.

I wouldn’t be surprised if google ads classifies fingerprinting as malicious.

Remove it from the bundle and try again.

Additionally, the ability to intercept form submissions can also be seen as malicious.

Especially if it’s a 3rd party script doing the interception and making AJAX calls to another domain.

This is basically what malicious scripts do.

HTH I have been building adtech for Google Ads etc for 15+ years. Happy to talk more if needed. But I’m pretty sure the two changes above will fix it.

[msf83]

Do you know if I fix it, how to trigger a rescan of the offending URL, not the advertisers' page? I'm trying to figure out what the lifecycle and stickiness of a flagged URL is.

Example: www.advertiser.com contains -> a.startup.com/script.js

I'm considering this strategy: * drop fingerprinting and form submission like you suggest * resubmit advertiser.com's ads for a rescan, but if theyve got startup.com's url flagged, will they rescan that URL too? * problem: how do I know how to long wait to see if it worked?

My next move would be: * setting up a new subdomain, new filename (like b.startup.com/newscript.js)

Thoughts?

[nana_gb]

The last time this happened with a client, fixing the script was good enough to resolve the issue with Google after resubmission.

But that may have changed.

[msf83]

Really appreciate your insight thank you this helps