WordPress database error: [Incorrect key file for table './blogs2/fzine_postmeta.MYI'; try to repair it]
UPDATE fzine_postmeta SET meta_value = '2782' WHERE meta_key = 'views' AND post_id = '85'

AdBrite Fraudulent Publishers: The Conclusion

AdBrite logoI’ve got a call from AdBrite’s office few hours ago, somebody in their office saw my posts on this blog :) . It’s nice to know that I can reach people through this blog. The manager explained to me that the history of my test campaign is available if I select a date range longer then the last 7 days, and it work indeed. They need to work a little bit on the interface of their website, right now it’s a bit confusing. For example, due the the lack of the grand totals, you have no idea that your campaign history is available if you don’t select a different date range, default is “last 7 days”. So, if you are wondering where is the history of your clicks, etc - select the date range to include all the periods.

That call was a nice personal touch; I guess, you may not have a call such that from Google about your troubles with AdWords :D As it turned out, they did reimburse the fraudulent clicked amount as the debit into my billing section.

As it turns out, in my theory, some publishers (who registered with AdBrite, but not affiliated with them), use false information to create an account, then run the scripts off-site (not off the same domain they registered), or maybe just generate clicks by a some sort of application emulating a browser. That happened to Google AdSense before, that’s why Google is so aggressive with it’s policies. There are methods to check that, and I hope AdBrite will implement more algorithms to check for similar situations.

If you like this post, dont miss the next one by subscribing to our Article News feed RSS feed!


Tags:

    Relevant articles:

    WordPress database error: [Can't create/write to file '/tmp/#sql_907_0.MYI' (Errcode: 30)]
    SELECT DISTINCT p.*, count(p2t.post_id) as cnt FROM fzine_post2tag p2t, fzine_tags t, fzine_posts p WHERE p2t.tag_id = t.tag_id AND p2t.post_id = p.ID AND (t.tag IN ('adbrite')) AND post_date_gmt < '2008-12-03 13:04:37' AND (post_type = 'post') AND p.ID != 85 GROUP BY p2t.post_id ORDER BY cnt DESC, post_date_gmt DESC

  • No Related Posts

This entry was posted on Thursday, July 12th, 2007 and is filed under General. 2,782 Views. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

2 Responses to “AdBrite Fraudulent Publishers: The Conclusion”

  1. AdBrite : MySpace Revenue : Internet Sucess | SEO Tips Adsense says:

    […] AdBrite Fraudulent Publishers: The Conclusion » Funds ZineZen of assets assets for ultimate grouping I’ve got a call from AdBrite’s duty some hours ago, somebody in their duty saw my posts on this blog […]

  2. Brian says:

    The crazy thing about adbrite is when they first hit the market they were really good. They had phone customer support and everything. Now they seem to becoming sketchy.

Leave a Reply

Close
E-mail It