coastboy23
commented
6 years ago Disregard some of the solutions discussed above. Spoke on phone directly with seemingly knowledgable Google rep and this can be resolved simply by moving be.brave.com pages to brave.io. Please proceed with this when you have an opportunity.
Google claims our installer download pages, e.g. http://bebrave.mystagingwebsite.com/gs-us-branded-bra712/violate their policies: https://support.google.com/adspolicy/answer/6020954?hl=en&ref_topic=1626336We are using trackable installers from our publisher referral program on the download buttons of our campaign landing pages. Right now there are 20 being used. But we will want to expand this eventually to possibly a couple of hundred as we expand our search marketing to more countries.
They have asked us to move the installer to a non-Brave.com domain such as brave-downloads.com. These are desktop download only campaigns, so we don't have to worry about redirect to mobile app stores. But we do need these installers to be trackable via our referral code system so we can monitor effectiveness of our campaigns.
Here are more comments and suggestions from the Google Ads team email thread to help resolve:Or will adding a redirect to button not work and we actually need to host the executable on a non brave.com domain?" "The latter - the link can not be accessible from the brave.com root domain or any of its subdomains. A crawler will check brave.com and all of its dependencies [{any number of dependencies here}.brave.com)]. Links out of the domain are also checked, so if you have a link that goes to 'brave-download.com', for example, which also has the forced executable this will not work.As far as I see it, though, the strategy is to force download and not to provide further information/content on Brave, so the strategy will remain intact if a new domain is created purely for the purpose of facilitating the referral links that are sitting on pubs. This is fine and I understand the strategy in the browser space.In sum, create a new root domain, e.g. 'brave-download.com' as above, and host the executable there and make it the new landing page for the publisher referrals, and be sure not to link to this root domain from the 'brave.com' root.There may be other options so I still recommend sharing the policy page with your browser development teams and seeing if they have other ideas. I would be happy to hash them out over the phone to ensure they are compliant before implementing.
.would it work okay if we created the root domain brave-download.com for our landing pages, and this was the URL we both linked to and exposed in our Google Ads campaigns, but still redirected to the executable hosted on https://laptop-updates.brave.com/download/BRA491. Or is this domain now permanently flagged in your system or associated with our account?
If the brave-download.com root domain redirects or further links to a domain that has the executable it would eventually get disapproved once the crawler catches the download. Why don't you keep the Google Ads routing to the same brave.com root, and set up brave-download.com solely for the pub referral ads/links? |