Publisher integration

Landing page

True Native teasers bring the visitor to a landing page on the website. The landing page loads and renders the native article for the clicked teaser by including an ADK container using the adk.native.article provider in the markup.

General guidelines

Choosing a URL structure

Every publisher account has an origin and a landing page base path. These are configured in the account settings in Advisible Console. If the origin is https://www.example.com and the base path is sponsored/, then the landing page URL is https://www.example.com/sponsored/articleId, where articleId is the unique ID of the article.

The above example uses a dynamic route, meaning that the website's server must respond to everything under https://www.example.com/sponsored/. This is the recommended approach whenever possible, but a fixed path can be used instead if dynamic routing is not available.

When the landing page is loaded, the article ID must be extracted from the URL and passed to Advisible using the itemId provider parameter. The table below shows three different schemas and how to extract the ID.

RoutingBase pathExtraction command
Dynamic pathsponsored/window.location.pathname.split('/')[2]
Fixed path using searchsponsored?id=new URLSearchParams(window.location.search).get('id')
Fixed path using hashsponsored#window.location.hash.slice(1)

Tracking

The landing page URL for an article can be visited at any time when the campaign is published. This allows the advertiser to leave the article available even after the campaign has ended. However, the article will only be tracked if the entry point is a valid teaser click. If the user visits the landing page directly, it will not be tracked.

Read time is measured when 50% of the article is visible or the article covers 50% of the screen, vertically.