Showing posts with label Google AdSense. Show all posts
Showing posts with label Google AdSense. Show all posts

24 May 2014

Google Accused Of Stealing Money From Publishers



By Chris Crum at WebProNews:


Someone claiming to be a former Google employee has accused the company of stealing money from AdSense publishers.

In a “leak” on Pastebin, this person says, “To sum it up for everyone, I took part in what I (and many others) would consider theft of money from the publishers by Google, and from direct orders of management. There were many AdSense employees involved, and it spanned many years, and I hear it still is happening today except on a much wider scale. No one on the outside knows it, if they did, the FBI and possibly IRS would immediately launch an investigation, because what they are doing is so inherently illegal and they are flying completely under the radar.”

It’s a pretty lengthy and detailed explanation. Here’s a portion:

In the first quarter of 2009 there was a “sit-down” from the AdSense division higher ups to talk about new emerging issues and the role we (the employees in the AdSense division needed to play. It was a very long meeting, and it was very detailed and intense. What it boiled down to was that Google had suffered some very serious losses in the financial department several months earlier. They kept saying how we “needed to tighten the belts” and they didn’t want it to come from Google employees pockets. So they were going to (in their words) “carry out extreme quality control on AdSense publishers”. When one of my fellow co-workers asked what they meant by that. Their response was that AdSense itself hands out too many checks each month to publishers, and that the checks were too large and that needed to end right away. Many of the employees were not pleased about this (like myself). But they were successful in scaring the rest into thinking it would be their jobs and their money that would be on the line if they didn’t participate. The meeting left many confused as to how this was going to happen.

What did they mean by extreme quality control? A few other smaller meetings occur with certain key people in the AdSense division that furthered the idea and procedure they planned on implementing. There were lots of rumors and quiet talking amongst the employees, there was lots of speculations, some came true and some didn’t. But the word was that they were planning to cut off a large portion of publisher’s payments.

After that point there was a running gag amongst fellow co-workers where we would walk by each other and whisper “Don’t be evil, pft!” and roll our eyes.

What happened afterwards became much worse. Their “quality control” came into full effect. Managers pushed for wide scale account bans, and the first big batch of bans happened in March of 2009. The main reason, the publishers made too much money. But something quite devious happened. We were told to begin banning accounts that were close to their payout period (which is why account bans never occur immediately after a payout). The purpose was to get that money owed to publishers back to Google AdSense, while having already served up the ads to the public.

This way the advertiser’s couldn’t claim we did not do our part in delivering their ads and ask for money back. So in a sense, we had thousands upon thousands of publishers deliver ads we knew they were never going to get paid for.

Google reaped both sides of the coin, got money from the advertisers, used the publishers, and didn’t have to pay them a single penny. We were told to go and look into the publishers accounts, and if any publisher had accumulated earnings exceeding $5000 and was near a payout or in the process of a payout, we were to ban the account right away and reverse the earnings back. They kept saying it was needed for the company, and that most of these publishers were ripping Google off anyways, and that their gravy train needed to end. Many employees were not happy about this. A few resigned over it. I did not. I stayed because I had a family to support, and secondly I wanted to see how far they would go.

From 2009 to 2012 there were many more big batches of bans. The biggest of all the banning sessions occurred in April of 2012. The AdSense division had enormous pressure from the company to make up for financial losses, and for Google’s lack of reaching certain internal financial goals for the quarter prior. So the push was on. The employees felt really uneasy about the whole thing, but we were threatened with job losses if we didn’t enforce the company’s wishes. Those who voiced concerned or issue were basically ridiculed with “not having the company’s best interest in mind” and not being “team players”. Morale in the division was at an all-time low. The mood of the whole place changed quite rapidly. It no
longer was a fun place to work.

The bans of April 2012 came fast and furious. Absolutely none of them were investigated, nor were they justified in any way. We were told to get rid of as many of the accounts with the largest checks/payouts/earnings waiting to happen. No reason, just do it, and don’t question it. It was heart wrenching seeing all that money people had earned all get stolen from them. And that’s what I saw it as, it was a robbery of the AdSense publishers. Many launched appeals, complaints, but it was futile because absolutely no one actually took the time to review the appeals or complaints. Most were simply erased without even being opened, the rest were deposited into the database, never to be touched again.

Several publishers launched legal actions which were settled, but Google had come up with a new policy to deal with situations such as that because it was perceived as a serious problem to be avoided. So they came up with a new policy.

There’s much more to the explanation. Read the whole thing here.

Obviously Google denies the whole thing. Google has given several news outlets the following statement:

This description of our AdSense policy enforcement process is a complete fiction. The color-coding and ‘extreme quality control’ programs the author describes don’t exist.

Our teams and automated systems work around the clock to stop bad actors and protect our publishers, advertisers and users.

Google’s Matt Cutts has been defending the company on Hacker News. He wrote:

Everything about this post strikes me as a conspiracy-laden fake, from the typos to wrong terminology to untrue policies to the lack of specific names of people. I passed this pastebin to the ads side to confirm for sure, but I would treat this as completely untrue.

Added: Yup, I’m hearing back from multiple people on the ads side that this is pretty much untrue from start to finish.

Also notice that the “rmujica” account that submitted this item has never submitted any other story or written any other comment on Hacker News before today.

In another comment, Cutts added:

I’ve worked with the people this post talks about since 2005. Even though I’m the head of the webspam team, I’m familiar with how AdSense deals with fraud.

For example, I often see disgruntled publishers complaining on the web, and from time to time I’ve followed up on specific blog posts to get the other side of the story. In addition, the group that manually fights webspam at Google is a sibling organization to the group that fights adspam.

Finally, I passed these claims directly to the ads side and so far I’ve gotten three (now four) different “this is fake” responses from people I trust and have worked with in different capacities for years, including an engineer that I worked with in search quality who later went to work in ads.

Someone commenting a Valleywag article said, “I never participated in adsense (fuck google) but I was part of a big online group who used it hard. Thousands were banned without reason in a single sweep near their payout date. It matches this description perfectly. I always suspected foul play and now this describes exactly what happened around that exactly time. Coincidence. I don’t think so…And what a group of small people could do against mighty Google?”

This person continued in another comment, “I didn’t participate in it as I was just a witness to the uproar. But what people were saying at the time matches what this guy is saying. It was a forum called WarriorForum, dedicated to Internet Marketing. I was planning on selling apps for them but nothing came out of it but it was around the time the ban fest happened.”

It’s unlikely that the “leaked” story will be proven, unless more of the mentioned employees come forward with real identities. At the same time, it could be difficult for Google to prove its case beyond a “you’re going to have to take our word for it” kind of scenario.

AdSense is said to account for roughly a third of Google’s revenue.

What do you think? Conspiracy theory or not?

13 Apr 2014

Google Starts Blocking Access to Paid Search Keyword Data



By Jennifer Slegg at Search Engine Watch: 


Many of us have been concerned about the possibility of Google expanding "(not provided)" to also encompass paid search. Until now, AdWords advertisers have gotten full access to keyword data, whether it's through Google itself or through one of the third-party tools using the API for this data.

When Google made the move to secure search, and effectively turned off the ability for webmasters to know exactly which keywords were driving organic traffic to their websites from Google, the next obvious question was when would this hit AdWords advertisers, and how Google would handle it.

That answer came today. In a blog post, Google said the following:

Today, we are extending our efforts to keep search secure by removing the query from the referer on ad clicks originating from SSL searches on Google.com.

Advertisers will continue to have access to useful data to optimize and improve their campaigns and landing pages. For example, you can access detailed information in the AdWords search terms report and the Google Webmaster Tools Search Queries report.


Some felt it was double standard, where AdWords got to keep their keywords while organic did not. However, while the loss of this data would be felt – and has largely been expected – the change isn't as doomsday as some are making it out to be. The impact with the loss of organic keyword data was significantly greater.

Advertisers will continue to have access to keyword data within the Google AdWords dashboard – it isn't a case where advertisers would be flying blind without any data at all. Advertisers who don't use a third party management tool likely won't notice a difference, aside from potentially needing to utilize AdWords tags if they aren't already.

At SMX West last month, Amit Singhal from Google hinted in his keynote that we would be seeing some changes to paid versus organic when it came to "(not provided)", although he was light on details.

Over a period of time, Sridhar [Ramaswamy], the Head of Ads, my friend, and I we have been looking at this issue. And we're also hearing from our users that they would want their searches to be secure. A lot has happened in the world, as you all know. And keeping user's searches secure is really important to the users. We really like the way things have gone on the organic side of search, because we are hearing and responding to what our users want. We really like where we are at.

Sridhar and I are looking at our world, and finding the right solution for our users who want their searches secure and are advertisers, so I have nothing to announce right now, but in the coming weeks and months as Sridhar and I find the right solution, expect something to come out of us.


Discussion about this change began earlier this week when A.J. Ghergich published a blog post detailing that AdWords will no longer be supplying third parties with paid search query data.

Because of the way Google AdWords does their tracking, they can still easily remove the referral keyword string from the referring AdWords URL, to provide secure search in regards to preventing those keywords from showing up in the website logs. But Google still has all that data within the AdWords dashboard, and can provide that information to advertisers.

Regardless of how they provide the keyword data within the Google AdWords dashboard, we won't see a day where advertisers get no keywords whatsoever, because the price would drop down as advertisers lose confidence in the transparency of what they're bidding on and what they're getting traffic from.

Ghergich reported that an anonymous source provided him with the information regarding the change to paid search query data. The details from the memo include:

- Google will cease supplying 3rd parties with paid search query data
- Reports within AdWords will remain unaffected
- This will also have an affect on website analytics packages but we've not yet heard about anything with Google Analytics
- Services that use this query data may have no way to access it anymore

Could they turn off access within Google Analytics? It's hard to say because some third parties use Google Analytics data, if they are truly trying to tighten down on any of that data for privacy concerns.

There is the possibility that they could be changing the API where Google would charge for paid API access, under the guise of "keeping it secure", or simply tightening down the number of companies that have access to the data currently.

What other reasons could Google have besides privacy concerns, which was the reason for the organic "(not provided)" change? According to Ghergich, his source feels that "another possible motive for the change by Google is that less data leads to less accurate AdWords decisions which increases ad spend."

Prior to Google making the change official, Search Engine Watch reached out to several companies who are currently using this paid search query data from Google AdWords, to get their take, and their thoughts if Google was to make a change to their current third party access to paid search query data.


Marc Poirier, Acquisio co-founder & EVP, business development told us:

This information is critical for search marketers, it helps them see how search queries map to keywords and to make the necessary adjustments such as adding negatives or exact match keywords to help continuously improve performance. Taking this away will seriously impede the discovery process and will promote the massive proliferation of exact match keywords and the accelerated death of broad match and even phrase match keywords. In other words, if this is true, it will likely have a dramatic impact on the number of keywords needed to find success in paid search.

Jon Henshaw, Raven Tools co-founder, told us:

We keep a close watch on the AdWords API to make sure that Raven complies with its terms of service, which Google takes very seriously.

We have not heard from Google about changes to their AdWords API related to search query data. But I really can't speculate or speak for any other third party provider about this.

In our case, online marketing agencies use Raven to manage AdWords campaigns and report campaign performance to their clients. The AdWords data that our customers value most in Raven is related to that, not whatever paid search query data that they may use for research. If this specific rumor turns out to be true, any impact on Raven's customers would be minimal.

All that said, our software evolves as the industry does.


Matt Ackley, Marin Software CMO, also told Search Engine Watch that they won't be greatly affected by the change.

We are aware of the reports circulating that Google may cease to provide search query data to third parties. The bulk of Marin Software's services involve keyword data. While search query data is related to keyword data the two are distinct. As such, bidding, reporting, tracking, and campaign management - the features and capabilities that set Marin Software apart as a powerful digital marketing platform - would be unaffected should Google no longer provide search query data to its paid search API partners.



15 Dec 2013

Google Launches Four New AdSense Features

Google announced some new features for its responsive ad units in AdSense, as well as the addition of a multi-screen optimization score for the publisher scorecard.

For responsive ads, Google has added ad refresh fro screen orientation changes.

Product manager Nick Radicevic explains, “If your responsive page changes its layout following a screen orientation change (e.g., when a tablet or phone goes from portrait to landscape), we’ll request and load a new ad to fit the new page layout.”

They’ve added smart sizing based on available space, so that ad code will automatically adapt all newly created responsive ad units to fit the page layout. Existing ads that have specified width/height will remain the same.

Google has also added reporting by ad size served.

On the multi-screen optimization score, Radicevic says, “To help you understand how well your site is optimized for the many screen sizes of your users, we’re introducing a new multi-screen category in our publisher scorecard. For example, if users need to zoom and/or scroll often, this may negatively impact their experience. Your score in the multi-screen category will measure what percentage of your pages are multi-screen optimized and compare this percentage to that of other AdSense publishers. Please note that you may not see this category in your scorecard if you have a low percentage of mobile traffic on your site.”

The score will be visible in the scorecard on the AdSense homepage.

Earlier this week, Google announced the launch of custom ad sizes.





Read the full story >>