Table of contents:
Updates and additions to your integrations will not be deployed automatically.
You will need to Deployment the changes for them to be applied.
If any of your integrations are not present in the pubstack catalog, please contact us so we can add them to the platform.
Integrate demand into your Pubstack Catalog
Overview
The purpose of integration catalog is to provide you with a solution to easily and quickly integrate all the monetization partners you have a contract with that you wish to integrate into no-code and make you able to autonomously manage your stack.
Access
The catalog integration are accessible for ad management customers at the following url https://app.pubstack.io/adstack/integrations
This screen displays the list of 3rd party partners that publishers can add and configure to his stack.
There are bidders, Prebid modules, Amazon TAM wrapper and Ad server.
The first tab “My integrations” displays active partners. The second one displays all available partners in Pubstack’s catalog that could be integrated.
A search bar is here to ease navigation and a filter by integration type can be applied.
Add and configure new partner
You can easily access a partner’s configuration settings by clicking on a card. Pubstack will offer to integrate Prebid bidders, Prebid modules (Real Time Data, identity…), Ad servers( Google Ad Manager), and wrappers (TAM).
Example when clicking on Xandr:
To learn how to continue the configuration per demand type see the following categories:
Bidder
Overview
To allow you to easily map your inventory to a bidder, the interface will offer you to download a .csv (comma separated value) template prefilled with all your ad unit information.
For most of the bidders, only the required parameters need to be filled in. This is a common way for publishers to handle new bidders. In the future, Pubstack will propose to enrich integrations with optional parameters.
Access
From the catalog interface in the integration section, simply select any partner to be redirected to its specific integration settings.
Example for Xandr:
Create an alias
You can use aliases for bidders for different purposes. However, it is completely optional.
If needed, on the top right on the screen, you can Create an alias by clicking on the corresponding button.
You can name an alias for any bidder adapter.
You can create as many aliases as needed. Pubstack will generate a file mapping based on each new alias name.
As of now, an alias cannot be deleted without Pubstack support, but you can still remove all data in its mapping to render it inactive.
Download and edit template
To configure a bidder, you can click on download template. Pubstack will generate a .csv file with prefilled columns: site, device, ad units and bid parameters according to bidder specificities. Data will be automatically populated from what you have configured in Pubstack app.
The file can be opened and edited by various tools like excel, google sheet, notepad… But be careful, do not modify the file format.
The structure of the file must not be modified either. No rows, columns or headers must be modified, added or deleted. For each row, you must only set the bid parameters related to the bidder requirements.
Example for Xandr bidder:
For google sheet:
-
- Go to File > import
- Click on the tab upload >browse
- Select your csv file and open it
- Click on import data
- Add your parameters
- Then once it’s done, go to File > download > comma separated values(.csv)
- Your file is ready to be uploaded in Pubstack
For Microsoft Excel:
-
- Go to File > Open
- Select your csv file and click Open
- Add your parameters
- Then once it’s done, go to File > Save As
- Make sure that your file format is .csv
- Click Save
- Your file is now ready to be uploaded in Pubstack
Headers
| pbstck_Adapter Name | pbstck_site | pbstck_device | pbstck_adunit |
|---|---|---|---|
| Alias Name/Bidder Name | Site name | Device name | Ad Unit name |
- pbstck_adapterName= alias name filled in bidder configuration screen by a field. If empty, by default Adapter name=Bidder Name
- pbstck_site = site name defined in Pubstack app at company level
- pbstck_device = device name defined in Pubstack app at scope level and associated to the site
- pbstck_adunit = name used across Pubstack to define the ad unit associated to device. The ad unit must be eligible for header bidding
- bid params = will be named by the specific name of bid params requested by the bidder. For example Xandr has placementId as param.
If a bid parameter is left empty on one row, the bidder will not be configured and no ad request will be sent to the partner.
To delete configuration for an ad unit, you can simply to empty the cells containing the bid parameters for that unit.
In short, if Pubstack should call a bidder for a site x device x ad unit, just fill in the bid parameters, otherwise leave it blank.
Upload new mapping
Once the template is completed, you can upload it by clicking the button. At this step, Pubstack will check the file before validating the configuration. Checks are performed to ensure file integrity, bid parameters related to bidder or adapter name.
If everything is correct, the upload process will continue and the bidder mapping for the publisher's inventory can be applied. The mapping will be set to "mapped".
Once this process is done, sites using the mapped ad units will be out of sync, and will need to go under deployment again to apply the changes.
Download current mapping
Once you have uploaded a valid mapping file, you can download current version by clicking on the button. The downloaded file is prefilled by all current parameters, new sites and ad units and can easily be modified and re-uploaded to change your mapping.
Module
Overview
To deal with many specific modules configurations, Pubstack offers a simple way to allow you to configure modules for your stack. The catalog offers Identity and Real Time Data(RTD) types of modules, which are parts of Prebid that can be added to your stack.
Access
From integrations menu, in the catalog, a list of available modules is displayed. You can click on a card to configure the module.
Configuration
For each site, you can configure a module by filling in the parameters in the json text area. For example for the ID5 module, only the partner parameter is required. You can simply fill in the partner ID and validate. Pubstack will then automatically add this module and configuration to the site.
You can also add some optional parameters related to documentation of 3rd party partners if needed.
Be careful with the form. It is under json format and syntax is really important.
Any error will be caught and prevent you from validating the configuration.
Google Ad Manager
Overview
Google Ad Manager is the most popular and adopted Ad Server solution of the market. As a main component of an Ad stack, it offers publishers a complete ad revenue engine, helping publishers streamline operations and capture the most value for every impression. This documentation helps you to configure your Google Ad Manager integration for your site from Pubstack.
Access to GAM configuration
From the catalog integrations select Google Ad Manager(GAM) card to access configuration settings.
Configure Network Id
The network Id code is a unique, numeric identifier for an Ad Manager network. This network Id code is used to build the Ad request to Google Ad Manager. You can get it directly on your Google Ad Manager account.
The network Id code is unique for Pubstack scope. You can simply fill the field and save. You can then click on the edit button if needed to modify it.
The list of ad managed sites belonging to your scope is now displayed below. You can manage each site configuration (adUnitPath and MCM ids) by unfolding it.
Configure a site
Define ad unit path
You must provide to Pubstack with the structure of your inventory you are using to help properly handle requests to your Ad Manager network.
How can I define the ad unit path?
The prerequisite to define the ad unit path is to declare ad units and context keys on the Pubstack platform (see Ad units and Before creating a context, you’ll need to define the necessary context keys to set its conditions ).
You can then define your ad unit path structure by:
-
-
Using both context keys and Ad server ad unit name
-
Below each
selection box, an example value (default one if set) is displayed from your selection. -
eg: the context key architecture ContextKey_1 / ContextKey_2 / AdServerAdUnitName gives the example value path of site_name / inventory_type / MyAdUnit.
-
-
-
-
Using only context keys If you don’t have an explicit ad unit to target in your GAM (with Ad server ad unit name), Pubstack will send targeting keys to the ad server based on the ad unit name and key values defined in the ad unit settings.
-
In that case, the ad unit path will be ContextKey_1/ContextKey_2/ContextKey_3
(ex: site_name/inventory_type/section)
You can define your ad unit path structure from 1 level to max 5 level.
Ad Server Ad unit name must be the last level of structure so no more levels can be added after, but you can remove it to add an additional level before then add it again
You can add a level by using the corresponding button or delete one easily by clicking on the bin icon.
Do not forget to save any change for both MCM id and ad unit path.
What do I need to declare if I use different levels for the ad unit path on the same site?
If you manage a site for which you have some specific sections where you have a different levels of ad unit path, you have to define the longest one you currently use on your Ad Manager network.
Pubstack will be able to deal with N levels and N+1 levels. Even is the last level is missing on the page, Pubstack will call the ad unit in GAM with the right path.
Define MCM ID(Multiple Customer Management) (optional)
You can delegate management of your Ad Manager network to a third-party publisher upon request and establish a parent-child relationship.
To be compliant with this delegation for Google, the Ad unit path declared in Google Publisher Tag must contain explicitly this link.
You may not need to fill in this information, but if you have a delegated relationship with a third party, you must define it otherwise the inventory cannot be monetized. You can get it on your Ad Manager account.
You can click on each site to expand it and fill MCM Id if needed.
