> For the complete documentation index, see [llms.txt](https://docs.adsecure.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adsecure.com/features/iab-standards.md).

# IAB Standards

Check with AdSecure if your ad campaigns are compliant with the IAB Standards.

## What are the IAB Standards?

The Interactive Advertising Bureau (IAB) is an advertising business organization that develops industry standards, guidelines and best practices for digital ads. When digital ads are compliant to the IAB Standards they are optimised to provide the best experience for the end user. As a result, such ads consistently drive higher levels of user interest and click rates, and can be a key difference between a higher or lower conversion rate for digital ad campaigns.

## Enable IAB Standards in your scans

Ads will only be checked for compliance with the IAB Standards when the 'IAB Standards' feature is enabled in the project creation or quick analysis creation.

![](https://1597915041-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPFKZe65DxLiZWt9eUQJw%2Fuploads%2FsPTS1Y0aStQQuuu31q3r%2F3bb738fe4bf3.png?alt=media\&token=bc53cb83-4ae6-4d1e-8745-1bd85cef92bd)

## IAB violations

When the IAB Standards feature is enabled on scans, an audit is performed per detected ad for the IAB violations below.

**IAB: Ad Dimension**\
IAB recommends certain ad dimensions that contribute to the majority of revenue and are sufficient to advertise across multiple screen sizes. This detection will flag ads that are not compliant with the IAB standards in terms of ad dimension. IAB recommends that the ad dimension should be in the range of 100x200 - 150x300.

**IAB: Ad Weight**\
Ad weight is the total size of all the ad assets being delivered to the browser at a given phase. This detection will flag ads that are not compliant with the IAB standards in terms of ad weight (initial load and sub-load). IAB recommends an ad size with an initial load of maximum 50KB and a sub-load of maximum 100KB.

**IAB: Ad Request Count**\
Ads consist of multiple resources. The number of requests made to fetch these resources has a significant impact on the load performance of the ad as well as on the page where the ad is displayed. This detection will flag ads that are not compliant with the IAB standards in terms of ad request count. IAB recommends a maximum of 10 requests.

**IAB: Ad File Compression**\
To optimize the file size for delivery of an ad to a browser, the assets within the ad should be delivered in compressed formats such as gzip. This detection will flag ads that are not compliant to the IAB standards within this category, which means they are not delivered in a compressed format.

These violations will be displayed in AdSecure reports when detected, just like you are used to from other violations in AdSecure. The IAB violations belong to the *User Advisory* category in AdSecure.

## IAB performance widget

Besides violations that appear in the AdSecure analyses, there is also a Performance widget present in individual ad reports where more information per IAB audit is displayed when the 'IAB Standards' feature was enabled on the scan.

![](https://1597915041-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPFKZe65DxLiZWt9eUQJw%2Fuploads%2FZgZ7upEymt1IiVQf5BNY%2F20e99b2e4775.png?alt=media\&token=13555d09-6ee6-41fc-aaf2-8216589f795e)

In this example, the ad creative is compliant to the IAB Standards in 3 of the 4 audits. The audit for *IAB: Ad Dimensions* reports that this ad creative is not compliant to the IAB Standards.

Learn more about [IAB Standards](https://www.iab.com/wp-content/uploads/2019/07/IABNewAdPortfolio_FINAL_0719.pdf).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.adsecure.com/features/iab-standards.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
