Updating the site to begin the Appnexus adpater by jasonc721 · Pull Request #6627 · prebid/prebid.github.io

jasonc721 · 2026-06-17T20:10:13Z

Pages updated to reflect the move to the MSFT adapter.

🏷 Type of documentation

text edit only (wording, typos)

decpreatction and to rename elements to Microsoft.

netlify · 2026-06-17T20:10:17Z

✅ Deploy Preview for prebid-docs-preview ready!

Name	Link
🔨 Latest commit	`ba40943`
🔍 Latest deploy log	https://app.netlify.com/projects/prebid-docs-preview/deploys/6a32ff2892a2db0008bbce71
😎 Deploy Preview	https://deploy-preview-6627--prebid-docs-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

jasonc721 · 2026-06-17T20:15:42Z

Hi @jsnellbaker and adrianmason@microsoft.com, please review.

PBDMSFT · 2026-06-18T14:04:32Z

 <amp-ad width="300" height="250"
    type="doubleclick"
    data-slot="/1111/universal_creative"
-    rtc-config='{"vendors": {"prebidappnexuspsp": {"PLACEMENT_ID": "13144370"}}, "timeoutMillis": 500}'>


@jasonc721 We actually have not changed our AMP vendor registration so please revert this to keep "prebidappnexuspsp".

To clarify why: prebidmsftpsp is not registered in the amphtml callout-vendors registry (src/service/real-time-config/callout-vendors.js). The only Prebid PSP vendors currently in that file are prebidappnexuspsp, prebidflux, prebidopenx, and prebidrubicon. No PR to ampproject/amphtml adding prebidmsftpsp exists. An unrecognized vendor name is silently ignored by the AMP runtime — all RTC callouts would be dropped and no bids returned. The registration in amphtml must come first.

— Claude

jsnellbaker · 2026-06-18T14:13:38Z

 fpd_supported: false
 pbjs: true
-pbjs_version_notes: please avoid using v7.15 and v7.16
+pbjs_version_notes: Support for the AppNexus adapter will be reduced beginning July 1, 2026, with full deprecation planned for early 2027. To maintain uninterrupted support and access to the latest features, please migrate to the [Microsoft adapter](msft.md).


I'm not sure we should include a link here - it may not render correctly on the download page.

jsnellbaker · 2026-06-18T14:15:18Z


    ```bash
-    gulp serve --modules=rtdModule,appnexusBidAdapter,rubiconBidAdapter,sharethroughBidAdapter,contxtfulRtdProvider
+    gulp serve --modules=rtdModule,msfgtBidAdapter,rubiconBidAdapter,sharethroughBidAdapter,contxtfulRtdProvider


jsnellbaker · 2026-06-18T14:19:48Z

-        bidders : ['appnexus','pubmatic', 'rubicon'],
-        defaultVendor: 'appnexus',
+        bidders : ['msft','pubmatic', 'rubicon'],
+        defaultVendor: 'msft',


just in case here - use appnexuspsp instead of msft

The issue here is deeper than the vendor name. The defaultVendor vendor map (S2S_VENDORS in modules/prebidServerBidAdapter/config.js) was removed entirely in Prebid.js 10.0. In the current codebase, defaultVendor is only used for metrics key naming — it no longer configures any endpoint. So defaultVendor: 'appnexus' is a no-op in Prebid 10+, not just defaultVendor: 'msft'.

The right fix for this section is to remove the defaultVendor examples and the 'Currently supported vendors' note and replace them with explicit endpoint config. The Microsoft PSP integration doc already shows the correct form:

pbjs.setConfig({ s2sConfig: { accountId: YOUR_SELLER_MEMBER_ID, bidders: ['msft'], enabled: true, allowUnknownBidderCodes: true, timeout: 1000, endpoint: { p1Consent: 'https://ib.adnxs.com/openrtb2/prebid', noP1Consent: 'https://ib.adnxs-simple.com/openrtb2/prebid' }, syncEndpoint: { p1Consent: 'https://prebid.adnxs.com/pbs/v1/cookie_sync', noP1Consent: 'https://prebid.adnxs-simple.com/pbs/v1/cookie_sync' } } })

The defaultVendor approach section in this doc was stale before this PR touched it — this is a good opportunity to clean it up.

— Copilot

that's the better fix

jsnellbaker · 2026-06-18T14:19:54Z

-          bidders: ['appnexus','pubmatic'],
-          defaultVendor: 'appnexus',
+          bidders: ['msft','pubmatic'],
+          defaultVendor: 'msft',


just in case here - use appnexuspsp instead of msft

jsnellbaker · 2026-06-18T14:20:02Z

    accountId: '1',
    bidders: ['tripleliftVideo'],
-    defaultVendor: 'appnexus',
+    defaultVendor: 'msft',


just in case here - use appnexuspsp instead of msft

jsnellbaker · 2026-06-18T14:20:52Z

 ## Configuration

-Here's an example config enabling the AppNexus Prebid Server:
+Here's an example config enabling the Microsoft Prebid Server:


just in case here - use appnexuspsp instead of Microsoft

jsnellbaker · 2026-06-18T14:26:12Z

  height="1"
  sandbox="allow-scripts allow-same-origin"
  frameborder="0"
-  src="https://acdn.adnxs.com/prebid/amp/user-sync/load-cookie.html?endpoint=appnexus&max_sync_count=5&source=amp">


this change should probably be undone as well.

Confirmed, this should be reverted. The endpoint= parameter is validated against a VALID_ENDPOINTS map in prebid/prebid-universal-creative's src/cookieSync.js, which currently only registers two values:

const VALID_ENDPOINTS = { rubicon: 'https://prebid-server.rubiconproject.com/cookie_sync', appnexus: 'https://prebid.adnxs.com/pbs/v1/cookie_sync' };

endpoint=msft would fail sanitization and the user-sync iframe would make no requests, silently breaking cookie sync for AMP. A PR to prebid/prebid-universal-creative adding msft to VALID_ENDPOINTS is a prerequisite before this doc change is valid.

— Claude

jsnellbaker · 2026-06-18T14:29:09Z


 Select your Prebid Server host:

- *AppNexus*


This page is tied to a 3rd party browser extension, so the name change to Microsoft may not be reflected fully. We may want to either leave this or have some thing that includes both like AppNexus (Microsoft).

jsnellbaker · 2026-06-18T14:33:29Z

+        "placement_id": 123
      },
      "districtm": {
        "placementId": 456


may want to change to placement_id - if we keep the msft alias in this example

jsnellbaker · 2026-06-18T14:35:09Z

 ```

 {: .alert.alert-info :}
-**Note:** the `prebidrubicon` and `prebidappnexuspsp` AMP vendor strings define slightly different parameters; AppNexus uses "PLACEMENT_ID" as the argument to rtc-config while Rubicon uses "REQUEST_ID". They both translate to `tag_id` when passed to Prebid Server.


another area to review as it's AMP related

Same root cause as the show-prebid-ads-on-amp-pages.md change: prebidmsftpsp is not registered in ampproject/amphtml's src/service/real-time-config/callout-vendors.js. The note should keep prebidappnexuspsp until the amphtml vendor registration is in place. The fix for this and the rtc-config example in show-prebid-ads-on-amp-pages.md are blocked on the same upstream PR to amphtml.

— Claude

jsnellbaker · 2026-06-18T14:37:41Z


    - rubicon-storedresponse.json - this is a request that calls for a stored-auction-response.
-    - appnexus-disabled-gdpr.json - this is a request that actually calls the appnexus endpoint after disabling GDPR by setting regs.ext.gdpr:0
+    - msft-disabled-gdpr.json - this is a request that actually calls the msft endpoint after disabling GDPR by setting regs.ext.gdpr:0


@PBDMSFT do you happen to know if a rebranded file was created for this setup?

If not - we may need to keep the name

Checked the PBS Java repo (prebid/prebid-server-java): no msft-disabled-gdpr.json file exists in sample/requests/. The rename here is invalid. This reference should be reverted to whatever filename currently exists in that repo — if appnexus-disabled-gdpr.json is also absent, the doc reference should be removed rather than changed to a non-existent filename.

— Claude

Updating the site to begin the Appnexus adpater

ba40943

decpreatction and to rename elements to Microsoft.

PBDMSFT reviewed Jun 18, 2026

View reviewed changes

jsnellbaker reviewed Jun 18, 2026

View reviewed changes

Conversation

jasonc721 commented Jun 17, 2026

🏷 Type of documentation

Uh oh!

netlify Bot commented Jun 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for prebid-docs-preview ready!

Uh oh!

jasonc721 commented Jun 17, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

PBDMSFT Jun 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

netlify Bot commented Jun 17, 2026 •

edited

Loading

PBDMSFT Jun 18, 2026 •

edited

Loading