Path in Platform: Inventory > Pages
Last edited: 2025/04/17
Layouts (formerly known as “Pages”) allow you to control which Ad Units receive ad requests based on defined triggers. You can also specify settings that apply at the Layout level. These settings will override Domain and Ad Unit level settings (see: Which setting applies to the ad unit when the parameter is set at multiple levels?).
A Layout is a "smart" container for Ad Units. It acts as a list of Ad Units that should be called when specific triggering criteria are met.
In other words, it allows you to send ad requests (with all necessary targeting) only when certain conditions are met - for example, if a user lands on a specific URL or belongs to a predefined group (such as non-subscribers).
<aside> <img src="/icons/arrow-right_green.svg" alt="/icons/arrow-right_green.svg" width="40px" /> Good Practice: It is strongly recommended to use Layout when you are using Ad units detection & targeting mode : Target all units at once / prefetch only.
The main reason for that is that in such scenario Layouts can decrease the size of the JavaScript sent by Yieldbird Tag and make it execute faster which can result in better Core Web Vitals (First Input Delay) and give Prebid Bidders more time to bid.
</aside>
To trigger the Layout based on URL:
Enable ‘URL’ Trigger
Write the {URL path} to be recognized
Choose how the system should interpret the path:
Examples of usage:
Include or Exact Match:
/article/image/
as Exact match → matcheshttps://example.com/article/image
/article/image/
as Include match → matcheshttps://example.com/article/image/12
andhttps://example.com/article/image/
Regular Expression (regex):
Use regex for URLs like:
https://example.com/UK/article
https://example.com/IT/feed
To separate articles and feeds by country:
/\\w+/article.*
/\\w+/feed.*
Use multiple expressions with " OR " (space + OR + space, in caps) e.g.:
/\\w+/article.* OR /\\w+/feed.*
⚠️ Incorrect formats like
"or"
,"OR "
, or" .OR "
will not work.
On this page: