You might have noticed that we added a share column to most of the reports with our version 2.5 update. What is that all about? In the online advertising industry, share of voice is used to represent the relative portion of ad inventory available to a single advertiser within a defined market over a specified time period. So, basically, the share column shows you what percentage of impressions each of your advertisers received during a period of time.

Example Report

We have gone a step further by making share of voice available for more than just advertiser reports. For example, what if you wanted to know what percentage of impressions were from Firefox users today? Sure, you could always get out your calculator and figure it out, but now you don’t have to!

Right away you can see that about 36.63% of visitors today were using Firefox without even thinking about reaching for your calculator. You’re welcome! Remember, the share column is available for almost all other report types as well (such as geography or custom fields), so you can now very easily compare impression distribution between many different elements and dimensions.

JSON (JavaScript Object Notation) is a lightweight data-interchange format. It is easy for humans to read and write. It is easy for machines to parse and generate. Based on a subset of the JavaScript Programming Language, JSON is a text format that is completely language independent but uses conventions that are familiar to programmers of the C-family of languages, including C, C++, C#, Java, JavaScript, Perl, Python, and many others. These properties make JSON an ideal data-interchange language.

JSON vs XML

You might already be using our API with XML so why might you want to switch to JSON? In most cases there really is no reason to switch aside from personal preferences. Many people find XML very verbose and clumsy to work with while JSON is very compact and easier to read and write. If you are more comfortable and productive with XML, then you should use XML. Otherwise you can choose to use JSON instead if you feel like it is a better fit for you.

Comparison

So, you might be wondering, just how much more compact and readable is JSON compared to XML? Here’s an example of the data returned when retrieving the information for a zone in both JSON and XML.

JSON

{
  "id": 1,
  "name": "Top of Page / 728x90",
  "group": 2,
  "type": 1,
  "size": 19,
  "targeting": [
    4,
    8
  ],
  "status": true,
  "recycle": false,
  "notes": "",
  "campaigns": [
    {
      "id": 3,
      "default": false,
      "chain": 0,
      "priority": 1,
      "status": true
    },
    {
      "id": 4,
      "default": false,
      "chain": 0,
      "priority": 1,
      "status": true
    }
  ],
  "publishers": [
    1,
    2
  ]
}

XML

<zone id="1" name="Top of Page / 728x90" group="2" type="1" size="19" targeting="000010001" status="true" recycle="false">
  <notes/>
  <campaigns>
    <campaign id="3" default="false" chain="0" priority="1" status="true"/>
    <campaign id="4" default="false" chain="0" priority="1" status="true"/>
  </campaigns>
  <publishers>
    <publisher id="1"/>
    <publisher id="2"/>
  </publishers>
</zone>

As you can see the JSON is actually slightly larger than the JSON in this case. This is not typical, however, it is pretty clear that the JSON is much easier to read and understand. Why does that matter? You are writing programs to read the JSON right? Well, if you find yourself tracing HTTP requests to view the data going back and forth between the API, trust me, I can tell you that JSON is much easier on the eyes! It is also much nicer for those folks that like to dig and explore the API without reading the documentation

The Verdict

Having the option to choose between using JSON and XML is a good thing. It gives you the flexibility to pick the right tool for the job. Interested in learning more about JSON? Head on over the official JSON web site at http://www.json.org/

We are pleased to announce that AdvertPro version 2.5 has been released!

Read on to find out more about new features and improvements. To obtain the update: visit our download site if you plan to install it yourself or request an update installation if you prefer to have us install it for you. Remember, you’ll need to have an up to date support contract to receive this update, so renew today!

Ad Server

Mobile Targeting We have added all of the most popular mobile operating systems and web browsers to our software targeting and reporting so if you’ve been waiting to start advertising apps to Android and iOS visitors on your web sites the wait is now over!

Retargeting Now you can retarget visitors who have previously viewed pages that have been tagged with segment pixels codes. For example, you might create segments for your advertisers home page, landing page, shopping cart and order confirmation pages. This creates a lot of exciting targeting possibilities, such as being able to target visitors that abandoned their shopping cart for a premium CPM.

Keyword Targeting Now you can block or target campaigns when no keywords have been passed to the ad server by entering the special keyword {null} as a blocked or targeted keyword value, which can be useful when passing %%KEYWORDS%% values to third-party ad servers and you want to make sure their ads are only shown when you actually have keywords to pass.

HTML5 The ad server now fully supports the new HTML5 doctype and tags.

