You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some clients uses alias in order to call multiple seat from AppNexusAst adapter (each seat belonging to a different monetization partner from the publisher).
Alias works fine for client side implementation.
However, alias aren't compatible with server side implementation at the moment.
Having support for server side for alias would allow to optimize performances for those AppNexus partners, as one single call would be made instead of current multiple calls. Also using AppNexus hosted prebid server solution would allow not to impact cookie sync, so only benefit for people having multiple AppNexus partners.
The text was updated successfully, but these errors were encountered:
Yes... this actually duplicates #11, and will be coming soon.
@jdelhommeau Just to be clear, which types of prebid.js aliases are important to you? Some are static in the code (defined by adapters themselves), and others can be defined by the publisher page through $$PREBID_GLOBAL$$.aliasBidder.
Some clients uses alias in order to call multiple seat from AppNexusAst adapter (each seat belonging to a different monetization partner from the publisher).
Alias works fine for client side implementation.
However, alias aren't compatible with server side implementation at the moment.
Having support for server side for alias would allow to optimize performances for those AppNexus partners, as one single call would be made instead of current multiple calls. Also using AppNexus hosted prebid server solution would allow not to impact cookie sync, so only benefit for people having multiple AppNexus partners.
The text was updated successfully, but these errors were encountered: