Breakout Ads
*Preview here.
BREAK THE FRAME: BANNERS THAT BLEND SEAMLESSLY INTO YOUR SITE
WHAT ARE BREAKOUT ADS?
This new format uses dynamic animations to pull attention out into the page and guide it back to the banner as you scroll down the page.
BENEFITS OF BREAK OUT ADS
👁️ Disrupts the Scroll
- Gets users to pause by breaking passive browsing
📐 Expands in Page
- 3D assets dynamically grow and change within a publishers website
⭐️ Heightened Immersion
- Attention verification paired with 3D assets pulls users deeper into the brand story
Add it to your presentation using our Pitch-ready slides here.
See Creative Requirements here.
*Preview here.
SET UP REQUIREMENTS
This table outlines the end-to-end SSP campaign workflow, the standard campaign setup process for AdOps, and the test campaign setup process for the Creative Studio team.
Requirement: SSP availability is strictly mandatory for this implementation. Creative planning and discussions will remain on hold until SSP is supported in the market.
SSP CAMPAIGN WORKFLOW
| STEPS | CLARIFICATION | OWNERSHIP |
|
1. Make a deal with the client |
- |
BDM
|
|
2. Receive a brief from the client |
- |
AM / BDM
(Depends on the market and client, based on the internal agreement between the AM and BDM teams)
|
|
3. Check the availability of placements in the Eskimi SSP inventory |
Scenario 1: If client wants
Scenario 2: If no specific sites mentioned or publishers are exist in our Eskimi SSP inventory:
|
AM / BDM
(Depends on the market and client, based on the internal agreement between the AM and BDM teams) |
|
4. Create the placement and send the tag to the publisher |
|
SSP team |
|
5. Prepare the campaign media plan |
|
AM |
|
6. Develop creatives |
The process depends on the creative type:
Scenario 1: static banners or templated Rich Media:
Scenario 2: Custom Rich Media or high-impact ads:
|
Scenario 1: AdOps Scenario 2: AM / Creative team
|
|
7. Confirm creatives with the publisher (optional; depends on the agreement with the publisher) |
For some high-impact campaigns:
When the creative is ready:
|
AdOps / SSP team / Creative team
(Responsibilities are described in the clarification column) |
|
8. Set up the campaign |
Once the media plan and creative preview have final approval, the campaign is ready for setup
|
AdOps |
|
9. AdOps informs the SSP Operations Specialist about the campaign |
Request traffic in the Slack channel #ssp_adops, or in the channel for the specific market, EG: #ssp_croatia or #ssp_greece - include:
Publisher availability must be checked and confirmed with the SSP team before this step (See Step 3) |
AdOps |
|
10. Check traffic and delivery |
|
AdOps / SSP team |
|
11. Request screenshots from all publishers |
|
AdOps / SSP team |
|
12. Campaign ends |
This follows the usual process for any other Eskimi DSP campaign
|
AdOps |
NOTE: Inform the SSP team about the traffic you will need as far in advance as possible. This allows time for traffic ordering, implementation and optimisation where required. Weekends and national holidays may delay traffic opening by SSP partners.
NOTE: Allow up to 24 hours for creative testing after the creative has been approved. This time is needed to confirm that the creative performs correctly and that all required metrics are measured accurately.
SSP CAMPAIGN SETUP FOR ADOPS
Eskimi SSP campaigns are set up differently from standard Eskimi DSP campaigns. Follow these steps:
- Start with the usual campaign setup and creative upload
- Check SSP publisher prices in the online document: https://bit.ly/384waVQ
- You must have access from the SSP team to open this file
- The campaign bid after margin must not be lower than the amount listed in the document
- Do not select targeting options for SSP campaigns unless the campaign is running too quickly or the client does not allow targeting to be removed; do not add impression capping or auto-optimisation
-
Create a package containing the required domains
-
If the site list is large, one common package may be used
-
If you need to control delivery separately for each publisher, create a separate package for each publisher
-
Find site IDs here: https://stats.eskimi.com/admin/adops/AppsSitesLookup/
-
Select IDs for the required exchange and add them to the package
-
In some cases, placement_id must be added instead of site_id
-
This is used when several campaigns run with one publisher at the same time, helping to keep trackers organised and control delivery by campaign or placement
-
The SSP team will confirm which ID is required
-
-
- If delivery is required on specific subdomains or site sections:
- Prepare a keyword list containing the section names used by the subdomain, such as lifestyle or sports
- In targeting settings, select Context options, then Find in URL
- Under Match options, choose Exact word type match
- Upload the keyword list in CSV format
- Set Default to No and Status to Enabled
- Assign the targeting to the relevant account user
- If the publisher provides traffic through a PMP Private Marketplace deal, AdOps must contact the publisher and request:
- Buyer ID
- Brand
- Country
- Creative type and sizes
- Campaign duration
- Position and targeting, if required
- After the publisher confirms the setup and provides the Deal ID, complete the deal setup in the DSP
- Select the exchange where the deal was created instead of the default Eskimi exchanges
- Use deal targeting in a separate campaign split where possible to improve performance control
- Select Allow multiple bids for all SSP campaigns, unless the client specifically requests that ads are not shown this way
- Select the correct exchange:
- Eskimi standard for standard banners
- Eskimi floating for floating banners
- Eskimi takeover for takeover banners
- GroupM or GroupM floating for campaigns running for WPP Kenya
- Check the CPM for every publisher added to the campaign
- Add and check the margin. The buying CPM must not be lower than the publisher CPM
- When setup is complete, use the following form to check whether anything has been missed
SSP TEST CAMPAIGN SETUP FOR CREATIVE TEAM
An Eskimi SSP test campaign is set up in a similar way to a standard SSP campaign:
- Upload the creatives
- Create the package for the site or placement where the creative will be tested
- Go to Tools > Packages > New package
- Enter the package name
- Select the package type and country
- Upload a CSV file containing comma-separated values
- Before uploading, confirm that you copied the correct publisher or placement ID for the creative type, such as takeover or floating
- EG: To test a floating ad in Lithuania, copy the floating-ad publisher or placement ID, place it in Excel, save it as a CSV file, and upload it
- Complete the campaign setup page as follows:
- Creative type: Banner
- Campaign type: Display Ads
- Name: Enter the name of the test
- Campaign goal: Awareness
- Primary campaign objective: CPM, then enter the bid value
- Pre-optimisation based on historical placement stats: Unselected
- Impression capping: Removed
- Date: Select the test date
- Total budget: Enter a small test budget, for example USD 10
- Daily Budget Pacing: Spread daily budget ASAP
- Bid (CPM): Enter the same value used for the primary campaign objective
- Country: Select the relevant country
- Deals and packages: Confirm that Eskimi floating or Eskimi takeover is selected, depending on the test
- Package: Select the test package (test sites and placements for Lithuania and Latvia may be found in the pinned messages in #ssp_lt and #ssp_lv)
- For a site package:
- Select Include Only
- Disable impression capping
- Disable auto optimisation
- Disable budget pacing for this package
- Disable App/site category exclusion
- For a placement ID package, select Include Only
- For a site package:
- Click URL: https://www.eskimi.com/campaigns
- Ad domain: eskimi.com
- Selected creative sets: Select the creatives
- Select Publish
The campaign will now have Pending status. The final step is to approve it:
- Go to Approve page → Ad Exchanges
- Scroll to the end and select E-SSP Partners
- Select the exchange that matches the banner type: Floating or Takeover
*Download Creative Requirements as a PDF here.
*Preview here.