Windows 8 We have added support for targeting and reporting of Windows 8 users.

API

JSON Not a big fan of XML? You will be happy to hear that our API can now output data in JSON format. To get JSON output instead of XML (which is still the default), simply add an &output=json parameter to your API requests. Our API documentation has also been updated with JSON examples.

Code Wizard

Action Code The action tracking pixel code output by the code wizard is now using an asynchronous JavaScript call to load the pixel, which means the pixel is longer visibly displayed in the page and it also should be able to resolve a greater percentage of referrers.

Deployment

MySQL Slave It is now possible to increase salability and reliability by configuring a replicated MySQL slave database server. In fact you can configure a pool of slaves and they will be load-balanced automatically! Due to slaves being read-only their use is limited to loading user session data and generating statistics reports.

With the upcoming clustering support it will be very important to have a few slaves for loading user session data if you use frequency capping or post view tracking. Customers with huge statistics databases know that generating reports can sometimes delay the real-time statistics batch updates, which increases the risk of data loss in the event of a power failure or system crash. By offloading report generation to the slave(s) this risk is completely eliminated because it removes all of the potential for read/write contention from the master.

JDK 7 & Tomcat 7 Deployment with JDK 7 (1.7.0) and Tomcat 7 (7.0.x) is now officially supported.

Performance

Multiple Chains Performance has been improved with zones containing many levels of chains. The ad server now walks down the campaign list in descending order by chain. This allows it to skip scanning campaigns in lower chains once campaigns in higher chains have already been found!

Reports

User Interface

Questions?

Contextual targeting enables you to more effectively target campaigns to relevant pages by matching keywords and phrases within the full text content of those pages. Advertisers are willing to spend more money for their ads to be placed on pages that contain relevant keywords or phrases. Why allow content advertising networks to collect the lions share of that money? With contextual targeting, you will be able to sell those advertisers directly and increase profits by completely cutting out the middle man.

You can also stretch your inventory to increase profits even further with contextual targeting. Say that you have an advertiser who buys 250,000 impressions every month at $10.00 CPM and you deliver those impressions run of site. Maybe their ads aren’t quite relevant to every page on your site though? Why not sell them 100,000 impressions only on relevant pages at $25.00 CPM instead? You still make the same amount of money ($2,500/month), your advertiser will be happier because their CTR will appear higher from having fewer impressions and you have 150,000 extra impressions that can be sold to another advertiser for an increased profit of $1,500/month.

How Contextual Targeting Works

1. Generate a zone code with the Code Wizard and check the Contextual option to enable indexing of pages where you will place the zone.
2. Place the generated zone code in your page(s). Secure pages are supported too!
3. The zone code triggers the web crawler component of the contextual targeting module to create a full text index of those pages as they are visited. This on-demand process happens in less than half a second the first time a new page is discovered. The ad server will then cache the page index for 1-24 hours (configurable) so there is very little impact on the performance of your site and the loading speed of your ads.
4. Campaigns can then be targeted to keywords and phrases in your pages. Exact and fuzzy matches of keywords are supported. Boolean operators (+/-) are also supported to require combinations of words, so you can actually require multiple keywords or phrases to be present in a page together. You can even require certain keywords or phrases to occur a minimum number of times to guarantee greater contextual relevancy.
5. The most relevant keywords from your pages can later be reviewed by generating a keyword report, which is a great sales tool that helps you estimate how many impressions certain keywords generate on average.

Where Contextual Targeting Excels

Lets say that you operate a web site that covers home theater equipment. The big attraction to your web site is a forum where enthusiasts can discuss all of the latest home theater audio and video gear. Over the years the forum grows to be home to several hundred thousands posts. How could you possibly target ads to all of those post pages? You use keyword targeting! The contextual targeting module uses a web crawler to full text index your forum post pages on-demand and it caches pages for a short time (4 hours by default) so it won’t overload your server.

Another great example would be a blog. Maybe you have popular blog about food and you like to post your favorite recipes regularly, but your tastes are all over the map. Even so, you have advertisers interested in advertising on posts featuring recipes that include ingredients they sell. Here’s where your problem comes in: all of your blog posts share the same page template so you are stuck with using the same zones for all of your posts. To pull this off you absolutely need contextual targeting so that you can target campaigns only to posts that mention key ingredients.

How about advertising networks? Even if you run a niche network there can still be a lot of potential for increasing relevancy and optimizing inventory usage with contextual targeting.

The Important Part: Associated Costs

We’ve set the price for contextual targeting very low to make it affordable for everyone. AdvertServe users can add contextual targeting to any plan for only $49 per month. There is no setup fee and there are no usage restrictions. AdvertPro users can buy the contextual targeting module for a low $449.00 one-time fee. Updates to the module are free as long as you have a current AdvertPro support contract.

Your advertiser has just e-mailed to inform you that they have acquired a shorter domain name. They would like you to change all of their ads to redirect to the new, shorter domain name. So, you log in to AdvertPro, go the media listing, filter it by their advertiser account and as you were fearing they have around a hundred Flash banners in total. Editing each of those media to change the redirect is not only going to be time consuming, it’s going to be error-prone because you could easily miss one of them in the process.

API to the Rescue!

Why not use the API to make all of the changes for you? It can take care of them in a matter of seconds. You just have to create a quick script that does the following:

1. Query the API for a list of Flash banner media owned by the advertiser
2. Do a search/replace for the domain name on the clickTAG of each Flash banner media
3. Use the API to update the media with the new clickTAG value

The Solution

Here we have a Perl script that will do a search/replace to change www.xyzcorporation.com to www.xyz.com in the ClickTAG URL for all Flash banners owned by the advertiser.

#!/usr/bin/perl -w
 
#
# Load Required Modules
#
 
use strict;
use LWP::UserAgent;
use XML::Simple;
 
#
# API Configuration -- Edit This Part
#
 
my $API_BASE_URL = "http://www.example.com";
my $API_SECRET_KEY = "5eb63bbbe01eeed093cb22bb8f5acdc3";
 
#
# Advertiser Information -- Edit This Part
#
 
my $ADVERTISER_ID = 1;
my $OLD_DOMAIN = "www.xyzcorporation.com";
my $NEW_DOMAIN = "www.xyz.com";
my $FLASH_TYPE_ID = 11;
 
#
# Here we set up an HTTP POST requests to query for the list
# of Flash banner media owned by the advertiser.
#
# The media type for Flash banners is 11, which you will find
# in the media API documentation.
#
 
my %query_params = (
  "secret" => "$API_SECRET_KEY",
  "advertiser" => $ADVERTISER_ID,
  "type" => $FLASH_TYPE_ID
);
 
my $query_ua = LWP::UserAgent->new;
 
my $query_response = $query_ua->post(
  "$API_BASE_URL/servlet/control/api/media/query", \%query_params
);
 
#
# If the API request was successful, parse the returned XML
# and loop through each media.
#
 
if ($query_response->is_success)
{
  my $xml = XMLin($query_response->decoded_content, KeyAttr => []);
 
  if ($xml && $xml->{'media'})
  {
    foreach my $media ( @{ $xml->{'media'} } )
    {
      #
      # Test to see if the clickTAG contains a reference to the
      # old domain name. If it does we can replace it with the
      # new domain name.  Then we can make another API request
      # to update the media on the ad server with the change.
      #
 
      my $clicktag = $media->{'creative'}->{'flash'}->{'clicktag'};
 
      if ($clicktag =~ /$OLD_DOMAIN/i)
      {
        $clicktag =~ s/$OLD_DOMAIN/$NEW_DOMAIN/ig;
 
        my $update_ua = LWP::UserAgent->new;
 
        my %update_params = (
          "secret" => "$API_SECRET_KEY",
          "id" => $media->{'id'},
          "flash_clicktag" => $clicktag
        );
 
        my $update_response = $update_ua->post(
          "$API_BASE_URL/servlet/control/api/media/update", \%update_params
        );
 
        if ($update_response->is_success)
        {
          print "Updated successfully: " . $media->{'name'} .
                " (ID# " . $media->{'id'} . ")\n";
        }
 
        else
        {
          die $update_response->status_line;
        }
      }
    }
  }
}
 
else
{
  die $query_response->status_line;
}

Some changes are necessary at the beginning of the script to change your API base URL and your secret API key as well as the advertiser ID# and old/new domain names.

More Solutions

This is just a simple example of how the API can save you time by performing a repetitive task for you. To learn more, continue reading the API chapter in the user manual: http://www.advertpro.com/docs/2.0/html/manual/api.html Remember, the API can work with any programming language! I personally just like Perl. Feel free to use Java, PHP, Ruby or whatever you’re most comfortable coding in.

For those of you that missed the announcement back in April, both AdvertPro and AdvertServe now have a complete data management, code generation and reporting API. What can you do with the API? Just about anything that you can do with the control panel. In fact, our control panel is running on top of the API, which means you could even go so far as to build your own. More commonly the API can be used for integration with other systems and automation of bulk operations.

For more information, please visit our developers page to access the API documentation.

Protect Your Secret Key

While it may be tempting to use JavaScript to interface directly with the API from a web page it’s not a safe practice. Especially if the page is located on a publicly accessible web site. All someone needs to do is view the source code of the page and they can easily steal your secret API key and start wreaking havoc on your data!

We’re not saying to avoid using JavaScript. By all means use it. Just make sure you’re doing it in a safe way.

1. Create a script using your language of choice (Java, Perl, PHP, Ruby, etc…) on your server that makes the request to the API and outputs its response.
2. Your secret API key should be stored in the script or in a file or environment variable that it can read.
3. Restrict file system access to your script or other file(s) where your secret API key is stored to only the necessary system users.
4. Make your JavaScript interface with your script rather than using the API directly.

This accomplishes the goal of keeping your API key a secret because it does not need to be transmitted to the client.

Restricting API Access

The API settings allow you to restrict access by IP address. This should be used to permit only the systems that need to use the API to connect to it. Like the IP address targeting in AdvertPro it supports range matching. For example, if you enter 192.168.1. it will allow access from 192.168.1.0 through 192.168.1.255 or if you need to target a smaller group of IP addresses entering 192.168.1.[8-16] would only allow access from 192.168.1.8 through 192.168.1.16. Just make sure to only put one IP address or range per line in the box when entering them.

Preventing Eavesdropping

Even though you are restricting access by IP address and not exposing your secret API key to the client, it is still a concern that data is being transmitted to and from the AdvertPro or AdvertServe servers over the public Internet. It might hop over 20+ servers before it gets there. If any one of those servers along the way is compromised an attacker could capture your secret API key and more importantly all of the data that you’re transmitting back and forth.

What can you do to stop that? The same thing you do to protect financial transactions: use HTTPS with an SSL certificate. This encrypts the data going back and forth between the API so that it can’t be read by anyone who might be attempting to listen in.

With AdvertServe getting an SSL certificate is easy. Just contact support and ask them to set up SSL for your account. It only takes a few hours to set up and it’s only $10/month! This will also secure your control panel and enable you to serve ads to secure pages as a bonus.

AdvertPro users will need to purchase and install an SSL certificate with Tomcat or Apache if they’re using mod_proxy_ajp. Our recommendation is the Standard SSL certificate from GoDaddy. It’s only $69.99/year and it’s guaranteed compatible with Tomcat, which is something I can’t say for many other SSL vendors. Many of them claim their SSL certificates will work with Java applications but they don’t and SSL certificates are generally non-refundable. Don’t say you weren’t warned!

Stay Tuned!

In the coming weeks I will be writing several articles about using the API for various purposes. Security comes first though. Some of the things that I plan on writing about will include creating advertiser and publisher signup forms, bulk zone creation, bulk changes to campaigns and media and how to create a script to e-mail PDF reports to you. If you have anything else that you’d like to see an example of, please comment!

Typically a lightbox is used to overlay larger versions of photos on top of a page when you click on their smaller counterparts. They are also great for advertising. Using a lightbox you can display your advertisement over top of your page when a visitor first arrives. This guarantees that the visitor will see your advertisers message and it is an easy way to create some valuable new ad space on your site.

Live Example

Let us take a look at a live example so we can see exactly what a lightbox advertisement looks like.

View Example

Pretty neat huh? Keep in mind that this is just an example so we are trying to keep it simple. It is possible to fully customize the HTML code displayed inside of the lightbox. So, yes, you can use Flash or even create an interactive mini-site to more deeply engage your visitors.

Loading jQuery

Odds are that you are probably already using jQuery on your web site. If you are there is no need to load another copy of jQuery. In fact, it is a bad idea to embed jQuery within your ads because of its size. For that reason we recommend that you load jQuery directly into your page if you aren’t already using it. Ideally you would load it from a CDN, such as the free ones provided by Google and Microsoft.

Download SimpleModal

The next step is to download the SimpleModal plugin for jQuery.

Download Here

There are two files contained in the ZIP file that you will want to upload to your server:

• jquery.simplemodal.css
• jquery.simplemodal.js

Remember to make note of their URLs because you’ll need them in a later step.

Creating the Media

