Skip to content
Closed
Changes from 4 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
41 changes: 41 additions & 0 deletions dev-docs/bidders/adpixis.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,41 @@
---
layout: bidder
title: AdPixis
description: Prebid AdPixis Bidder Adaptor
biddercode: adpixis
pbjs: false
pbs: true
media_types: video, banner
userIds: all
fpd_supported: false
tcfeu_supported: false
usp_supported: true
coppa_supported: true
schain_supported: true
prebid_member: false
ortb_blocking_supported: true
multiformat_supported: will-bid-on-one
floors_supported: false
aliasCode: limelightDigital
sidebarType: 1
---

### Bid Params

{: .table .table-bordered .table-striped }

| Name | Scope | Description | Example | Type |
|:--------------|:---------|:--------------------------------------------------------------|:-----------------------|:----------|
| `host` | required | Ad network's RTB host | `'<adserving domain>'` | `string` |
Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor

Choose a reason for hiding this comment

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

The comment below suggests that 'host' is only needed for Prebid.js, but the metadata field says pbjs: false. Something's off.

Copy link
Contributor

Choose a reason for hiding this comment

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

@bretg thanks for your comments, we will fix everything, about the host - we use it only as query parameter for PBS to identify the publisher on our side
https://github.com/prebid/prebid-server/blob/master/static/bidder-info/limelightDigital.yaml#L1

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Copy link
Contributor

@bretg bretg Mar 31, 2025

Choose a reason for hiding this comment

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

Sorry, 'host' isn't fixed. PBS does not allow any kind of domain (e.g. adpixis-rtb.com) as a required parameter. It's ok to be an optional parameter, so the adapter has to have a reasonable default.

The way to think about this is from the publisher's perspective:

  1. It's lazy to assume that your publisher customers can geo-balance your endpoints
  2. It's unreasonably duplicative to make them pass something like this to the limelight endpoint just to identify the alias.

The way you need to do that is to just hardcode the alias domain in your YAML file. e.g.

"http://ads-pbs.ortb.net/openrtb/{{.PublisherID}}?host=adpixis-rtb.com"

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed. I've set Host to optional

Copy link

Choose a reason for hiding this comment

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

Is this "host" parameter different for each customer? Different for each request?

I do like the idea of renaming this because "host" has a meaning that may not be relevant here. However, you already have a "PublisherId" parameter. How would "publisher" differ from "publisherId"?

@apykhteyev can you please address these questions?

Copy link

Choose a reason for hiding this comment

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

The limelight digital adapter, which adpixis is an alias of, still has host as required despite the documentation change here to optional.

Host does not correspond to the bidder domain, though I imagine it is being used to route requests internally somehow. Is that the case @apykhteyev? If that is true, @bretg does this really have to be optional?

Copy link
Contributor

Choose a reason for hiding this comment

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

The important thing is that we do not force publishers decide how to route each request. I agree the 'host' parameter is misnamed if it's just something like an account ID.

Copy link
Contributor

Choose a reason for hiding this comment

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

@bretg @bsardo we did host parameter optional as you requested for this adapter. Even I can remove it from here it all, but I can't make it optional for our limelight digital adapter.

Let me try to explain our business.

We offer our RTB solution as SaaS for multiple clients and they use our infrastructure. Most of our clients request whitelabel domain and whitelabel pbs adapter. So it's ok we can create this alias and we don't require this host parameter and it's enough to have just publisherId

But some of clients don't need whitelabel solution and use our default domain ortb.net. So internally we use their client dedicated subdomain to differentiate request from different clients. Different clients could have same publisher ids, that why just publisherId is not enough for main limelightDigital adapter. As PBS don't allow to use dynamic subdomain - we moved this host to query parameters, and use it internally to understand what's client send us request from regular limelightAdapter. Our main adapter don't use host for any rerouting and just pass it as is for backend processing

And as I said we remove host from whitelabeled version. Hope it clarifies. Let me know for any questions

| `adUnitId` | required | Ad Unit Id will be generated on <Public title name> Platform. | `42` | `integer` |
| `adUnitType` | required | Type of Ad Unit (`'video'`, `'banner'`) | `'banner'` | `string` |
| `publisherId` | required | Publisher ID | `'12345'` | `string` |
| `custom1` | optional | Custom targeting field 1 | `'custom1'` | `string` |
| `custom2` | optional | Custom targeting field 2 | `'custom2'` | `string` |
| `custom3` | optional | Custom targeting field 3 | `'custom3'` | `string` |
| `custom4` | optional | Custom targeting field 4 | `'custom4'` | `string` |
| `custom5` | optional | Custom targeting field 5 | `'custom5'` | `string` |

<Public title name> server-side Prebid Server adapter requires only `publisherId` and `host` parameters. But <Public title name> client-side Prebid.js adapter requires only `host`, `adUnitId`, `adUnitType`.

<Public title name> server-side Prebid Server adapter supports only `banner`, `video`, `audio`, `native` media types. But <Public title name> client-side Prebid.js adapter supports only `banner` and `video` media types, doesn't support `audio` and `native`.