Skip to content

Conversation

@arezitopedia
Copy link
Contributor

Type of change

  • Bugfix

  • Feature

  • New bidder adapter

  • Updated bidder adapter

  • Code style update (formatting, local variables)

  • Refactoring (no functional changes, no api changes)

  • Build related changes

  • CI related changes

  • Does this change affect user-facing APIs or examples documented on http://prebid.org?

  • Other

Description of change

As part of the transition to the new Microsoft adapter, we kindly request that our original alias (code) from the AppNexus adapter be ported to the new Microsoft adapter to ensure continuity and consistency in bidder configuration and reporting. We propose using the new alias name "oftmsft" to prevent any conflicts with the existing alias associated with the legacy adapter during transition.

Other information

@jsnellbaker @dgirardi

Copilot AI review requested due to automatic review settings November 11, 2025 17:55
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds the '152media' (oftmedia) bidder alias 'oftmsft' to the Microsoft (msft) bidder adapter to support the transition from the legacy AppNexus adapter. The alias uses gvlid 32, consistent with the original 'oftmedia' alias configuration.

  • Adds 'oftmsft' alias with gvlid 32 to the msftBidAdapter
  • Maintains continuity for 152media's bidder configuration during the Microsoft adapter transition

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
@patmmccann patmmccann changed the title Add 152media alias to Microsoft New Adapter Microsoft Adapter: Add 152media alias Nov 12, 2025
@jsnellbaker jsnellbaker self-assigned this Nov 12, 2025
@jsnellbaker
Copy link
Collaborator

@arezitopedia I checked internally with others on this request; I believe there were separate conversations, that we wanted to wait before adding new aliases for the msftBidAdapter.

At this point, we may be okay to proceed with aliases, but there was an internal request for the alias to be a transfer (from appnexus to msft) instead of creating a second alias just for msftBidAdapter.

Is this something you'd be willing to do with this PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants