Backfill codes serve the delivery of a campaign to allow the previously established whether the customer will remove the impressions delivered or whether these "returns". For this, all impressions are sent to the customer adserver once, who can decide whether he wants to point out these. he wants this not prove with advertising, he returns it to AdSpirit and AdSpirit can bring a different customer delivery.
use
To use backfill codes please activate in the campaign planning the appropriate entry. Also send the located to backfill code to the customer and let them know that the code has to be adjusted in two places. Example Code:
<script type="text/javascript" language="JavaScript">
(function ()
{
var asm_pb_x = 728; // <-- CHANGE THIS VALUE ACCORDING TO CREATIVE WIDTH
var asm_pb_y = 90; // <-- CHANGE THIS VALUE ACCORDING TO CREATIVE HEIGHT
//DO NOT CHANGE ANYTHING BELOW HERE
... ... ...
})
()
</script>
The two bold in the above example code numbers are to be adapted by the customer by the height and width of the delivered advertisement. These values must match the height / width are set in the ad server in the customer advertising materials (eg the customer advertising material is created as HTML advertising media in 300x250, then it must be registered in the code 300 and 250). Script-promotional obtain the values 0 (zero) for height and width.
The code thus generated must always deliver the customer if he does not want to use even an overlay. Making sure that the code is correctly installed and in use. All overlays where no backfill Code has been deposited by the customer are counted for the customer (ie even if the customer has forgotten to install the backfill Code).
adjustments
In certain situations, adaptations to the code are necessary. The following adjustments allowed AdSpirit this:
asynchronous loading
If the customer uses asynchronous code, must this be signaled to the backfill script. To this end, in the AdSpirit saved by the promotional article client code is adjusted. The following line is to be inserted before the code of the customer:
<script type="text/javascript" language="JavaScript">
asm_bkfl_obj.setAsync("%backfill_instance_id%");
</script>
causes the call of this script that the backfill code automatically waits up to 1500 milliseconds to asynchronously executed by the customer and the customer scripts so that time is to decide whether or not to display.
Please note: If this method is used, is that the customer does not decrease a display in the case, necessarily written an IFrame for the next customer.
Offline mode
In certain situations, especially if the customer loads multiple iframes or scripts before he makes a decision, it may be necessary that the customer is not only feedback if he wants to return a display but that it also provides feedback when the display wants to lose weight. To this end, in the AdSpirit saved by the promotional article client code is adjusted. the following line is to be inserted before the code of the customer:
<script type="text/javascript" language="JavaScript">
asm_bkfl_obj.setOffline("%backfill_instance_id%");
</script>
causes the call of the script that the backfill code is not independent but only waiting for the feedback from the customers. So that the customer can notify his feedback, this used to send back the traffic, the value stored in the campaign planning> Backfill code. If the customer remove the display, he used the same code and makes the following adjustments. Before:
...
if(typeof(asm_bkfl_obj) != "object"){ asm_sndMsg("asm_bkfl:"+asm_amsname+";"+asm_kidid+";"+asm_pb_x+";"+asm_pb_y); }
else{ asm_bkfl_obj.pushBack(asm_amsname,asm_kidid,asm_pb_x,asm_pb_y); }
...
Later:
...
if(typeof(asm_bkfl_obj) != "object"){ asm_sndMsg("asm_bkfl:fire;"+asm_amsname+";"+asm_kidid+";"+asm_pb_x+";"+asm_pb_y); }
else{ asm_bkfl_obj.fire(asm_amsname,asm_kidid,asm_pb_x,asm_pb_y); }
...
If the backfill code can be used directly in the advertising medium, alternatively, the following code may be used:
<script type="text/javascript" language="JavaScript">
asm_bkfl_obj.pushBackID("%backfill_instance_id%");
</script>
... to return the display, and:
<script type="text/javascript" language="JavaScript">
asm_bkfl_obj.fireID("%backfill_instance_id%",false);
</script>
... to remove the display.
Furthermore, callback functions can be defined which call a JavaScript (accepted View, View returned) when a state has entered:
<script type="text/javascript" language="JavaScript">
asm_bkfl_obj.setCallBack("%backfill_instance_id%", "funktionA", "funktionB");
function funktionA(id){/* view wurde abgenommen */}
function funktionB(id){/* view wurde zurückgegeben */}
</script>
Setting the timeout
If an advertiser will not be able to access the passback code in the gefoderten time there will be deviations. Should the period be raised, the following code needs to precede the advertising media:
<script type="text/javascript" language="JavaScript">
asm_bkfl_obj.setMaxTimeOut("%backfill_instance_id%", 3000, 6000);
</script>
In the above example, the time period is increased to 3,000 to 6,000 milliseconds.
Possible problems
Possible reasons for Zählabweichungen are generally in the technical nature of the backfill codes: If this is not or not displayed by advertisers right or "thinks" AdSpirit other reasons that this was not displayed, is automatically counted for the advertisers and there are deviations (AdSpirit numbers> Advertiser numbers).
The other way around, there are always differences in favor of Advertisers (AdSpirit numbers <Advertiser numbers) when about the browser fails to comply with certain orders. This is particularly noticeable in Internet Explorer, especially if the ad shown by the advertiser very many other scripts for loads (more than 3 steps).