For security and page load reasons, it's highly advisable you serve ads through Kevel's Decision API.
Kevel offers four ad code options: Synchronous, Asynchronous, Email, and 3rd Party Ad Server.
Synchronous code loads on a page like it normally does: line by line, waiting for element. It can potentially slow down page loads, especially if the synchronous code is serving third-party ads that pass impressions from one server to another.
3rd Party Ad Server code is useful if you are serving Kevel ads through another server (such as DFP), or if you need to serve ads to a platform where HTML cannot be used. Note that 3rd Party Ad Server code cannot be used with companion ads or other distribution options.
All Standard ad tags contain a comment that explains what the code loads:
/* load placement for account: NetworkName, site: SiteName, size: 160x600 - Wide Skyscraper*/
ados_add_placement() function loads the actual placement:
ados_add_placement(1613, 15404, "azk57720", 6);
The first number is your network ID. The second is the site ID. The string is the name of the placement. Kevel generates this string randomly. This placement name must match in both the script and the
<div>. The last number is the adType ID.
Updated 9 months ago