MobileFuse Adapter: Remove pub_id query param for Simplified Partner ID Setup #6003
Closed
tomaszbmf wants to merge 2 commits into
Closed
MobileFuse Adapter: Remove pub_id query param for Simplified Partner ID Setup #6003tomaszbmf wants to merge 2 commits into
tomaszbmf wants to merge 2 commits into
Conversation
✅ Deploy Preview for prebid-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
ChrisHuie
approved these changes
May 2, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This update to the Prebid documentation reflects the removal of the
pub_idquery parameter, which was previously necessary only whentagid_srcwas used. Sincetagid_srchas been removed in the linked Prebid Server PRs, thepub_idquery parameter is no longer needed. This change simplifies the Partner ID setup and ensures the documentation stays aligned with the current implementation.🏷 Type of documentation
📋 Checklist