Stacks

Overview

A stack is composed of the technical partners, ad units & settings necessary to run the appropriate monetization of a website.

Within a stack, you can select all the monetization partners you have a contract with that you wish to integrate into no-code, select the ad units that will be displayed on your website, and customize your preferences in terms of lazy loading, floor pricing rules, timeout configuration, and soon refresh rules.

A stack is always related to a single site.

Create the default stack

Once a Site setup is successfully done (as specified in Implementation), the Default stack action will be unlocked.

The Default stack creation steps are pretty straightforward:

• • Select desktop & mobile ad units

For each device, you will be asked to select at least one ad unit among the ones you already created, as documented in Ad units.

Please note that it is not possible to select two ad units with neither the same Ad server name nor the same Div ID within the same stack.

• • Set the rules applied to the stack
    • Header bidding timeout: define the Prebid timeout delay before calling the AdServer with the winning bid
    • Lazy loading: enable or disable Lazy loading on the stack, and select the rule to be used
    • Floor price: enable or disable Floor pricing rules, with the preset to be used
    • Comment: free speech section to help you keep track of the stack’s purpose
  • Save as draft or Validate

Saving the stack configuration as draft will set its status to Draft, which allows you to keep editing it without modifying the stack version currently in use. The first time you save a stack, its version will be v1.

Once satisfied with the stack configuration, you have to validate it in order to set its status to Ready to deploy and be able to move forward.

First version of the Default stack when created & validated

Note: if you edits a ‘Ready to deploy’ stack, this will archive it, and it will be replaced with an iterated version (v1 → v2, for example).

Deploy & edit a stack

When ready, any user with owner status can deploy the stack with the associated action button:

It will take a few minutes for the stack to actually be live. You will be reminded to make sure that your website is properly connected to Pubstack, with a shortcut to the associated documentation:

Once the stack is live, you have the possibility to work on an incremental version of the stack without affecting the one currently in production. To do so, you can replicate the actions done at the stack initial creation with the Edit button, and choose whether to Save a draft or Validate the new version.

Deploying a new version of the stack. The Save as draft step is optional.

As shown in the video, you can have two versions of the stack showing up in the app: the Live one, and the newly created one. It is up to an owner user to decide when to deploy the next version.

Create additional stacks

Go to a site’s page, select the “Stacks” tab and you will be able to see the different stacks currently set up.

By clicking "New stack” you’ll be brought to this page, allowing you to fill in the required information to create a new stack.

Setting stack priorities

Set stack priorities

You can choose in what order your stack are prioritized by clicking the "Edit priorities” button.

Arrow heads will then appear on the left side of each stack.

You can change the order under which each stack is selected by clicking on the upwards or downwards pointing arrows.

The default stack cannot be moved and will always be the last stack.

In this example, Pubstack will first check if the call fits into the defined context of the "test1” stack. If not, the second stack, "demo”, will be checked. And finally, if no context requirements are met, the call will pass through the default stack.

Check if your stacks are up to date

If you modify certain items in your ad stack (such as ad units, integrations, contexts and context keys), your stacks will not be updated automatically.

You will need to go see all impacted websites, who will now be “out of sync” and update them when you are ready to deploy the change.

See Deploy / Push into production