Skip to main content
Uplift Ads is a server-side ad server that drives ad revenue without compromising customer experience or security. Ads load rapidly and require no cookies or JavaScript tags, making the solution fully GDPR compliant out of the box. Platform 195 will work with you to determine the right ad products, placements, and sales models for your properties — whether that’s CPM, CPC, duration-based tenancy, or a combination.

Ad products

Native Ads

Responsive ads custom-designed to match the style of your web content. Typically feature on channel landing and home pages.

Display Ads

Fixed banner sizes served into containers. Ideal for search results pages with dynamic keyword targeting.

Sponsored Ads

Boost products into sponsored positions on search results pages, matched against your organic listings.

Recommender Ads

Product recommendation ads on detail pages and category pages, matched to a user’s current context.

How it works

Every ad product follows the same three-step pattern:
1

Request

Your server POSTs to the Uplift Ads API at page load, passing your zoneIds and targeting keywords. Authentication is handled via headers. See Authentication.
2

Serve

Parse the JSON response and render the returned creative components or product IDs into the correct position on the page.
3

Track

Fire the impressionUrl, clickUrl, and optionally viewableImpressionUrl and conversionUrl at the appropriate user events. See Tracking Ad Engagement.

Environments

Uplift Ads provides separate dev and production environments. Your account manager will supply your x-api-key and x-site-id for each environment. Use the dev environment for all testing; production credentials are issued once testing is complete.
EnvironmentBase URL
Devhttps://dev.api.upliftads.io/v3/
Productionhttps://api.upliftads.io/v3/
All request and response examples in this documentation use the dev environment. Swap the base URL and credentials for production once testing is complete.

Targeting with keywords

All ad products use a keywords array to pass targeting context with each request. Keywords follow a Key.Value format — for example, Dest.123-2 or Dep.LGW. Platform 195 will agree the full keyword taxonomy with you during onboarding.

Evidencing ads

To support automated screenshot evidence for advertisers, wrap every ad placement in a div with a class of FID_ followed by the flight ID returned in the response:
<div class="existing_class FID_{{flightId}}">
  <!-- ad content -->
</div>