Pages

Path in Platform: Inventory > Pages

Last edited: 2024/02/07

Pages main purpose is to allow to limit which ad units have Yieldbird’s targeting and (when using Prebid Stack) participate in Prebid Auctions.

Also, you can use it to set shorter Prebid Auction timeout for specific page types (e.g. gallery pages)

What is Page

You can treat Page as a "smart" bucket for ad units. It is basically a list of ad units that you want to call on a defined URL. In other words, Yieldbird will trigger Prebid Auctions and key value targeting only on ad units assigned to a given URL.

URLs don't have to be defined very precisely; you can specify the Page to combine a collection of URLs by matching them using a regular expression (more about it in How to define a page? below).

Good Practice: It is strongly recommended to use Pages when you are using Ad units detection & targeting mode : Target all units at once / prefetch only. For other Targeting / auction type settings Page architecture is not needed. The main reason for that is that in such scenario Pages 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.

How to define a page

1. In the Pages tab, click <Add new>.
2. Select the domain for which you want to create a page.
3. Define how the Page shall be detected. To do that, write the URL path to be recognized and define how the system shall treat the defined URL path:
• Include - will match all URLs containing the page name
• Exact match - will match only one specific URL
• Regular expression - will allow you to execute the script provided it finds the match

Examples of usage:

• Include or exact match:
• /article/image/ - as exact match will match https://example.com/article/image but it won’t match https://example.com/article/image/12
• /article/image/ - as include match will match https://example.com/article/image/12 and https://example.com/article/image/
• Regular expression:

If you have URLs like so:

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

Where each geo has its own country code and feed and article have a different ad layout. Then you can separate article and feed by creating pages this way:

4. /\w+/article.*
5. /\w+/feed.*

This way you will cover all country codes.

Also, you can use several regular expressions at the same time, adding the regular expressions you are looking for separated by “ OR “ (space+OR+space, with OR in capital letters. If you miss any of these rules, e.g. write “ or “, “OR “, “ .OR “ etc., it will not work).

4. Add the ad units to the Page, using the transfer list

Other use cases of page architecture

• Some of Yieldbird’s Publishers used Pages to disable e.g. Prebid only on single URLs. To do that they created a Page without any ad units in it.
• You can customize the Prebid Timeout per page, for example, by setting it to lower values for URLs where the user spends less time.

On this page:

• Pages
• What is Page
• How to define a page
• Other use cases of page architecture