Last edited: 2024/03/27
After confirming that all technical requirements are met, we start by creating key values, technical ad unit and a set of placements - steps necessary to be done before proceeding with creating UPRs.
Yieldbird will create in GAM one additional set of key values that will be used for dividing the traffic.
New key value name: yb_ab
Key value values: a0, a1, a2, a3, a4, a5, a6, a7, a8, a9, b, c, d, e
Yieldbird will create one “phantom” ad unit called PriceGenius_Technical_Unit_do_not_remove. It will not serve any ads. Its sole purpose is to be able to properly set up Price Genius Placements (explained below).
To allow automated UPR updates using GAM’s API connection Price Genius’ pricing rules are targeted at Placements. These basically work as ad unit containers and are a purely technical thing that does not affect any aspects of your monetization.
<aside> <img src="/icons/link_yellow.svg" alt="/icons/link_yellow.svg" width="40px" /> Read more about Placements in GAM documentation
</aside>
Before starting the actual implementation, Yieldbird tech team verifies the shares of particular yb_ab key value values. If there are issues with this step, we do custom troubleshooting.
<aside> <img src="/icons/new-alert_red.svg" alt="/icons/new-alert_red.svg" width="40px" /> Attention: Do not remove nor modify Price Genius technical ad unit, key values or placements, since it will disrupt Price Genius’ operations.
</aside>
← Previous
Next →
<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" /> All these steps are performed by Yieldbird.
</aside>
On this page: