Wiki source code of Zavolání Ad Serveru

Last modified by ZdVo on 2017/12/04 08:45
Content · Comments (0) · Attachments (0)
Hide line numbers
 1: Now that everything is configured, we know what data we want to sent and which ad slots are managed by which ad server, we are ready to call the ad server for the ads.
 2: There are actually various ways to do that depending on how much control you want to have, but in 99% of cases you will call the following method:
 3: 
 4: {{code language="js"}}
 5: ibbAds.tag.requestAndPlaceAds();
 6: {{/code}}
 7: 
 8: This will call **ALL** configured Ad Servers,  request ads for **ALL** configured Ad Slots and place the ads in their respective ad slots as they arrive.
 9: 
10: As you can see, a lot is happening in that call.  
11: 
12: You can have more control over which ad slots you want to fill with ads by providing arguments to the call. Let's explain it by example:
13: 
14: {{code language="js"}}
15: ibbAds.tag.requestAndPlaceAds(adserver); // will only request ads for ad slots managed by 'adserver', but not by 'adserver2'
16: ibbAds.tag.requestAndPlaceAds('BbmCz'); //  will only request ads for ad slots managed by ad server 'bbmcz' - referenced by name
17: ibbAds.tag.requestAndPlaceAds(sky); // will only request ads for ad slot referenced by variable called sky - the tag will call the appropriate ad server as configured for the slot
18: ibbAds.tag.requestAndPlaceAds('skyscraper'); // will only request ads for ad slot referenced by name 'skyscraper' - the tag will call the appropriate ad server as configured for the slot
19: ibbAds.tag.requestAndPlaceAds(['skyscraper','bottom-right-ad-slot']); // will request ads for listed ad slots from their corresponding ad server(s) - it is also possible to pass in variables referencing ad slots and any combination of names and variables
20: 
21: {{/code}}
22: 
23: Using these calls, you can for example first request the ads for the first 5 ad slots in the page which you know are almost always visible and only request ads for remaining 3 ad slots if the user scrolls down to a certain point etc.
24: 
25: 
26: You can have even finer control over requesting ads and placing the to the page, although in most cases it is not advisable to manual manage the process.
27: 
28: If you want to only request the ads (without placing them into their ad slots), you use the call:
29: 
30: {{code language="js"}}
31: ibbAds.tag.requestAds();
32: {{/code}}
33: 
34: It accepts the same arguments as the requestAndPlaceAds call, so you can do it for only a chosen ad server instance or chosen ad slot(s). Because all calls to ad server are asynchronous, you will only receive a reference to "future" ads (the ads that will arrive in the future) and you have to handle that accordingly. For that, a method called whenAdsArrive is provided so that you can grab the ads as soon as the ad server returns them and do what you need to do with them. Here is the example of how you would do that:
35: 
36: {{code language="js"}}
37: 
38: ibbAds.tag.requestAds().whenAdsArrive(function(ads) {
39:     // manipulate the array of ads returned from ad server
40:     // not that this function will be called one time for each ad server from which the ads were requested and it may returned empty array of ads if no ad was returned.
41: });
42: 
43: {{/code}}
44: 
45: {{warning}}
46: 
47: In case of multiple call of requestAndPlaceAds method in paralel (in same time) and per position, for example (ibbAds.tag.requestAndPlaceAds('skyscraper'); ibbAds.tag.requestAndPlaceAds('square'); ibbAds.tag.requestAndPlaceAds('leaderboard'); ...) competition/surround ad funcionalities will not work. There could be problems with frequency capping as well. Since frequency capping is written into cookie and cookie is dependent on domain. (in this case on showit domain). So, last paralel showit request will overwrite "frequency cookie" (information about frequency could be erased). From those reasons, we strongly recommend to call/request position, which are supposed to be displayed in same time, within one showit request. If is necessary to call showit request per position, then call each showit sequentially and not in parallel. 
48: 
49: {{/warning}}
50: 
51: 
52: {{info}}
53: 
54: Please note that requesting ads is also considered as impression and **will be charged** according to your pricing scheme!!!
55: 
56: {{/info}}
57: 
58: 
59: === Place the ads to the slots ===
60: 
61: This happens automatically if you use the standard requestAndPlaceAds call.
62: If you want to place the ads into their ad slots manually though for some reason, you can call: 
63: {{code language="js"}}ibbAds.tag.placeAds(ads); // an array of Ad definitions must be passed as argument
64: {{/code}}
65: 
66: Note that each Ad definition contains already information about to which ad slot it should be placed. The ad slot(s) are emptied before placing a new ad to them.
67: 
68: You could actually completely skip calling the ad server and place the ads created by yourself (e.g. for debugging purposes). In that case, you have to create the ad definition first and then place it,  e.g. like this: 
69: 
70: {{code language="js"}}
71: var ad = ibbAds.tag.createAd(1); // argument is ad id
72: ad.setSlotMarkup('skyscraper', '<div>some html or script to be shown in skyscraper slot</div>');
73: ibbAds.tag.placeAds([ad]); // you can place multiple ads at once if you wish
74: 
75: {{/code}}
76: 
77: 
78: === Clear ad slots ===
79: 
80: Ad slots are automatically cleared before any new ad is placed into them. 
81: If you wish to clear them manually for some reason, you can call:
82: 
83: 
84: {{code language="js"}}
85: ibbAds.tag.clearSlots(); // accepts the same arguments as requestAndPlaceAds, so you can clear any group of ad slots you wish separately
86: 
87: {{/code}}
88: 
89: 
90: === Reload ads for ad slots ===
91: You can reload ads in ad slots by repeatedly calling requestAndPlaceAds described above.
92:
Wiki source code of Zavolání Ad Serveru

Navigation

AdServer v2
