Click to Native Browser

Introduction

Demand-side platforms running in-app-to-mobile web campaigns on the Fyber Marketplace are likely interested in tracking cookies, running cross-device matching, and measuring mobile web conversions. To track cookies upon ad click-through, Fyber must open the landing page URL in the native browser, rather than opening the landing page in our default embedded browser.

In the embedded browser, only device IDs are trackable. In the native browser, user cookies, bounce rate and web conversions are trackable.

Definitions

Title Definition
Click URL Click URL also known as 'Landing Page URL' is the website address that a user is taken to when clicking on an ad. The click URL is passed within the client's creative tag
In VAST 2.0, it is the clickthroughurl element
Native Browser Also know as the 'External Browser' - is the browser app on the device i.e., the Chrome or Safari app
 

Who Can Use this Feature?

This feature can be used by:

  • Programmatic Demand partners connected using a bidder and OpenRTB protocol
  • API demand partners, if they are able to target by SDK version OR add the new custom extension to their API specification

Implementation Steps to Open the Native Browser

Fyber supports two implementation methodologies: 

Method 1: URL Suffix

  1. When running an app to web campaigns, target Fyber Marketplace supply that supports opening the landing page in the native browser.
  2. Fyber uses a custom bid request extension to flag native browser supply:
Custom Extension
imp.ext.brsrclk:1

Where [1] = native browser is forced open upon click

  1. DSP must append a new URL suffix to their Click URL to force open the native browser.

If the URL suffix is not added, Fyber opens the landing page in the embedded browser.

URL Suffix: FYBER_OPEN_BROWSER

Native Link Browser Example
https://ads.DSP.com/delivery/r/ajs.php?did=5bf512f8cb99bd00d942ad21dc941a00&......&FYBER_OPEN_BROWSER

Method 2: URL Prefix

  1. When running an app to web campaigns, target Fyber Marketplace supply that supports opening the landing page in the native browser.
  2. Fyber uses a custom bid request extension to flag native browser supply:
Bid Request Extension
imp.ext.brsrclk:1

Where [1] = native browser is forced open upon click

  1. DSP must append a new URL prefix to their Click URL to force open the native browser.

If the URL prefix is not added, Fyber opens the landing page in the embedded browser.

Native Browser Link Example
fybernativebrowser://navigate?url=http%3A%2F%2Fwww.google.com

URL Prefix: fybernativebrowser

Notes

  • The scheme must match exactly "fybernativebrowser"
  • The host path must match "navigate"
  • The URL must contains a single query param named "url"
  • The value for the parameter "url" must be -
    • Properly URL encoded
    • Should not contain any scheme other than "http" or "https"

For details on Smartlink, click here.