1. Log in to AdvertPro and click on Media in the toolbar
2. Click on the Create New Media link
3. Enter a Name for you media, select the Advertiser and choose Dynamic for the media type.
4. Paste the following code into the Local HTML Content box (notice we prefix the links with %%CLICKLINK%% so the ad server can track clicks):

   <div id="lightbox-banner" style="display: none">
     <a href="%%CLICKLINK%%http://www.sanfrancisco.travel/"><img src="http://services.renegadeinternet.com/examples/lightbox-banner/img/goldengate.jpg" border="0" width="625" height="434" alt="Click Here!" /></a>
     <div id="simplemodal-caption">
       Advertisement
     </div>
   </div>
   <script type="text/javascript">
   jQuery(function ($) {
     $('#lightbox-banner').modal();
   });
   </script>

5. Press the Create Media button to complete the process

Publishing to your Website

1. Log in to AdvertPro and click on Code Wizard in the toolbar
2. Click on the Dynamic Code option in the menu on the left
3. Then click on the HTML link underneath it
4. Select the Media you just created on the right
5. Press the Generate Code button
6. Copy the generated code and paste it into the bottom of your page
7. Finally, you should insert the following code just before the media code to ensure that SimpleModal is loaded first:

   <script type="text/javascript" src="http://www.yoursite.com/js/jquery.simplemodal.js"></script>
   <link href="http://www.yoursite.com/css/jquery.simplemodal.css" rel="stylesheet" />

The Final Result

At this point you should be able to go to your site and see your new lightbox advertisement as soon as the page loads. If you run into trouble, take a look at the index.html file contained in the ZIP file you downloaded earlier. It will show you how to properly include jQuery, SimpleModal and the the AdvertPro code into your page.

Bits on the Run manages the complete video workflow: upload, transcode, stream, and analyze.  They handle the complexities so that you don’t have to.   With just a few clicks you can design your own video player, encode to multiple bitrates, deliver to multiple platforms/devices, and more.  In this blog post we’re going to be looking specifically at how to create a video player for displaying video banner ads.

Creating a Free Account

1. Open your browser to http://www.bitsontherun.com/
2. Click on the Free Account button
3. Enter your E-mail Address and create a Password
4. Wait a minute and then check your e-mail for a message from Bits on the Run.   Click on the Activate Your Account button contained in that message to activate your account
   
5. You will then be logged in to your new account

Uploading a Video

1. Click on the green Upload a Video button on the home page
2. Click Browse to locate the video file on your computer.  It can be in any format.  If you don’t have a video to test with you can download the QuickTime trailer for Big Buck Bunny, which we’ll be using in this example.  After you’ve selected the file press the Upload button.
3. Once the file finishes uploading you can enter some information about the video such as a title, description and the date it was produced

Creating a Custom Player

1. Click on the Players tab at the top of the page
2. Make a copy of the 4:3 example player by pressing the duplicate button to the right of the player’s name in the list of available player configurations (see below)
3. Click on the 4:3 example player (copy) you just created in the list of available player configurations.
4. Change all of the following settings and then press the Save button when you are done.
   
   
   

Generating the Video Embed Code

1. Click on the Videos tab at the top of the page
2. Then press the embed button to the right of the video’s name in the list of available videos (see below)
3. Change the Player to the new 336×280 Banner Player that you created (see below).
4. Copy the HTML code from the Embed Code box, which should look like the following:

   <script src="http://content.bitsontherun.com/players/KFLTjIVN-g3oqV69i.js" type="text/javascript"></script>

5. Next, you want to append the following code to it (this enables click tracking with the clickproxy plugin):

   <script type="text/javascript">
   function clickListener (obj) {
     window.location.replace('%%CLICKLINK%%http://www.example.com/');
   }
   </script>

6. Change http://www.example.com/ to the URL you want the video to redirect to when clicked on.  Leave the %%CLICKLINK%% variable in front of the URL to enable click tracking.  Also, if the URL contains a query string it should be URL encoded before inserting it into the code!
7. Now you should have a completed video embed code with click tracking support that looks like this:

   <script type="text/javascript" src="http://content.bitsontherun.com/players/KFLTjIVN-g3oqV69i.js"></script>
    
   <script type="text/javascript">
   function clickListener (obj) {
     window.location.replace('%%CLICKLINK%%http://www.bigbuckbunny.org/');
   }
   </script>

Creating the Media

1. Log in to AdvertPro and click on Media in the toolbar
2. Click on the Create New Media link
3. Enter a Name for you media, select the Advertiser, choose HTML banner for the media type and 336×280 for the size.
4. Paste the video embed code into the Local HTML Content box
5. Press the Create Media button to complete the process

