The ad media is loaded within an iFrame at the position on your website where you position our embed code or the placeholder HTML container. The size of the iFrame, as well as the number and design of the ads can be freely configured by you via the ad unit layout form in the publisher frontend.
As the name "Static-Ads" implies, the size of the ad is static and therefore should rather be used in the desktop area. However, if you optimize your website for different screen sizes, then we recommend using Responsive-Ads.
Through the asynchronous integration, your website is loaded independently of the advertising call of our ads. First, you place the desired placeholder HTML elements at the locations on your website where you want ads to appear. Then, our delivery API is loaded once and asynchronously using a dynamic <script> tag. Once the API has finished loading, a global callback function is executed which stores your actual embedding logic.
This type of integration is especially useful if you want to place multiple AdUp ads on your site. Due to the programmatic definition of the ad units, you also have various events available to which you can react accordingly (e.g. "onClick" or "onNoAds").
With synchronous integration, a <script> tag is specified directly at the position on your website where the advertising material should appear. When your website is loaded, the script is then executed automatically (synchronously) and creates an iFrame with our ads at the corresponding position.
This is the easiest way to integrate AdUp ads. However, due to the definition of the ad unit via URL parameters, not all options are available to you here in contrast to the asynchronous integration.
The unique placement key of your ad unit.
Activates/deactivates the Responsive-Ads feature for the ad unit.
Note: For "Static-Ads" in the asyncrhonous integration, the parameter must always be set to "false"!
Keywords by which the ads are to be filtered. Several keywords can be separated by semicolons.
This is the minimum price you want to earn for a click. Generally, the lower the minimum price, the more campaigns you will be presented with and the more money you can earn due to greater competition for the position.
The current URL of the page on which the advertisement is played. Should always be set if our advertising material is embedded within one or more nested iFrames on your page, as we may then no longer be able to determine the url.
Number of ads to be skipped during delivery. Useful if you place several ads on one page.
Activates the "Lazy Loading" feature. This means that the ad is only loaded (and thus the impression is only tracked) as soon as it is visible to the user.
By default, with "lazy loading" our advertising media are only displayed when they are visible to the user. With the help of the "lazyoffset" option, you also have the possibility to define an offset (in pixels). In this way, our advertising media load a little earlier as soon as they are "close" to the visible area.
Values for dynamic ads placeholders can be transferred here.
Activates the "Fly-In-Ads" feature for the ad unit.
For more information and options, see the Fly-In Ads documentation.
Impressions and clicks are not tracked when activated. Should only be used for test purposes!
Normally, we determine the required GDPR data automatically via the TCF API built into the website.
If this is not available, or if it is not possible to use it for technical reasons, you have the option of transferring the GDPR data manually here.
true or 1 = GDPR applies
false or 0 = GDPR does not apply
null or (omit) = Unknown (default)
The IAB Consent String (base64url-encoded)
Translated with www.DeepL.com/Translator (free version)