Hiding traffic sources from Big G

[AlexAkimbo]

So, Google Chrome Extensions are so hot at the moment for me. For a year or so to be honest. My MB team is buying lots of pop traffic and drive it to chrome web store. Lately, i am facing issues like extension drops from Chrome webstore for "deceptive marketing tactics/installations".

General (simplified) campaign flow is:

1. Pop traffic sources
2. Traffic cleaning (per geo, per os, bot/vpn/proxy removal, etc.) + cloaking
3. Voluum
4. Extension's website download page (+ complete clean up of entire redirect chain before this + referral removal + headers manipulation + etc.)
5. Chrome webstore

Do you have any recommendations or ideas on how to hide complete campaign from Big G so i can avoid further extension drops?

 

[bartosimpsonio]

There really is no formula

G's entire business is built around tracking people around and trying to identify everyone for their ad-fraud detection purposes. Or whatever other purposes.

Avoiding any of that is probably a black art, so no one's gonna be able to give you a cookbook solution

First thing you oughta do is retrace the entire path and try to find out what leaked where

 

[AlexAkimbo]

There really is no formula

G's entire business is built around tracking people around and trying to identify everyone for their ad-fraud detection purposes. Or whatever other purposes.

Avoiding any of that is probably a black art, so no one's gonna be able to give you a cookbook solution

First thing you oughta do is retrace the entire path and try to find out what leaked where

Thanks mate for the answer. But (there is always some but), the most fkd up thing is that there is no option to track entire redirect chain because I sanitise everything during redirection so each visit is like brand new direct one. Also no G’s tracking enabled on redirect domains (those are churn and burn domains buried into the ever changing smart link).

Do you have any idea what else I can do on server/http protocol to prevent possible crawling or backtracking from chrome’s web store?

 

[bartosimpsonio]

Thanks mate for the answer. But (there is always some but), the most fkd up thing is that there is no option to track entire redirect chain because I sanitise everything during redirection so each visit is like brand new direct one. Also no G’s tracking enabled on redirect domains (those are churn and burn domains buried into the ever changing smart link).

Do you have any idea what else I can do on server/http protocol to prevent possible crawling or backtracking from chrome’s web store?

They pay thousands of human reviewers to do this. So basically you'd be up against residential IPs which are identical to your potential customer IPs. Unless you find a way to detect these reviewer IPs there really is nothing you can do except count on luck