-
Notifications
You must be signed in to change notification settings - Fork 749
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Smarthub: Update to Attekmi Endpoint #4047
base: master
Are you sure you want to change the base?
Smarthub: Update to Attekmi Endpoint #4047
Conversation
Code coverage summaryNote:
smarthubRefer here for heat map coverage report
|
Code coverage summaryNote:
smarthubRefer here for heat map coverage report
|
We discussed this in committee. Renaming an adapter is covered in the FAQ -- https://docs.prebid.org/faq/prebid-server-faq.html#how-can-we-rename-our-bid-adapter Please add attekmi as an alias of smarthub. It's confusing for publishers to navigate re-brandings without a transition period where both old and new names are available. |
Attekmi cannot work as an alias, does that mean we have to create a completely new adapter like Smarthub? |
It certainly could if you wanted it to. You started this thread with "We change adapter name from Smarthub to Attekmi". Maybe we should step back and confirm what you're actually doing here. This PR just changes the URLs and the titles, but doesn't actually attempt to get rid of the 'smarthub' biddercode. Let's make sure we're on the same page about what's important, which is that all of your publisher customers have coded their pages/stored requests with the 'smarthub' biddercode. They've also set up build processes that include and enable the 'smarthub' adapter. What Prebid is picky about is forcing publishers to change either their pages or their build processes outside of a major release. That's called a 'breaking change'. So question - are you going to be asking your customers to change their pages to replace 'smarthub' with 'attekmi'? That's most rebranders want to do, which is why we ask for aliases. This way, you can start transitioning publishers to the new brand but nothing breaks for those who are too busy to change. If you're just changing the technical DNS endpoints, then there would be no need to change the branding in some of these files. The docs PR covering this suggests that attekmi is intended to be used a biddercode. Some rebranders don't worry about changing the biddercodes. For instance, the companies 'rubicon' and 'appnexus' haven't existed for many years, but that's still what the bid adapters are called. The fact that 'Magnite' and 'Microsoft' own these biddercodes is mentioned in the documentation, but there's no separate docs files for them. |
Thanks for the detailed answer! In this PR we only change the URLs and titles and leave the 'smarthub' biddercode. Our clients use and will continue to use the 'smarthub' biddercode. We are not going to ask our clients to change the current biddercode. We are aware of the experience of other partners, thank you for the clarification. |
Code coverage summaryNote:
smarthubRefer here for heat map coverage report
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am asking you to have a transition period where people can get used to your rebranding... at least through a major release. i.e. publishers and host companies should not have to be aware of this rebranding for things to work or to find documentation. I view this as no different than appnexus/MicroSoft and rubicon/Magnite.
static/bidder-params/smarthub.json
Outdated
@@ -1,12 +1,12 @@ | |||
{ | |||
"$schema": "http://json-schema.org/draft-04/schema#", | |||
"title": "SmartHub Adapter Params", | |||
"description": "A schema which validates params accepted by the SmartHub adapter", | |||
"title": "Attekmi Adapter Params", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"title": "Attekmi Adapter Params", | |
"title": "Attekmi (formerly SmartHub) Adapter Params", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I changed title
static/bidder-params/smarthub.json
Outdated
"title": "SmartHub Adapter Params", | ||
"description": "A schema which validates params accepted by the SmartHub adapter", | ||
"title": "Attekmi Adapter Params", | ||
"description": "A schema which validates params accepted by the Attekmi adapter", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"description": "A schema which validates params accepted by the Attekmi adapter", | |
"description": "A schema which validates params accepted by the Attekmi (formerly SmartHub) adapter", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I changed description
static/bidder-params/smarthub.json
Outdated
"type": "object", | ||
"properties": { | ||
"partnerName": { | ||
"type": "string", | ||
"description": "SmartHub unique partner name", | ||
"description": "Attekmi unique partner name", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"description": "Attekmi unique partner name", | |
"description": "Attekmi (formerly SmartHub) unique partner name", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No problem. I changed description
Code coverage summaryNote:
smarthubRefer here for heat map coverage report
|
We change adapter name from Smarthub to Attekmi,
changing endpoints but keep biddercode 'smarthub'
Docs PR prebid/prebid.github.io#5699