Overview

This section focuses on how to integrate Advisible services into a website. It covers the basics of ad integration, including how to set up and configure the Advisible Development Kit (ADK), as well as best practices for optimizing ad performance and user experience. Whether you are new to ad integration or looking to enhance your existing setup, this guide provides the essential information you need to get started with Advisible. Let's start with an overview of how the platform works.

What are Advisible Native Ads?

Advisible Native Ads mimic the appearance of other content on a website. The platform offers two main types of native ads:

• Content Display — links to external content
• True Native — the user stays on the publisher's site

True Native ads can be further divided into two formats:

• teasers, which open the article on a separate page; and
• scroll articles, which display the native article inline within an editorial article feed.

Platform architecture

Advisible's ad serving architecture consists of the ADK frontend library that makes ad requests to the Placement Service. The Placement Service is a real-time bidding server that queries ads from multiple Ad Servers. Each ad server is specialized in a certain kind of advertisement (True Native and Content Display mentioned above) and integrates with the platform using an adapter, which consists of a frontend and a backend. The ad server returns eligible ad items (and bids if applicable) when queried by the Placement Service through its adapter backend. The final ad response is then returned to ADK which uses the Client Adapter to render and track the ad leveraging the frontend part of the adapter.

The diagram below illustrates the flow of an ad request through the components described above, from the time a user visits a page to when the ad is served and rendered and tracked.

Now that you are familiar with the overall architecture and flow of ad requests, the next step is to learn about the components of ADK.