The Final Result

At this point you can preview the media to watch your new video ad! Click on the picture below to watch the one that I created.

Remember to try clicking on it. If the click tracking is working properly you will be redirected to the Big Buck Bunny movie home page.

Chains provide a way for you to logically group campaigns together and display them in a specific order.

Say, for example, that you have the following types of campaigns running in the same zone:

• Paid campaigns
• Third-party ad network campaigns
• In-house campaigns

You want to make sure that all of your paid campaigns get the required number of impressions.  That is accomplished by placing them in a higher chain than your other campaigns.  By placing your third-party and in-house campaigns in lower chains they will only take up the excess impressions. Let’s look at how the chains should be set to make that happen.

The ad server starts at the highest chain (greatest number) and works its way down to the lowest chain. Visitors will first see the paid campaigns, then the third-party campaigns and finally your in-house campaigns.

How does the ad server decide when to move between chains?

Good question!  Your campaigns in the higher chains will normally have some types of  limits set on them.  They might be using even distribution, frequency capping or some form of targeting.  Those settings will all limit their impressions.  Say, for example, that you set a frequency cap of 2 views per hour on all three of your paid campaigns.  After six page views those campaigns would all be “capped out” so the ad server would move down to the next chain and start showing your third-party campaigns.  Once the frequency caps have expired, the ad server will actually move back up to the higher chain and display your paid campaigns again.

What About Priority?

Most of the time you will have several paid campaigns running at the same time.  By default all campaigns are given the same priority so that they will rotate equally.  What if you want one campaign to run more than the others though?  Simply increase its priority to be higher than the others.  There are several ways to do this using ratios and percentages, so you can decide which is easier for you to use.

Using Ratios

Using Percentages

The trick with using percentages is to make sure your priority values all sum up to 100.  That effectively makes them equivalent to percentages.  The nice thing is that you don’t need to do any math to convert ratios to percentages if you do this!

Another important thing to remember is that each chain operates independently. That means that priority values are only ranked against priority values of campaigns in the same chain.  This allows you to virtually have multiple rotations within a single zone, so if a campaign in the highest chain was set to get 20% of the impressions it would only get 20% of the total impressions given to that chain rather than 20% of the total impressions for the zone.

Hopefully this helps demystify chains for those of you having a hard time understanding them.  They really are a powerful tool.  Using them effectively with even distribution, frequency capping and targeting is a great way to optimize your inventory usage.

How many times have you put a new Flash banner campaign online only to find it is not clickable? Maybe it was clickable when you put it online, but days later you discover it’s not tracking clicks because the advertiser embedded their link in the Flash .swf file. Did the advertiser forget to tell you they used clickTag rather than clickTAG? Unless you’re extremely lucky, you’ve no doubt traded dozens of e-mails back and forth with an advertiser trying to help them get their clickTAG working correctly too many times.

Help has Arrived!

AdvertServe users now see the following prompt appears after uploading a Flash .swf file.

Simply click the Yes button and your Flash .swf file will be tested in a real browser environment. If the clickTAG is broken or missing it will instantly be repaired. Since we’ve partnered with another company to provide this feature we will be charging $1.79 per file you choose to verify, however, we shouldn’t need to convince you that this is a small price to pay to guarantee a working clickTAG with no hassle.

Wait… I have to Pay to Upload .swf Files Now!?!

No, simply click the No button and your Flash .swf file will be uploaded without testing the clickTAG.  There is no charge for that.  In fact, this is a good way to avoid paying the $1.79 fee if you already know the clickTAG works.  What happens if you choose to skip testing and your clickTAG doesn’t work though?  In that case you will see a green check mark icon displayed to the right of the Flash .swf file name in the file browser.  Simply click that icon and it will prompt you again to run the testing and repair the clickTAG.

It Really Works?

Yes, it really does! Here is a list of common problems that will be detected and fixed.

• Embedded or hard-coded links
• Using the wrong combination of ActionScript and Flash versions
• Missing clickTAG button
• Missing or broken clickTAG scripting
• Using clickTag, ClickTag, etc… instead of clickTAG

Of course it’s not limited to fixing just those problems. If an unknown issue is detected a new top layer with a working clickTAG will be inserted into the Flash .swf file. This allows the tool to fix anything your advertisers can throw at it!

We hope you enjoy using this new tool as much as we do.  If you’re an AdvertPro user, don’t worry, this will also be made available to you very soon!