Layouts (formerly: Pages)

Last edited: 2025/05/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?).

What is Layout

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).

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.

Defining a Layout

1. Go to Inventory > Layout, click ‘Add New’.
2. Select the Domain for which you want to create the Layout.
3. Optionally, you can disable Only send ad requests for Ad Units assigned to the Layout.
• If enabled: When a Layout is detected on a given pageview, the Yieldbird Platform will send ad requests to GAM only for the Ad Units assigned to that Layout.
• If disabled: Ad requests will be sent to GAM for all Ad Units available on the URL, but the Yieldbird Platform (including all modules) will operate only on the Ad Units assigned to the Layout.
4. Define the Triggers for the Layout. You can trigger a Layout based on:
• URL (full path, partial path, or regular expression)
• Custom Variable (any variable used in your website architecture)

To trigger the Layout based on URL:

1. Enable ‘URL’ Trigger
2. Write the {URL path} to be recognized
3. Choose how the system should interpret the path:
• Include – matches any URL containing the defined path
• Exact match – matches one specific URL only
• Regular expression – uses regex to define complex patterns

Examples of usage:

• Include or Exact Match:
• /article/image/ as Exact match → matches https://example.com/article/image
• /article/image/ as Include match → matches https://example.com/article/image/12 and https://example.com/article/image/
• Regular Expression (regex):

Use regex for URLs like:

1. https://example.com/UK/article
2. https://example.com/IT/feed

To separate articles and feeds by country:

3. /\w+/article.*
4. /\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.

Exemplary use cases of Layouts

• Limiting Prebid Timeout on URLs where users stay for a shorter time (e.g., gallery pages) - helps reduce lost ad requests caused by longer Prebid processing.
• Controlling Ad Unit visibility based on user groups - for example, showing fewer ads to subscribers while keeping full ad setup for non-subscribers.

On this page:

• Layouts (formerly: Pages)
• What is Layout
• Defining a Layout
• Exemplary use cases of Layouts