Ad

An ad a combination of a placement and template. This is where the bulk of configuration is done. For example, parting, capping, geotargeting, custom targeting and more.

Creating an ad

1. Select an advertiser

2. Select a placement

Overriding of pricing can be done here.

3. Select a template

Only templates that have been linked to the selected placement will be available at this stage.

4. Select styles

Select the styles this ad should be served in. The list of styles to chose from depend on the selected template in the previous step.

5. Locales

Choose the locales this ad can be offered in. Ads will always have a default locale. When creating creatives, the corresponding locales will be available to populate.

6. Scheduling

Start time, end time and pacing

Pacing options are asap or evenly. When evenly is selected, a start and end time must be present

7. Capping (optional)

Event Capping: Cap clicks or impressions per day or over the lifetime of the ad.

Budget Capping: Cap spending based on a daily or lifetime limit.

Frequency Capping: Cap how often an ad will be shown to the same user. Eg: Show the ad 3 times per day.

For frequency capping to work, it is required that your application sends a unique identifier per user. This identifier does not need to include personal information, but it must be a stable reference.

8. Priority

Apply a prioity to the ad (Standard, Sponsorship or House).

Apply a weight to the ad (Higher meaning more weight).

This can be used to prioritize one ad over another ad. If there are two possible candidates when requesting an ad, the ad with a higher priority will be shown.

9. Parting (optional)

Select the days and times the ad should be available to serve. Eg: All weekend, weekdays in the mornings etc.

By default, the timezone used will be the timezone of the end user. However you may want to set a specific timezone for your ads to be shown in. For example: A worldwide event like the Superbowl

10. Geotargeting (optional)

Select cities or countries you want to serve this ad in. In order for this function to work the ad request must contain one of the following:

• User's IP address, which will be used to determine the approximate location.

• Geoname ID, if the approximate location is already known by the publisher, the geoname ID can be sent directly, omitting the IP address. Eg: For targeting in Germany, 2921044 could be sent.

Must satisfy ANY of the geonames ids. Ads without geo targeting are always eligibles.

11. Location Targeting (optional)

For more granular location targeting, radii can be created via latitude, longitude and a radius values. When an ad request contains targeting.location that falls within one of the radii, the ad will eligible to be served.

Must satisfy ANY of the coordinates. Ads without location targeting are always eligible.

12. Destination Targeting (optional)

For more granular destination targeting, radii can be created via latitude, longitude, radius and minConfidence values. When an ad request contains targeting.destination that falls within one of the radii and the minConfidence value is higher than minimum value, the ad will be eligible to be served.

Must satisfy ANY of the coordinates. Ads without destination targeting are always eligible.

13. Custom Targeting (optional)

Create custom targeting parameters. When targeting.custom contains values matching the custom targeting, the ad will be eligible to be served.

Must satisfy ALL of the key values. Ads without custom targeting are always eligible.

Ad Measurement & Verification

This section covers how to configure third-party verification for your ads using the Open Measurement (OMID) standard.

Open Measurement (OMID)

Open Measurement allows external vendors (such as IAS, DoubleVerify, or Moat) to verify ad viewability and brand safety. This is essential for enterprise-grade campaigns.

General Configuration

When setting up verification, you have the possibility to use an existing configuration from the Advertiser. These "Advertiser Templates" serve as a starting point to quickly populate vendor details, ensuring consistency across all ads under the same advertiser.

Configuration Fields

When adding verification resources to an ad or creative, you must provide:

• Vendor Key: The unique identifier for the provider (e.g., ias.com-omid).

• Script URL: The URL of the JavaScript verification resource provided by the vendor.

• Verification Parameters: (Optional) A string of data used by the script to identify the specific placement or campaign.

Automatic Inheritance

All active ad verifications will be automatically applied to all creatives in the advertisement. If no active verifications are configured at the ad level, no verifications will be returned.