How to Configure Delivery Rules in BiddingStack
This guide explains how to configure Delivery Rules in BiddingStack. Delivery Rules control when, where, and to whom ads are eligible to be delivered. They allow you to define traffic conditions using domains, geography, user attributes, placements, and bidder settings.
1. Log in to BiddingStack
Access your BiddingStack account and ensure that you have permissions to configure Delivery Rules for your project.
2. Navigate to Delivery Rules
In the sidebar, click Delivery Rules Sets.
3. Basic Configuration
| Field | Purpose |
|---|---|
| Name | A unique identifier for the Delivery Rule |
| Enable | Enable or disable the rule |
| Projects | Define which project or projects the rule applies to |
4. Define Rule Logic
Delivery Rules are built using logical conditions that determine whether a request is eligible for bidding. Rule logic is divided into two main sections: Context and User Profile.
Each section can contain one or multiple Groups. Conditions inside a group are applied using OR logic. Multiple groups are applied using AND logic.
Each Condition supports different comparison operators depending on the data type. You can freely choose the appropriate operator based on your use case, such as equals, contains, starts with, less than, and other available options.
This flexibility allows Delivery Rules to be tailored precisely to different traffic, user behavior, and targeting requirements.
Below is a detailed list of available Conditions:
| Section | Condition | Description and Typical Usage |
|---|---|---|
| Context | Domain | The domain name of the page. Used to target specific websites. |
| URL | Full page URL including path. Used to target specific sections or page types. | |
| URL Query | Parameters in the URL. Commonly used for campaign or source targeting. | |
| Cookie | Browser cookie values. Used to identify logged-in users or custom segments. | |
| Last Referrer | The referring page or domain. Used to distinguish traffic sources. | |
| Meta Property | HTML meta tags defined on the page. Used for content metadata targeting. | |
| LocalStorage Variable | Values stored in browser localStorage. Used to persist user state across sessions | |
| Data Layer | Variables provided by the site data layer. Used for structured page or analytics data | |
| Segment ID | Predefined audience or traffic segment identifier. Used to apply rules to specific segments | |
| User Profile | GEO country | Country detected from IP address. Used for regional or country-level targeting |
| IP | User IP address. Used for internal traffic filtering or fraud control | |
| Time zone | User local time zone. Used for time-based or regional delivery rules | |
| Languages | Browser language settings. Used for language specific targeting | |
| User Agent | Browser user agent string. Used for advanced device or browser identification | |
| Device Type | Type of device used by the user such as Mobile, Desktop, or Tablet | |
| Browser Type | Browser used by the user. Useful for compatibility or performance based rules | |
| Active days | Number of days the user has been active. Used to identify returning or loyal users | |
| Pageview of the day | Total pageviews for the current day. Used for frequency or engagement control | |
| Article view of the day | Number of articles viewed today. Used to identify high engagement users | |
| Article view of the week | Article views in the last 7 days. Used for weekly engagement segmentation | |
| Article view of the month | Article views in the last 30 days. Used for monthly active audience targeting | |
| Article view in total | Total article views since tracking started. Used for lifetime engagement analysis | |
| Pageview of the session | Pageviews within the current session. Used to detect deep browsing behavior | |
| Article view of the session | Article views within the current session. Used for real-time engagement based rules |
5.Delivery Scope
Delivery Scope defines where and to whom the Delivery Rule applies. You can configure Placements, Override Project, or Bidders.
In most cases, only one of these options needs to be configured, and the others can be left empty.
Placements
Select which ad units or placements the rule applies to. You can apply the rule to all placements or target specific ad units.
Use this option when the rule should affect only certain ad placements.
Override Project
Select which project this Delivery Rule should apply to instead of the default project. This option allows the rule to use a specific project configuration to override the default project behavior.
Use this option when the rule needs to be evaluated and delivered under a different project than the one originally matched.
If an override project is selected, the rule will use the settings of that project. If left empty, the default project configuration will be used.
Bidders
Control which bidders can participate when this rule is matched. You can restrict or allow specific demand sources based on your strategy.
Use this option when you want to limit or prioritize specific bidders for matched traffic.
6. Save and Publish
Once your Delivery Rule configuration is complete, click Save, then navigate back to the project overview and click Publish to activate the rule in live bidding.
Note: Only published configurations will take effect in BiddingStack.
Delivery Rules are a key component of BiddingStack's logic engine, enabling you to precisely control programmatic ad delivery. With Delivery Rules, you can filter traffic based on domain, GEO, and user attributes, divide users into groups using rules, determine which bidders can participate for each rule, and override project defaults when necessary.
Mastering Delivery Rule Sets gives you powerful control over how your ads are served, ensuring your campaigns reach the right users under the right conditions.