Today we are excited to announce the launch Beta 1 of our Mobile Activeboard application. You need to have a gold ActiveBoard subscription to use the mobile site.

We are excited to support the following devices

• Apple iOS 3.2-5.0 beta
• Android 2.1-2.3:
• Android Honeycomb
• Windows Phone 7
• Blackberry 6.0
• Blackberry Playbook
• Palm WebOS (1.4-2.0)
• Palm WebOS 3.0
• Firebox Mobile (Beta)
• Opera Mobile 11.0
• Kindle 3

To launch the mobile site, simply visit your favourite ActiveBoard from any mobile browser.

You can always visit the Standard ActiveBoard site by clicking the "Full Site" Button from the Mobile ActiveBoard menu. This will load the standard site by default on your phone. (You can switch back to the mobile site by clicking on the "Mobile Site" link at the bottom of any ActiveBoard).

You can also test out the mobile interface from any browser by appending mobile.spark to the URL.

For example, if the URL to your forum is http://adbutler.activeboard.com, you can visit the mobile site by visiting http://adbutler.activeboard.com/mobile.spark

While the standard ActiveBoard interface currently has more features, mobile ActiveBoard is a great way to engage with users online from a mobile device -- our developers are continuing to add more features to the mobile version.

Tracking URL Outline

The following is a brief description of what tracking URLs are and how they work:

Every banner has it's own unique tracking URL, roughly as follows:
http://servedbyadbutler.com/redirect.spark?banID=XXXXX;CID=YYYYY;setID=ZZZZZ
To track clicks on banners, you'll need to enter the banner ID (banID), the campaign ID (CID), and the set ID (setID).

Each Flash and Raw HTML/Script banner has a bit of text and a link [click here] beneath the content of the ad that looks like the following:
"NOTE: For information and help tracking click-thrus, click here."

Clicking on that link will take you to a guide, pre-loaded with the appropriate tracking URL.
ex. Going to a banner in a campaign gives the following:
http://servedbyadbutler.com/redirect.spark?banID=519143350;CID=49714;setID=ZZZZZ

Note: At this time, a setID is required to properly track the clicks and where they came from. 

Banner Setup

1. Navigate to the advertiser whose banner you will be creating.
   
   Note: If no such advertiser exists, create them with -- remember that the email and password don't need to be exact, and can be changed later.
2. Create a campaign for the multi-clickable banner and the dummy banners, then navigate into the campaign.
3. Create the actual banner you intend to serve normally.
4. Create as many additional dummy banners as you require (for each link in addition to the main tracking link).
5. Navigate to each dummy banner you have created, copy the banner # of each one, and keep track of them. (make sure to mark which is which)
   
   While doing so, copy the campaign # from one of them, and also keep track of it.
6. Now navigate back to the actual banner to serve again, and modify it as follows:
   
   • For each tracking link needed, put <*tracking_link*>;banID=AAA;CID=BBB in, where AAA is the appropriate banner # from the previous step, and BBB is the campaign #.
7. Now you can assign the banner to as many sets as required.

Live Example

I like using colors in examples, as they're easy to distinguish so I'll do so here as well.

In this example, I have created 3 dummy banners and the actual banner I want to serve in a campaign. I then assigned them to two separate sets.

Below is the test HTML I used. Note the banID and CID fields of each tracking link correspond to the appropriate dummy banner.

<a href="<*tracking_link*>"> main </a>
<hr>
<a href="<*tracking_link*>;banID=519157250;CID=53123"> blue </a>
<hr>
<a href="<*tracking_link*>;banID=519157249;CID=53123"> red </a>
<hr>
<a href="<*tracking_link*>;banID=519157248;CID=53123"> green </a>
<hr>

To test them out, I clicked on a bunch of the links in each set from a test website which served only those two ads. As expected, all of the clicks and views were tracked properly for the campaign!

Additionally the statistics for the test sets I created were also recorded properly.

The advertiser's campaign statistics

The set specific statistics