# SSP

# SSP Campaign Workflow and Campaign Setup

### **SSP Campaign Workflow**

<table border="1" id="bkmrk-steps-clarification-" style="border-collapse: collapse; width: 100%; height: 1064px;"><tbody><tr style="height: 29px;"><td class="align-center" data-sheets-value="{"1":2,"2":"Steps"}" style="width: 26.9136%; height: 29px;">**Steps**</td><td class="align-center" style="width: 42.1606%; height: 29px;">**Clarification**</td><td class="align-center" data-sheets-value="{"1":2,"2":"Ownership"}" style="width: 30.9258%; height: 29px;">**Ownership**</td></tr><tr style="height: 29px;"><td class="align-center" data-sheets-value="{"1":2,"2":"Make a deal with client"}" style="width: 26.9136%; height: 29px;">Make a deal with the client</td><td class="align-center" style="width: 42.1606%; height: 29px;">-</td><td class="align-center" data-sheets-value="{"1":2,"2":"BDM"}" style="width: 30.9258%; height: 29px;">BDM</td></tr><tr style="height: 29px;"><td class="align-center" data-sheets-value="{"1":2,"2":"Receiving brief"}" style="width: 26.9136%; height: 29px;">Receive a brief from the client</td><td class="align-center" style="width: 42.1606%; height: 29px;">-</td><td class="align-center" data-sheets-value="{"1":2,"2":"AM"}" style="width: 30.9258%; height: 29px;">AM / BDM

(Depends on the market/client; Based on internal agreement between teams AM &amp; BDM)

</td></tr><tr style="height: 66px;"><td class="align-center" data-sheets-value="{"1":2,"2":"Campaign placement\n\n2 scenarios: \n1. If client wants placement on specific sites with whom we didn't make deal yet, inform them that this postpones start of the campaign as we need to make deals with mentioned publishers\n2. If no specific sites mentioned, check with SSP team if existing publishers can commit "}" style="width: 26.9136%; height: 66px;">Check the availability of placements in the Eskimi SSP inventory</td><td style="width: 42.1606%; height: 66px;">2 scenarios:  
  
**Scenario 1** - If client wants placement on specific sites with whom we didn't make deal yet:

1\. Inform client that this postpones start of the campaign as we need to make deals with mentioned publishers.

2\. Find publisher contacts and introduce publisher to Eskimi SSP team, along with information which type of creatives will be potentially launched

**Scenario 2** - If no specific sites mentioned or publishers are exist in our Eskimi SSP inventory:

1\. check with SSP team if existing publishers can commit

</td><td class="align-center" data-sheets-value="{"1":2,"2":"AM"}" style="width: 30.9258%; height: 66px;">AM / BDM

(Depends on the market/client; Based on internal agreement between teams AM &amp; BDM)

</td></tr><tr style="height: 46px;"><td class="align-center" data-sheets-value="{"1":2,"2":"Placement creation & tag send to the Publisher"}" style="width: 26.9136%; height: 46px;">Placement creation &amp; tag send to the Publisher</td><td style="width: 42.1606%; height: 46px;">This is a mandatory step only if the new publisher/placement need to be created. In all other cases it would be enough to confirm with SSP team if the previously shared pixels are still valid on publisher side.

</td><td class="align-center" data-sheets-value="{"1":2,"2":"SSP operations specialist"}" style="width: 30.9258%; height: 46px;">SSP team</td></tr><tr style="height: 29px;"><td class="align-center" data-sheets-value="{"1":2,"2":"Media plan"}" style="width: 26.9136%; height: 29px;">Prepare campaign Media Plan</td><td style="width: 42.1606%; height: 29px;">Once placement confirmed by SSP team, AM need to prepare mediaplan for campaign.

Where estimations can be done by using information from [SSP spreadsheet](https://docs.google.com/spreadsheets/d/1pMGPoAvQxSTBYn-M4zDM7_6kbr-_qHVNjS6Vr9LFXes/edit#gid=1071710348) and historical campaigns results.

</td><td class="align-center" data-sheets-value="{"1":2,"2":"AM"}" style="width: 30.9258%; height: 29px;">AM</td></tr><tr style="height: 29px;"><td class="align-center" data-sheets-value="{"1":2,"2":"Creative preview"}" style="width: 26.9136%; height: 29px;">Develop Creatives</td><td style="width: 42.1606%; height: 29px;">Depends on the creative this step consist different scenarios:

**Scenario 1** - Run static banner, templated RM:

1\. AdOps need to get images from client/AM/BDM and upload them in system

2\. AdOps need to share preview with client for confirmation

**Scenario 2** - Run custom RM / high impact ads:

1\. AM/BDM need to collect creative workflow expectation from the client, together with all needed materials for development

2\. Collected materials and scenario have to be sent to Creative team. AM/BDM is responsible to send these materials

3\. Creative team prepare creatives and is responsible that creatives consist all requested event measurement and works well on actual environment ([display.eskimi-creatives.com)](https://display.eskimi-creatives.com/)

4\. AM/BDM getting confirmation and preview link from creative team send the preview to the client for confirmation

</td><td class="align-center" data-sheets-value="{"1":2,"2":"Adops"}" style="width: 30.9258%; height: 29px;">Scenario 1 - AdOps

Scenario 2 - AM/Creative Team

</td></tr><tr style="height: 460px;"><td class="align-center" style="width: 26.9136%; height: 460px;">\*Confirm creatives with Publisher (optional step; depends on agreement with publisher)</td><td style="width: 42.1606%; height: 460px;">In some cases, specially with high-impact ads it is needed to share creative preview with the publisher as well. Sometimes publishers give campaign approval only when see the actual creative that will be advertised. At the same time it is possible to confirm that the banner shows without issues on the actual site where campaign will run.

Therefore, when creatives are developed:

1\. Creative team is responsible to provide the preview link to AdOps and SSP team.

2\. AdOps is responsible to set up test campaign for actual publisher

3\. SSP team is responsible to request test traffic from publisher and get confirmation to run particular creative

4\. When test campaign is live, creative team responsible to make sure that banners looks/works as expected on live environment.

</td><td style="width: 30.9258%; height: 460px;">AdOps / SSP team / Creative team

(described responsibilities in middle column)

</td></tr><tr><td class="align-center" style="width: 26.9136%;">Campaign setup</td><td style="width: 42.1606%;">When we have final media plan approval, creative preview approval, campaign is ready for set up

</td><td style="width: 30.9258%;">AdOps

</td></tr><tr style="height: 113px;"><td class="align-center" data-sheets-value="{"1":2,"2":"Adops informs SSP operations specialist about campaign:\n1. Campaign name, duration, period\n2. Total impressions\n3. Country\n4. Any other specific information\n5. Campaign setup in DSP"}" style="width: 26.9136%; height: 113px;">Adops informs SSP operations specialist about campaign:</td><td style="width: 42.1606%; height: 113px;">To request traffic write in the slack channel **#ssp\_adops** following details (or the channel belongs to specific market, example #ssp\_croatia, #ssp\_greece etc)

1. Campaign name
2. Country
3. Creative type (standard sizes, floating, takeover)
4. Campaign duration
5. Publishers you need (if you have a list from the client or would like to target by yourself).
6. Number of the daily impressions you’ll need.

\*Take into account that publishers availability should be checked and confirmed with SSP team before this step (check step 3 above).

</td><td class="align-center" data-sheets-value="{"1":2,"2":"Ad Ops"}" style="width: 30.9258%; height: 113px;">AdOps</td></tr><tr style="height: 79px;"><td class="align-center" data-sheets-value="{"1":2,"2":"\nTraffic & Delivery check\n\n\n"}" style="width: 26.9136%; height: 79px;">Traffic &amp; Delivery check  
  
  
</td><td style="width: 42.1606%; height: 79px;">This is the stage of live campaign, where AdOps is responsible to control delivery in DSP report and make sure that campaign is getting enough traffic to satisfy client needs.

While SSP team is responsible to control supply, and make sure that campaign fill rate satisfy publisher needs and agreement.

</td><td class="align-center" data-sheets-value="{"1":2,"2":"SSP operations specialist"}" style="width: 30.9258%; height: 79px;">AdOps / SSP team</td></tr><tr style="height: 46px;"><td class="align-center" data-sheets-value="{"1":2,"2":"Screenshots from all publishers"}" style="width: 26.9136%; height: 46px;">Screenshots from all publishers</td><td style="width: 42.1606%; height: 46px;">It is usually possible to request screenshot from campaign directly from publisher. So screenshots might be requested based on client request and depends on who is handling communication with the publisher.

Usually it is AdOps who communicate with client and pass information to SSP team who managing communication with publisher.

</td><td class="align-center" data-sheets-value="{"1":2,"2":"Ad Ops / SSP operations specialist"}" style="width: 30.9258%; height: 46px;">AdOps / SSP team</td></tr><tr style="height: 63px;"><td class="align-center" data-sheets-value="{"1":2,"2":"After campaign ends:\n1. Reporting\n2. Invoicing\n"}" style="width: 26.9136%; height: 63px;">After campaign ends:  
1. Reporting  
2. Invoicing</td><td style="width: 42.1606%; height: 63px;">This is the usual process as for any other Eskimi DSP campaign</td><td class="align-center" data-sheets-value="{"1":2,"2":"Ad Ops"}" style="width: 30.9258%; height: 63px;">AdOps</td></tr></tbody></table>

<p class="callout info">Note: Inform SSP Team about the traffic you’ll need as much in advance as you can – to have time for the traffic ordering, implementation and optimization if these actions are needed. Weekends and national holidays will be the challenge for the traffic opening from the SSP partners.</p>

<p class="callout info">Note: Please allow up to 24 hours for creative testing after the creative has been approved. This 24-hour timeframe is essential to ensure that the creatives perform optimally and that all necessary metrics are accurately measured.</p>

---

### <span style="background-color: rgb(236, 202, 250);">**SSP Campaign Setup (for AdOps)**</span>

Eskimi SSP campaign setup is done in a bit different way comparing with the standard Eskimi DSP campaign setup. These are steps you need to follow when setuping it:

<div id="bkmrk-start-with-usual-cam"><div><div>1. Start with usual campaign setup and creatives upload.
2. Check SSP Publishers’ prices in online doc [https://bit.ly/384waVQ](https://bit.ly/384waVQ) (you should be given access
    
    by SSP Team to access this file). **ATT:** your bid in campaign after margin cannot be smaller than it is mentioned in the document.
3. SSP campaigns has no targeting – please do not select any targeting options except your campaign is running too quickly or client do not let us remove targetings. Also, there shouldn't be impression capping or auto-optimization added to campaign.
4. Find the site IDs in the [https://stats.eskimi.com/admin/adops/AppsSitesLookup/](https://stats.eskimi.com/admin/adops/AppsSitesLookup/). Pick IDs accordingly to the exchange you need and add to the package.  
    \***There are cases when you need to add placement\_id to the package instead of site\_id.** It happens when we run several campaigns with one publisher at the same time. In case to keep trackers in order and control delivery per each campaign/placement. SSP team can clarify to you if the site\_id or placement\_id need to be added in particular case.
5. Mark “allow multiple bids” – this parameter is a must for all SSP campaigns. Except the cases when it is specifically asked from the client not to show ads in this way.
6. Pick one of exchanges:
    
    
    - **Eskimi standard** – for the standard banners.
    - **Eskimi floating** - for the floating banners.
    - **Eskimi takeover** - for the takeover banners.
    - **GroupM or GroupM floating** for the campaigns running for WPP Kenya.

</div></div></div><div id="bkmrk-check-the-cpm-for-al"><div><div><div>7. Check the CPM for all Publishers you added for this campaign.
8. Add and check the margin to have the buying CPM not lower than Publisher’s CPM.
9. Once all set up done, you can check if there is something that might be missed using the [following form ](https://docs.google.com/forms/d/e/1FAIpQLSdLlGb3tF5jLTjI4JuSuw9zC_JLXGUOtr8SiAAYHnel0drFvg/viewform)

</div></div></div></div>### <span style="background-color: rgb(236, 202, 250);">**SSP Test Campaign Setup (for Creative team)**</span>

Eskimi SSP test setup is very similarly to the set up of the SSP campaign.  
1\. Start with uploading the creatives.  
2\. Create the package where you want to test (site or placement id). Go to **Tools →** **Packages** **→** **New package →** Write package name **→ Select package type** **→ Select country → Upload CSV file** (comma separated values). **<span style="background-color: rgb(248, 202, 198);">Note:</span>** before uploading make sure you copied the right id of the publisher/placement based on the creative type (takeover or floating ad). E.g. Need to test Floating ad in LT market. Copy the floating ad placement\\publisher id, put it in excel, save it as CSV file and upload it to the system.   
3\. In the <span style="text-decoration: underline;">campaign set up page</span>:

• Select **Creative type →** Banner  
• Select **Campaign type** **→** Display Ads  
• Write the name of the test  
• Select **Campaign goal →** Awareness  
• Select **Primary campaign objective →** CPM and write the bid value  
• Unselect <span style="text-decoration: underline;">Pre-optimisation based on historical placement stats</span> button  
• Remove Impression capping  
• Select the date  
• Write Total budget (let’s say 10$)  
• Select **Daily Budget Pacing →** Spread daily budget ASAP  
• Write Bid (CPM) - the same number as in primary campaign objective  
• Select the Country  
• In **Deals &amp; packages section:** check if *Eskimi floating* or *Eskimi takeover* exchanges are selected (depending on the test)  
• Select the package (test sites and placements of LT &amp; LV could be found pinned in Slack channels **\#ssp\_lt &amp; ssp\_lv**)  
 **\*If site package**, select these: Include Only, Disable impression capping, Disable auto optimisation, Disable budget pacing for this package, Disable App/site category exclusion  
 **\*If placement id package**, select: Include only  
• Write Click URL - [https://www.eskimi.com/campaigns](https://www.eskimi.com/campaigns)  
• Select Ad domain **→** eskimi.com  
• Select the creatives in **Selected creative sets**  
• Press **→** Publish

Now the campaign is in <span style="text-decoration: underline;">pending status</span>. The last step is to approve the campaign.  
4\. Go to **Approve** page **→ Ad Exchanges** (scroll to the end) **→ E-SSP Partners** **→** Select the exchange depending on the banner (Floating or Takeover).

<div id="bkmrk--1"></div><div id="bkmrk--2"></div>

# Introduction to SSP

### **What is SSP?**

A supply-side platform (SSP) is an advertising technology platform used to coordinate and manage the supply and distribution of ad inventories. SSPs help digital media owners and publishers sell digital ads in automated auctions.

The purpose of SSPs is to efficiently improve the yield optimization of advertising space inventory on websites and mobile apps to minimize wasted space and maximize views. In short, SSPs allow publishers to sell their inventory to the best ad network.

---

### **What advantages do SSPs provide publishers?**

- Higher growth. Chance to reach as many advertisers as possible across the programmatic ecosystem - DSPs, exchanges, networks.
- Automation. As soon as publishers configure in the dashboard how they want their ad campaign to run, the system automates the ad serving. This means that placements are filled in real-time automatically, without manual actions.
- Control over inventory. Publisher controls enable to set up how you want the ads to be displayed on the website/in the app.
- Reporting. Statistics that SSPs generate for publishers can be eye-opening: who bids on inventory, what is a median bid and how each piece of inventory performs. The right metric can give publishers a real understanding of their inventory value.

---

### **How do SSPs use data?**

In addition to helping publishers reach a wider net of potential buyers, SSPs enable publishers to share the valuable data they have about their users at the ad impression level. When publishers make unsold ad impressions available through an SSP, the buyers — DSPs, ad exchanges and ad networks — will take into account the content of the page where the available ad impression appears, as well as the user data the publisher has for that impression (data might include demographics, location, browsing and purchase history) and match it against the audience targeting criteria set by the buyers. If the publisher data and advertiser targets overlap, the buying platforms will bid on the ad impression in an auction on behalf of the advertiser.

# SSP Video

#### **What is Eskimi SSP video?**

<span style="font-weight: 300;">Eskimi SSP is a video advertising and monetization solution that bridges the gap between video supply and demand. </span>

<span style="font-weight: 300;">The video players allow publishers to monetize their supply through different video placements - in-read, floating, and sticky. The players support in-stream and out-stream ads, so even CTV publishers can be onboarded. </span>

---

#### **What are the Eskimi video capabilities?** 

##### **Outstream player**

<span style="font-weight: 300;">Outstream - video ads (</span>**VAST**<span style="font-weight: 300;"> &amp; </span>**VPAID**<span style="font-weight: 300;">) are served between the website’s content (ex.: in-article). The out-stream video player is compatible with </span>**desktop**<span style="font-weight: 300;"> and </span>**mobile**<span style="font-weight: 300;"> devices. The video tag is responsive so the publisher is required to integrate only 1 code. Outstream code can be implemented </span>**directly** **on the page** <span style="font-weight: 300;">or through a third party like - </span>**Google Ad Manager**<span style="font-weight: 300;">. </span>

##### **Instream player**

<span style="font-weight: 300;">Instream - video ads (</span>**VAST** <span style="font-weight: 300;">&amp; </span>**VPAID**<span style="font-weight: 300;">) interrupt another video on the website (ex.: pre-roll). The Instream video player is compatible with </span>**desktop**<span style="font-weight: 300;">, </span>**mobile**<span style="font-weight: 300;"> &amp; </span>**CTV**<span style="font-weight: 300;"> devices. The video tag is responsive so the publisher is required to integrate only 1 code. Instream code can be implemented </span>**directly** **on the page** <span style="font-weight: 300;">or through a third party like - </span>**Google Ad Manager**<span style="font-weight: 300;">. </span>

<span style="font-weight: 300;">Instream player allows controlling:</span>

- <span style="font-weight: 300;"> How many ads will be shown in the content;</span>
- <span style="font-weight: 300;">What will be the time between ads;</span>
- <span style="font-weight: 300;">Randomize or sequence the content where the video ads will be shown;</span>

<span style="font-weight: 300;">For instream ad monetization video content is required. The video content has to be on the website. However, if the publisher doesn’t have any content on the website, it is possible to offer a </span>**3rd party content**<span style="font-weight: 300;">. Keep in mind that the content will be only in </span>**English**<span style="font-weight: 300;"> and will have</span> **additional pricing**<span style="font-weight: 300;">. </span>

---

#### **Video placement templates**

<span style="font-weight: 300;">Both instream and outstream video players have a rich variety of positions on the website. Let’s go through them:</span>

##### **Floating**

**Top left:** [<span style="font-weight: 300;">https://manage.aniview.com/player/preview.html?type=tp&amp;AV\_TEMPID=63eca44719247c3265075204&amp;AV\_PUBLISHERID=63e22d57f3cd17944e0a6665</span>  
  ](https://manage.aniview.com/player/preview.html?type=tp&AV_TEMPID=63eca44719247c3265075204&AV_PUBLISHERID=63e22d57f3cd17944e0a6665)**Top right:** [<span style="font-weight: 300;">https://manage.aniview.com/player/preview.html?type=tp&amp;AV\_TEMPID=63eca47a27e2d783e10ebb76&amp;AV\_PUBLISHERID=63e22d57f3cd17944e0a6665</span>  
  ](https://manage.aniview.com/player/preview.html?type=tp&AV_TEMPID=63eca47a27e2d783e10ebb76&AV_PUBLISHERID=63e22d57f3cd17944e0a6665)**Top middle:** [<span style="font-weight: 300;">https://manage.aniview.com/player/preview.html?type=tp&amp;AV\_TEMPID=63eca340e1532919970d0fb5&amp;AV\_PUBLISHERID=63e22d57f3cd17944e0a6665</span>](https://manage.aniview.com/player/preview.html?type=tp&AV_TEMPID=63eca340e1532919970d0fb5&AV_PUBLISHERID=63e22d57f3cd17944e0a6665)

**Bottom left:** <span style="font-weight: 300;">[https://manage.aniview.com/player/preview.html?type=tp&amp;AV\_TEMPID=63eca545bcc1b9b90107f344&amp;AV\_PUBLISHERID=63e22d57f3cd17944e0a6665](https://manage.aniview.com/player/preview.html?type=tp&AV_TEMPID=63eca545bcc1b9b90107f344&AV_PUBLISHERID=63e22d57f3cd17944e0a6665)</span>

**Bottom right:** [<span style="font-weight: 300;">https://manage.aniview.com/player/preview.html?type=tp&amp;AV\_TEMPID=63eca50e6116b913ef09b1d6&amp;AV\_PUBLISHERID=63e22d57f3cd17944e0a6665</span>  
  ](https://manage.aniview.com/player/preview.html?type=tp&AV_TEMPID=63eca50e6116b913ef09b1d6&AV_PUBLISHERID=63e22d57f3cd17944e0a6665)**Bottom middle:** [<span style="font-weight: 300;">https://manage.aniview.com/player/preview.html?type=tp&amp;AV\_TEMPID=63eca568881a486f580eaf2e&amp;AV\_PUBLISHERID=63e22d57f3cd17944e0a6665</span>](https://manage.aniview.com/player/preview.html?type=tp&AV_TEMPID=63eca568881a486f580eaf2e&AV_PUBLISHERID=63e22d57f3cd17944e0a6665)

<span style="font-weight: 300;">Floating video position is highly customizable. It is possible to:</span>

- <span style="font-weight: 300;">Define a video player size when it is floating. </span>
- <span style="font-weight: 300;">Different pause options. </span>
- <span style="font-weight: 300;">Floating on button or impression. </span>
- <span style="font-weight: 300;">Etc.</span>

##### **In-read**

[<span style="font-weight: 400;">https://manage.aniview.com/player/preview.html?type=tp&amp;AV\_TEMPID=63ecaaecdccdb0653803f534&amp;AV\_PUBLISHERID=63e22d57f3cd17944e0a6665</span>](https://manage.aniview.com/player/preview.html?type=tp&AV_TEMPID=63ecaaecdccdb0653803f534&AV_PUBLISHERID=63e22d57f3cd17944e0a6665)

##### **Sticky**

**Top right:** [<span style="font-weight: 400;">https://manage.aniview.com/player/preview.html?type=tp&amp;AV\_TEMPID=63ecac7fb9a16891e800b835&amp;AV\_PUBLISHERID=63e22d57f3cd17944e0a6665</span>](https://manage.aniview.com/player/preview.html?type=tp&AV_TEMPID=63ecac7fb9a16891e800b835&AV_PUBLISHERID=63e22d57f3cd17944e0a6665)

**Top left:** <span style="font-weight: 400;">[https://manage.aniview.com/player/preview.html?type=tp&amp;AV\_TEMPID=63ecaca0b9a945a8e9043e04&amp;AV\_PUBLISHERID=63e22d57f3cd17944e0a6665](https://manage.aniview.com/player/preview.html?type=tp&AV_TEMPID=63ecaca0b9a945a8e9043e04&AV_PUBLISHERID=63e22d57f3cd17944e0a6665)</span>

**Top middle:** [<span style="font-weight: 400;">https://manage.aniview.com/player/preview.html?type=tp&amp;AV\_TEMPID=63ecac4744aa2d4581010586&amp;AV\_PUBLISHERID=63e22d57f3cd17944e0a6665</span>](https://manage.aniview.com/player/preview.html?type=tp&AV_TEMPID=63ecac4744aa2d4581010586&AV_PUBLISHERID=63e22d57f3cd17944e0a6665)

**Bottom left:** [<span style="font-weight: 400;">https://manage.aniview.com/player/preview.html?type=tp&amp;AV\_TEMPID=63ecabe8d6faf99ce10ffd76&amp;AV\_PUBLISHERID=63e22d57f3cd17944e0a6665</span>](https://manage.aniview.com/player/preview.html?type=tp&AV_TEMPID=63ecabe8d6faf99ce10ffd76&AV_PUBLISHERID=63e22d57f3cd17944e0a6665)

**Bottom right:** <span style="font-weight: 400;">[https://manage.aniview.com/player/preview.html?type=tp&amp;AV\_TEMPID=63ecab24bf55da62030a22a7&amp;AV\_PUBLISHERID=63e22d57f3cd17944e0a6665](https://manage.aniview.com/player/preview.html?type=tp&AV_TEMPID=63ecab24bf55da62030a22a7&AV_PUBLISHERID=63e22d57f3cd17944e0a6665)</span>

**Bottom middle:** <span style="font-weight: 400;">[https://manage.aniview.com/player/preview.html?type=tp&amp;AV\_TEMPID=63ecac282f8f04654701df9d&amp;AV\_PUBLISHERID=63e22d57f3cd17944e0a6665](https://manage.aniview.com/player/preview.html?type=tp&AV_TEMPID=63ecac282f8f04654701df9d&AV_PUBLISHERID=63e22d57f3cd17944e0a6665)</span>

---

#### **Integration process - local demand**

<span style="font-weight: 300;">The technical integration process for any video placement (</span>**outstream, instream, CTV**<span style="font-weight: 300;">) is handled by the SSP team. Reach out to </span><span style="font-weight: 300;">[kannan@eskimi.com ](mailto:kannan@eskimi.com)</span><span style="font-weight: 300;">and </span><span style="font-weight: 300;"><prajay@eskimi.com> </span><span style="font-weight: 300;">for further information. They will provide video tags, guide the publisher how to implement the tags and troubleshoot any discrepancies. </span>

<span style="font-weight: 300;">After the integration is finished the publisher traffic will be bought through </span>**Eskimi DSP**<span style="font-weight: 300;"> by using </span>**Aniview exchange**<span style="font-weight: 300;">. Publishers will be visible the same way as on any other exchange. No additional process is needed for campaign execution. </span>

<span style="font-weight: 300;">For any product related questions reach out to </span><span style="font-weight: 300;"><gabriele@eskimi.com></span><span style="font-weight: 300;">. </span>

---

#### **Integration process - global demand**

<span style="font-weight: 300;">If the publisher needs to be onboarded for the global demand parallel to local demand then:</span>

1. <span style="font-weight: 300;">Domains and geographies need to be provided by the sales team with the SSP team.</span>
2. <span style="font-weight: 300;">The domains will go through the approval process which will take up to 2 weeks.</span>
3. <span style="font-weight: 300;">After the approval process is finished Eskimi will provide ads.txt lines which need to be implemented by the publisher. </span>

<span style="font-weight: 300;">The global demand consists, but not limited to, global SSPs such as </span>**Google, Yahoo, Appnexus, Pubmatic, Magnite, Unruly, Index Exchange, SmartAdServer** <span style="font-weight: 300;">and others. </span>

# SSP Publisher Onboarding Guide

##### **Introduction**

Welcome to the SSP Publisher Onboarding Guide. This guide will provide you with comprehensive information and instructions to successfully onboard publishers onto the SSP platform. By following this guide, you can ensure a smoother onboarding process and be better equipped to troubleshoot any issues that may arise.

---

##### **Information Needed for Onboarding**

<div id="bkmrk-domain%3A-obtain-the-p"><div>1. **Domain:**
    
    
    - Obtain the publisher's domain name, which will be used to identify their website or application.
2. **Existing Player:**
    
    
    - Determine whether the publisher already has a video player integrated into their platform.
    - If they do, identify the specific player they are using.
3. **Tag Implementation:**
    
    
    - Determine where the SSP tag will be implemented on the publisher's website or application.
    - This information is crucial for proper ad delivery and integration.
4. **Specific Requirements:**
    
    
    - Identify any specific requirements or preferences the publisher may have.
    - This could include custom ad formats, ad placements, or any other unique specifications.

</div></div>This information has to be collected by the person who is responsible for the publisher management.

---

##### **Onboarding for Global Demand**

For publishers targeting global demand, gather the following information:

<div id="bkmrk-domain%3A-provide-the-"><div>1. **Domain:**
    
    
    - Provide the domain name associated with the publisher's website or application.
2. **Country:**
    
    
    - Identify the specific country or countries the publisher is targeting.
3. **Direct or Reseller:**
    
    
    - Determine whether the publisher is directly working with advertisers or through a reseller.
4. **Instream or Outstream:**
    
    
    - Clarify whether the publisher intends to display video ads within their content (in-stream) or as standalone units (out-stream).
5. **Floor Price:**
    
    
    - Determine the desired floor price for the publisher's ad inventory.
    - The floor price is the minimum price at which an ad impression is sold.
6. **MCM (Managed Channel Mapping):**
    
    
    - Specify whether the publisher requires Managed Channel Mapping for enhanced control over ad placements.

</div></div>It is essential to start the onboarding process for global demand as soon as possible. As the publisher review and approval process may take up to **1 to 2 weeks**.

---

##### **Troubleshooting**

For troubleshooting purposes, follow these guidelines:

<div id="bkmrk-open-a-support-ticke"><div>1. **Open a Support Ticket:**
    
    
    - Open a support ticket by sending an email to the SSP team.
    - The ticket has to include the following information:

</div></div>\- In each support ticket, include a clear description of the issue or question.

\- Provide details such as the player/template/channel/source ID (depending on the issue).

\- Share a test page where the issue can be reproduced.

\- Specify GEO and OS targeting settings for accurate troubleshooting.

- Attach relevant screenshots or screen recordings of the issue for better understanding.

---

##### **Conclusion:**

Congratulations! You now have a comprehensive SSP Publisher Onboarding Guide. By following these instructions and providing the necessary information, you can streamline the onboarding process and troubleshoot any issues that may arise effectively. Remember to maintain clear communication with the SSP support team throughout the onboarding journey.