Bring programmatic demand to your screens
Six ways to connect your inventory to Eskimi, from a full OpenRTB endpoint down to a shared folder. Pick what fits your CMS today — nothing here requires exclusivity with your existing SSPs or exchanges.
Six ways to integrate
Every path below reaches the same demand. The right one for you depends on what your CMS or player can already do — not on how much engineering time you have to spend.
| Method | Best for | Effort | Real-time | Reporting |
|---|---|---|---|---|
|
A
OpenRTB (Real-Time Bidding)
Your system acts as a supply-side platform, sending real-time bid requests to Eskimi for every ad slot and receiving a winning creative in the response. |
SSP-ready networks | High | Yes | Automatic |
|
B
API Integration
Eskimi talks directly to your CMS over its REST API for server-to-server campaign, creative, and reporting calls. |
CMS with REST APIs | Medium | Near | Automatic |
|
C
VAST Tag
Your player requests an ad from a VAST tag URL for each slot, the same way a standard video ad server is called. |
VAST-capable players | Low | Yes | Automatic |
|
D
Content Feed / Playlist URL
Your player periodically fetches the current creative from a hosted content feed URL that Eskimi keeps up to date. |
URL-capable players | Very Low | Near | Semi-auto |
|
E
UI Automation
Eskimi operates your web-based CMS on your behalf to schedule and swap campaigns, with no integration work on your side. |
Web CMS with no API | Low (partner side) | No | Semi-auto |
|
F
File Transfer (SFTP / Shared Folder)
Creatives are pushed to an SFTP server or shared folder on a schedule, and proof-of-play reports come back as CSV files. |
Minimal infrastructure | Very Low | No | Manual |
Not sure which fits? The online application walks through a few technical questions and mirrors this same table back as a recommendation.
How impressions are estimated
A "play" on a screen is not the same as an impression — a screen typically has more than one viewer per play. We apply an impression multiplier (average viewers per play) to turn logged plays into estimated audience impressions, the same way outdoor audience measurement has always worked. If you already have footfall or dwell-time data for your locations, we use it; otherwise a conservative default applies until real measurement is available. This keeps reporting honest: plays are a fact, impressions are always a transparent estimate built on top of them.
Creative formats we deliver
Campaigns are booked as image, video, HTML5, or animated creative. Your screens only need to accept the formats they can actually play — tell us what's supported and we serve within those limits.
| Format | File types | Specs |
|---|---|---|
| Static image | JPEG, PNG | Native resolution, max 10MB |
| Video | MP4 (H.264), MOV | Native resolution, 10-15s, max 50MB, 25-30fps |
| HTML5 | HTML + ZIP | Responsive, max 5MB |
| Animated | GIF | Native resolution, max 10MB |
Reporting fields
Whichever method you integrate through, this is the shape of proof-of-play data we need back. Required fields are the minimum to reconcile delivery; recommended fields make reporting and audience estimates richer.
| Field | Description | Priority |
|---|---|---|
date |
Calendar date the plays occurred (YYYY-MM-DD). | Required |
time_hour |
Hour of day the plays occurred, for daypart analysis. | Recommended |
campaign_id |
Identifier of the campaign the plays belong to. | Required |
creative_id |
Identifier of the creative that played. | Required |
screen_id |
Identifier of the screen the plays occurred on. | Required |
screen_name |
Human-readable name of the screen or site. | Recommended |
location |
City, venue, or address of the screen. | Recommended |
plays |
Number of times the creative played in the period. | Required |
duration_sec |
Total seconds the creative played in the period. | Required |
impressions |
Estimated audience impressions delivered. | Recommended |
impression_multiplier |
Average viewers per play used to derive impressions. | Recommended |
reach |
Estimated unique audience reached. | Recommended |
cost |
Media cost for the period, in the agreed currency. | Required |
Already have a CSV or API export with different column names? Send a sample — we map fields on our side rather than asking you to rebuild your export.
Frequently asked questions
Do I need real-time bidding to work with Eskimi?
No. OpenRTB is the deepest integration, but it's one of six. VAST, a content feed URL, UI automation, and even a plain SFTP drop are all supported paths — pick whichever matches what your CMS or player already does.
Can I keep working with my existing SSPs and exchanges?
Yes. Integrating with Eskimi is not exclusive — your inventory can be connected here alongside any other demand source you already run.
What if my screens don't have audience measurement?
That's fine to start. We apply a standard impression multiplier until real footfall or dwell-time data is available, and switch to your measurement the moment you can provide it.
How long does onboarding take?
It depends on the method: a content-feed URL or file-transfer setup can be live in days; an API or OpenRTB integration takes longer because it involves two engineering teams. Submit the application below and your technical contact will confirm a timeline.
Ready to connect your screens?
Tell us about your inventory and technical setup — it takes a few minutes, and lands directly with our partnerships team.
Apply to integrate →