Skip to content

New Bidder: Epom Ad Server - #6714

Open
ruin wants to merge 7 commits into
prebid:masterfrom
epom:epom_as-bid-adapter
Open

New Bidder: Epom Ad Server#6714
ruin wants to merge 7 commits into
prebid:masterfrom
epom:epom_as-bid-adapter

Conversation

@ruin

@ruin ruin commented Aug 20, 2026

Copy link
Copy Markdown

🏷 Type of documentation

  • new bid adapter

📋 Checklist

Description

Documentation for Epom Ad Server (epom_as), a new sell-side bid adapter submitted for both
Prebid.js and Prebid Server.

Epom Ad Server is white-label: each network runs its own deployment on its own domain, so the
serving host is supplied per ad unit via params.host and the adapter posts to https://{host}/hb/bid.
Only the host is configurable — the request path is fixed by the adapter, so a page configuration
cannot redirect the auction payload. A page may mix several deployments; impressions are grouped by
host and one request goes to each.

Banner only, GVL vendor 849, TCF EU and USP signals forwarded via ortbConverter. Maintainer:
support@epom.com.

Related pull requests:

epomrnd and others added 5 commits August 20, 2026 11:52
Documentation for the epom_as bid adapter, available on both Prebid.js
and Prebid Server. Distinct from the existing epom_dsp and epom pages,
which document the buy side of the Epom platform.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…arameters

The privacy section said no cookies are sent and named withCredentials: false.
The adapter sends credentials, and has since the commit that made the ad server
answer with the request origin rather than a wildcard — so the published page
claimed the opposite of the code on the one line a privacy reviewer diffs.

channel and customParams were added to the adapter and to its module markdown
but never reached this table, which documented four of six parameters.

Server-side support is declared false until the Prebid Server adapter is
actually submitted; the frontmatter feeds the bidder table on docs.prebid.org,
and publishers would otherwise configure something that does not exist.
The page had no test block, and the example used a hostname that does not exist,
so nobody could verify the adapter without an Epom account of their own. The
placement below is kept filled for exactly this purpose.
Set to false a moment ago on the grounds that nothing was submitted yet. Putting
it back: the Prebid Server pull request goes out tomorrow, and a flag flipped off
'until then' is the kind of thing nobody remembers to flip back. The docs pull
request will not merge ahead of it.
The front matter declared no GPP support while the page's own privacy section described forwarding
regs.gpp and regs.gpp_sid. The prose was right: the adapter is built on ortbConverter, which carries
both, so the flag now names the sections it really covers.

fpd_supported was set with no First Party Data section, which the contributor guide does not allow.
The section is written rather than the flag removed, because the support is real and worth stating
precisely: custom parameters are merged into imp.ext.data, and a key already on the impression wins.

The dead userId key is gone and userIds carries a value. The parameter table documents every
constraint the params schema applies, including the ones it gained.
@netlify

netlify Bot commented Aug 20, 2026

Copy link
Copy Markdown

Deploy Preview for prebid-docs-preview ready!

Name Link
🔨 Latest commit fc9d542
🔍 Latest deploy log https://app.netlify.com/projects/prebid-docs-preview/deploys/6a8865c85755e00008b6b01e
😎 Deploy Preview https://deploy-preview-6714--prebid-docs-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

The page said both transports send the same OpenRTB payload. What is the
same is the payload Epom reads; the calls themselves differ in two ways a
publisher will otherwise meet as a surprise. A server-side call carries no
cookies, so per-user frequency capping needs user.buyeruid from a cookie
sync. And the reader's address arrives in a header the adapter forwards
from device.ip, because the connection comes from the Prebid Server host
rather than from the reader.

Also drops "the one difference" from the host paragraph, which stopped
being true once there were three.
Reordering the transport paragraphs left two blank lines before the next
heading, which markdownlint MD012 refuses.
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.

2 participants