BlogBank Blog

Here are some tips for inputting BlogBank codes onto your blog.

1. When you login to your account, you will see 3 ad codes – our advise is to install all three for maximum earnings. Whenever we have a campaign, we can automatically activate any of these codes to appear on your blog. If there is no campaign going on, we don’t display anything — we believe in only showing ads when we are paying you.

2. Remember that the BlogBank ads are based on CPM so traffic matters. Our suggestion is to place the ads on your blog’s sidebar for maximum CPM. You can also choose to place the code on single posts (i.e two on the sidebar, one on single post) — it’s really up to you.

3. Although we do not pay via clicks we DO track click through data. This data is used to present to clients which allows them to see which blogs are more effective for campaings. Please put your BlogBank ads in visible areas of your blog: on the upper 50% of your template or in prominent areas in your single post, but never below your template. We disable ads that are placed in the bottom of the page. We also disable ad codes that are “spammed” several times inside a blog.

We’ve been getting queries from some of our publishers/bloggers regarding the status of payments for campaigns concluded in the last few months that I think we should blog about it now. As of writing, we sadly are not yet done producing the data for all campaigns after May 2008.

First of all, please accept our apologies for being unable to send out your payments. We are very sad about this, too.

Primarily, we are having trouble with some possible taxation issues as we are effectively passing money from one company to another entity. BlogBank being a Filipino company, we have specific laws that categorize transactions we do as taxable, and this may include the payments we pass on to our bloggers. I wish I could explain things further but I’m seriously not qualified and just as clueless; as bloggers ourselves we would’ve wanted earnings be passed on to the publishers before taxes. This would’ve resulted in a similar setup to AdSense publishers where they (we) receive payments as is and settle our respective taxes on our own. Under Philippine laws though, we cannot apply a similar solution.

As a result of the legal barriers we have now, we are unable to compute the earnings for all blogs running BlogBank ads. Typically, earnings are computed by a simple formula that pegs traffic data against the total money set aside for the blogs of a given campaign. Unfortunately, the said “total money” is no longer a fixed value as it may be subject to certain taxes and similar things. We have been consulting with experts in this matter to make sure every action we take is fair and legal.

Be assured that we do have the capacity to pay and checks will be sent out as soon as we can. We are working hard to iron out the kinks to avoid possible legal troubles in the future. More updates on these matters soon.

This is a rather late update and some of you may have already found it, but there is a new tab in our publisher app that reports the earnings for your sites for previously concluded campaigns. I’m sure all our publishers have been waiting for this.

As of now, the tool reports earnings up to the end of May. We are still processing the stats for campaigns that conclude after that date and will make them available at the soonest time we can.

Go on, check your earnings now.

If you’ve recently used our publisher app and used the “forgot your password” functionality, the email with the password reset link probably would’ve reached you hours after the link is made stale. There was a configuration problem that caused outgoing mails from our server to get quarantined in the delivery queue, making it behave seem more like snail mail. The good news, it’s now solved! System–generated email should now be in your mailbox in a minute or so, and you can act on them promptly.

We will be rolling more changes to our publisher tool soon to give you more details on your site and campaigns and yes — we will be sending out a batch of checks in the next few days!

We’re very sorry.

As you may know, we have an upcoming BlogBank event for our publishers and fellow bloggers this coming week. And because we were very much aware that many of our publishers somehow wanted some stats and details regarding the previously concluded campaigns, we planned to get the numbers out before our event so we could issue checks on the day we all party.

Our online reports and notifications tools were not yet ready so we had to do it manually. The combination of doing things manually and rushing them at the same time was vulnerable to errors, and sadly it happened.

We’ve heard from some of our publishers that they received the wrong reports listing the earnings of sites they do not actually own. We understand the various concerns regarding this, more importantly the privacy side of it. We deeply apologize and we assure you that this will not happen again. We will be re–sending the reports correctly as soon as everything is in place.

All statistical and financial data are in proper order, the problem basically resulted from the reports being sent to the wrong publishers — a very costly one at that.

We understand that these are inexcusable errors and we sincerely apologize to our community. As bloggers, we also understand how you feel about this situation. Please bear with us as we strive to be of better service to you. We are committed to providing better ways for you to get the most out of your blog, and will continue to do that for our local blogging community.

Feel free to leave comments if you have questions you’d like addressed, or you can personally approach Jayvee or Markku for any queries you may have.

Hey there folks. Blog Bank ads, if you may have noticed are slowly migrating from 250 x 150 to 180 x 150 to be more sidebar friendly. We know you’ve been asking for this for the longest time and so we’re slowly doing this. Two of our three campaigns are currently running 180 x 150 ads so if you’re in the mood to do some sidebar relocating with us, then that’s very much appreciated.

Have a great weekend!

Hi folks. There have been inquiries about accessing your account’s payment earnings and stats. We’re very much aware about this and we’re in the process of rolling out a tool which you can access through your dashboard in the next two weeks. One of the reasons why this is taking time is because we’re also figuring out how taxation should work for publishers (should publishers be taxed or should they file for their own taxes?). It’s a little tricky, but we’re getting there.

Also, payments for last month’s campaign are also going to be happening in the next few days. Stay tuned for more updates!

One of the top support requests from our publishers is the issue of using our BlogBank ad code on Blogger–published or Blogspot–hosted sites. Since Day 1, our code does not work in the latest version of Blogger’s publisher tools. But thanks to some creative hacking of Maruel, one of our publishers, we can now use BlogBank on Blogspot!

Read the rest of this entry »

First, the good news. After we opened signups to the public, we managed to more than double our daily network traffic! That data was around two days ago — I wouldn’t be surprised if we now have surpassed three times our pre–launch traffic figure. This surge should help us grow by attracting more advertisers, which can only be good for everyone.

Now the bad news. New signups are temporarily disabled. The overwhelming response of the local blogging community has produced dozens of new publishers a day. Though it is a good thing, it affects our pre–sold inventory of impressions from our current publishers.

We apologize to everyone who’s been planning to signup; we’ll be back in no time. Consider this our holy week break as we plan to be back just as brick and mortar shops reopen next week, give or take a day or two.

Until then!

We’re currently fixing the ad codes for Blogspot hosted blogs. For those of you running or have signed up under a blogspot account, we apologize for the delay in the implementation. Rest assured we’re working on it and will update you very soon.