For Prebid.JS
This page is for the integration of Prebid Server connections only. A Prebid.JS guide will be released in the near future for Prebid.JS connections.
Specification Support
Specification | Version | Last Update Date | Notes |
---|---|---|---|
Prebid Server | 3.18.0 and above |
| 3.18.0 is the minimum Prebid Server Version that embeds the fwssp adaptor |
IAB Content Category Taxonomy | v1 |
| IAB Content Categories are mapped to FreeWheel Global Industries |
Guide Change Log
Current Guide Version
Guide Version | Date | Author | Description |
---|---|---|---|
v1 |
| Admin | Initial Release |
Historic
Table of Contents
1. Introduction
SFX has provided tech resources in order for publishers to integrate with the Prebid Server Framework. This is an open source framework that allows publishers to integrate with demand sources in a plug and play type fashion and with less complexities than other integration methods.
With the sunsetting of SFX, any customers using an existing Prebid Server Integration will need to complete a new adaptor integration in order to migrate to their new FW SSP network. This page outlines the integration steps for publishers to complete these steps.
1.1 Integration Diagram
1.2 Pre-Requisites
Before starting this integration, please ensure you have the following to start:
- Existing connection to a Prebid Server provider using PBS-Go
- There are two implementation types of Prebid Server: PBS-Go and PBS-Java. Freewheel currently does not support PBS-Java.
- Expected QPS volumes (daily max and average)
- Estimated traffic per geo
- Ensure ads.txt and app ads.txt are up to date
- Must use the adaptor released in Prebid Server version 3.18.0 or above
- New endpoint url - see section below
- Freewheel account team to provide:
- Profile ID
- Network ID
- Custom site section ID
2. How to add the new FW Prebid Server Adaptor
The new Freewheel adaptor is named fwssp. This new Prebid Adaptor will work in parallel to the existing SFX adaptors whilst the migration of clients is complete. Then the FW SSP Adaptor is going to replace the SFX instances of freewheel-ssp and freewheelssp adaptors in the future once SFX is deprecated.
Note that the SFX adaptors will be deprecated later in 2025 once all clients have migrated to their new networks. After this date clients will no longer be able to use them
3. Endpoint
The following dedicated endpoint is what will be used for Prebid Server traffic to Freewheel and is hardcoded into the fwssp Prebid Server Adaptor config file:
4. New Parameters
With the release of the new adaptors, there will be a need for certain parameters to change versus those used previously on SFX in order to meet the requisites of the new FW SSP platform. This is due to differences in architecture and concepts between the two platforms
FW SSP Parameter | Description |
---|---|
profile_id | A profile is used to determine and control what type/formats of ads can serve into a particular inventory type e.g creative specs. This is set up on the backend and the value to implement will be provided by your Freewheel account team The expected format is the name of the profile as a string and not a numerical ID |
network_id | The network ID is the ID of the customer account or instance, known as a 'network'. The value to implement will be provided by your Freewheel account team. The expected format is a numerical string. SFX Note Networks are similar concept to SFX Private Exchanges (PX). |
custom_site_section_id | The site section (id) determines the exact piece of inventory where the ad request is coming from as designed in your network design. You may have one or many different site sections breaking out inventory depending on what network design was agreed upon with your Freewheel account team. The value to implement will be provided by your Freewheel account team. The expected format is either the tag or the numerical ID of the site section. SFX Note Site Sections are a similar to the concept of SFX Zones, however unlike zones, the ad unit is separated from the site section and the site section agnostic of what type of ad unit is being used. |
5. Config Code
If you need access to the adaptor code, you can view it on the following Github repository.
6. User Syncing/Cookie Syncing
Starting from the 7.11 release on 8/25/2025, we'll have the ability to handle cookie syncing for Prebid Server clients, until then user/cookie sync will not be able to function via the fwssp Prebid Server Adaptor. The code to manage this will be integrated into the adaptor code including the sync pixel. Each Prebid Server instance will be able to retrieve the FW cookie ID via the sync pixel and use it to populate the user.buyerid in the outgoing ad request to Freewheel. This will then be used downstream to check if we have a cookie match with the DSPs as we send outgoing bid request.
The expectation is the the upstream adserver will host the user match table in-between your cookie ID and the Freewheel Cooke ID.
7. Schain/Sellers JSON
The populating of the Schain will be handled via the Prebid Server. Your Freewheel account representative will provide you with the required codes to enter in your ads.txt and ensure that your new publisher IDs are added into our sellers.JSON as an onboarding step. This schain object will be passed in the ext.schain object of the ORTB ad request - refer here to the ORTB-S Integration Guide section 5.10.
8. Ads.txt/app ads.txt
Link to the new Hub guide for FW SSP - still pending publication on https://hub.freewheel.tv/display/MUG/ads.txt+and+app-ads.txt+setup.
9. Passing Contextual information
In order to successfully monetize your supply and align all relevant demand, we'll require clients to correctly pass contextual information around the supply. The section below details the fields required to pass the needed information for ORTB ad requests:
For the most optimal monetization, clients should pass at a minimum Programmer, Brand, Channel and Genre. If these aren't passed, Freewheel may not be able to effectively monetize the supply.
10. ORTB type ad Request Body
Please refer to section 5 of our OpenRTB Supply Integration Guide for the current list of supported ORTB fields. Note that there will often be new fields added to this section.
11. Troubleshooting Tips
Since integrations often break due to typos, errors in config, we highly recommend checking the format of your requests based on the samples below or the documentation housed on Github. Please also ensure that you use the correct adaptor - fwssp and not another adaptor.
11.1 Sample ad requests and responses
Please refer to the below code blocks which pass the expected parameters as a guide and to sanity check the code