# Implementations | Publisher/web | Adserver | Adserver endpoint | HB | Adserver key | Flagship | |------------------|---------------------|-------------------|------------|----------------------------|--------------------------| | mafra | their paticka (sas) | a.1gr.cz | our prebid | ElementId | idnes.cz | | csfd | their sastracker | a.csfd.cz | our prebid | ElementId | csfd.cz | | vlm | their sastracker | a.denik.cz | our prebid | ElementId | denik.cz | | eco | their sasic (sas) | a.centrum.cz | our prebid | AdUnits | aktualne.cz / hn.cz | | prima | their sas.js | a.iprima.cz | our prebid | .sas_mone data attributes | echo24.cz | | iinfo | their gam | | our prebid | ElementId | mesec.cz | ## Mafra Format rendering: We are calling Mafra format rendering functions, from mafra publisher module. ### HB service creative ``` ``` ## CSFD, VLM SAStracker library has a function in the adserver response that calls our render. That returns true (CPEx should render) or false (SAStracker should render) based on format catching and allowedSSPs: ### sastracker code ``` if (window.cpexPackage && cpexPackage.adserver.render(divId, creative, width, height)) { continue } ``` ### HB service creative code ``` ``` ## ECO ### HB service creative code ``` ``` ## IINFO ### HB service creative code ``` ``` ## CNC ### HB service creative code ``` ``` ## iPrima Echo24 manages the code execution, integrating cpexPackage like a regular library. - S2S: Prima calls adserver and `cpexPackage.render` from a "config" script, based on SAS response - HB: Prima calls `cpexPackage.headerbidding.refresh` They also use `cpexPackage.clearAds` and access bids from `pbjs` directly. ### HB service creative code ``` ```