How to Create and Manage Projects
This guide explains how to create and manage projects within BiddingStack. Use this process to ensure your projects are properly configured, deployed, and ready for placement and bidding integrations.
1. Log in to BiddingStack
Access your BiddingStack account. Ensure you have the necessary permissions to create and manage projects.
2. Navigate to Projects
-
Click "Projects" in the left-hand sidebar.
-
Select "All Projects" to view the list of all existing projects.
-
Click "New Project" in the top-right corner to create a new project.
3. Fill in Project Details
Mobile environment use a simplified integration compared to Web. Some configuration options that are available in Web, such as Enable Prebid, Advanced Targeting, or Custom Ad Units, are not present in Mobile. Follow the simplified setup steps for these environments.
Basic
General project information such as project name, environment, and domain.
| Field | Purpose | Options / Configuration | Mobile |
|---|---|---|---|
| Name | Project name for identification and management. | Enter a clear project name. | ✔ |
| Environment Type | Selects the environment type to load the correct integration configuration. | Web, Mobile or AMP. | ✔ |
| Domain/App ID | The full domain of your website or moible app ID. | Enter your domain. | ✔ |
| Project Type | Defines the type for the project. | Production (production use) or Testing (for testing and debugging). | ✔ |
| Enable SPA Support | Enables support for Single Page Applications (SPA) to reload ads on route changes. | Enable if your site uses SPA frameworks. | |
| Enable CMP | Enables Consent Management Platform (CMP) to manage GDPR / CCPA compliance and user consent. | Enable if you need to collect user consent for privacy compliance. | |
| Load Pubperf | Loads Pubperf analytics script for ad performance monitoring. | Enable if using Pubperf for monitoring. | |
| Pubperf ID | Sets your Pubperf account ID to link performance data. | Enter your unique Pubperf ID provided by Pubperf. |
Categories
Select a top-level category and applicable subcategories to define your website's content type for accurate ad targeting, compliance, and performance reporting.
Demand
Setup demand channels for your project.
| Field | Purpose | Options / Configuration | Mobile |
|---|---|---|---|
| Enable Prebid | Enables Prebid.js client-side header bidding functionality. | Enable if using Prebid.js on your site. | |
| Enable Prebid Server | Enables server-side header bidding through Prebid Server. | Enable if adopting a server-side bidding setup. | ✔ |
| Bidders | Select demand partners to control which bidders compete for your inventory, helping to optimize revenue and ensure integration accuracy. | Select bidders from the dropdown list. | ✔ |
| Enable Amazon Publisher Services | Activates Amazon Publisher Services (APS / TAM) for header bidding. | Enable if you integrate with Amazon APS for bidding. | ✔ |
Settings
Configuration of your site.
| Field | Purpose | Options / Configuration | Mobile |
|---|---|---|---|
| Note | Internal note or label to identify the site | Simple text to distinguish different site setups. | ✔ |
| Currency | Sets the reporting and billing currency for the site. | Select based on your business region from the dropdown list. | ✔ |
| Prebid RTD | Describes the function and role of each RTD (Real-Time Data) module, such as identifying the module, fetching real-time data, or providing ad targeting information. | Refers to the parameters and settings available for the module, including whether it is enabled (enabled), the data source (dataEndpoint), refresh interval (refreshInterval), storage method (storage), and keys mapped to ad units (targetingKeys). | ✔ |
| Prebid Analytics | Enables Prebid Analytics with multiple providers to collect bidding and performance data for reporting and optimization. | The specific configuration is provided by the respective ad/analytics service provider. | |
| Additional CSS | Custom CSS code to apply site-specific styles or overrides. | Add custom CSS | |
| Additional JavaScript | Custom JavaScript code to run on the site for added functionality or tracking. | Insert custom JS. | |
| Only Refresh In View | When enabled, ads refresh only if they are currently visible in the user’s viewport. | Toggle ON to activate, OFF to refresh regardless of viewability. | |
| Refresh Rate (ms) | Interval in milliseconds for ad refreshes when enabled. | Define refresh interval. | |
| Label of The placeholder | Text label shown in the placeholder area before ads load or if empty. | Set placeholder label. | |
| Color of The placeholder | Background color of the placeholder area, often for visual consistency. | Defines background color of the placeholder. |
Demand Settings
Configuration of demand settings.
| Field | Purpose | Options / Configuration | Mobile |
|---|---|---|---|
| Enable Empty Ads Fallback | Displays fallback content when an ad slot cannot be filled, ensuring page layout and user experience remain intact. | Enable if you need to to display fallback content when ad slots are empty. | ✔ |
| Enable Floor Price Automation | Automatically adjusts floor prices based on performance data to maximise revenue while maintaining fill rates. | Toggle ON to enable automated floor pricing optimisation. | ✔ |
| Bid Timeout (ms) | Sets the maximum time allowed for bidders to respond. | Example: 1200 (timeout in milliseconds, e.g. 1200 ms = 1.2s) | ✔ |
| Enable Schain | Controls whether the system sends SupplyChain Object (schain) information with each bid request. | On: The bid request will include the schain field, carrying supply path transparency data. | ✔ |
| Schain | Define the actual SupplyChain Object in JSON format, which provides details of all intermediaries (SSPs, exchanges, resellers) involved in the ad impression. It is used to ensure transparency and reduce fraud. | JSON object format, e.g.: {"ver": "1.0", "nodes": [{"hp": 1, "asi": "example.com", "sid": "pub-123456789"}], "complete": 1} ver: Version (e.g., "1.0") complete: Indicates whether the supply chain is fully known (1) or partial (0) nodes: Array of entities in the chain (SSPs, resellers, etc.) | ✔ |
Advanced Settings
Configuration of advanced features.
| Field | Purpose | Options / Configuration |
|---|---|---|
| Enable Ad Free | Enable an ad-free experience for specific users or subscriptions, disabling ad delivery. | Toggle ON to activate ad-free mode for configured user groups. |
| Preload Factor | Defines the percentage of screen height at which to trigger ad requests before the ad space is visible, optimizing ad load time and improving overall page performance. | A numeric value between 0 and 100, default is 50. |
| In-View Render Factor | Defines the percentage of an ad's area that must be visible in the user's viewport for the ad to be rendered. | A numeric value between 0 and 100, default is 0. |
| Enable Keep Away Rule | Prevent ads from appearing too close together to improve UX and comply with platform policies. | Toggle ON to activate spacing rules between ads. |
| Enable Viewability KVP | Adds key-value pairs for ad viewability targeting and reporting. | Toggle ON to enable. |
| Enable Bidders Traffic Optimisation | Enables bidder traffic optimisation and activates the Max Bidders Limit and Whitelist Bidders settings. | Toggle ON to enable. |
| Max Bidders Limit | Defines the maximum number of bidders allowed to participate in each auction once optimisation is enabled. Helps reduce latency and improve efficiency. | Example: 5 (limits to 5 bidders) |
| Whitelist Bidders | Guarantees that specific bidders always receive 100% of the ad requests, bypassing ranking and optimisation rules. Ensures strategic or priority partners are not excluded. | Select bidders from the dropdown list. |
| Enable Dynamic In Content Position | Enables dynamic insertion of in-content ads based on content structure. | Toggle ON to activate. |
| Max In Content Ads per PV | Sets the maximum number of in-content ads that can appear per page view. Default: -1 (no limit). | Example: 3 (limits to 3 in-content ads per page view) |
| Dynamic In Content Margin Top | Sets the top margin (as a percentage of screen height) for dynamically inserted in-content ads. | Example: 100 (adds 100% of screen height as margin-top). |
| Dynamic In Content Density | Controls the density of in-content ads as a percentage of screen height. | Example: 100 (ads will be inserted every 100% of the screen height). |
| Insertion CSS Path | Defines the CSS selector path for targeting dynamic ad insertion positions within content. | Example: .comments. |
| Enable Consentless Ads | Enables serving ads without user consent under specific compliance configurations. | Toggle ON to activate. |
| Enable Browsing Topics | Enables Google Topics API for interest-based advertising without third-party cookies. | Toggle ON to activate. |
| Enable PAIR | Enables Google PAIR (Publisher Advertiser Identity Reconciliation) for first-party data-based targeting. | Toggle ON to activate. |
| Enable Scrolling View Mode | Adjusts ad behaviour based on user scrolling for viewability optimisation. | Toggle ON to activate. |
| Enable Publisher Audience Signals | Enables passing publisher-defined audience segments for advanced targeting. Requires Segments and Content Taxonomies to be selected. | Toggle ON to activate. |
| Enable Sticky Close Button | Keeps the close button visible on sticky ads, especially at the footer, so users can close them easily. | Toggle ON to enable the close button. |
4. Click "Save Changes" to Create the Project
This stores the configuration in the platform and generates a unique project ID.
5. Click "Settings" to Edit or Delete the Project
-
General: Update basic details like the project name, environment, domain, and general settings.
-
Install: View ad tag installation instructions and script code snippets, including the project ID. Enable users to complete ad integration easily on both web (desktop) and mobile platforms, ensuring the project ID is correctly configured for ad delivery, tracking, and reporting across all devices. For mobile integration, request the mobile SDK from your account manager and follow the provided instructions to implement it in your app or mobile site.
6. Click "Publish" to Deploy
This pushes the project configuration to the live ad stack and makes it available for request handling.
Once published, the version number is updated to the latest. All changes must be published to take effect.
7. Create a Child Project
Child Projects enable independent management, hierarchical organization, and efficient operations across multiple projects. They can be used for environment-specific overrides or to test variations while maintaining a shared parent configuration.
You can create a child project in two ways:
- From the navigation bar: Click "New Child Project". Fill in the details and save.
- From an existing parent project: Click "Duplicate to Child" to inherit configurations and quickly create a child project, reducing repetitive work and improving efficiency. Make the necessary changes and save.
Summary
By following these steps, you can successfully create, configure, and deploy projects within BiddingStack.
Always ensure project details and settings are accurate before publishing, as each update affects live bidding behavior and ad delivery.