SDK Components

Document created by pubmatic-archivist on Mar 27, 2017
Version 1Show Document
  • View in full screen mode

Components of all Adtypes

Following are a list of components that are in all Adtypes.

Unique Device ID

Unique Device ID (UDID). This parameter is required by the adServer for proper targeting of the user. This device ID is determined by the SDK internally on behalf of the Publisher, and its MD5 value is appended to the adRequest before sending.

As of now, we are using the Windows Advertising ID for uniquely identifying a device. It is queried internally by the SDK and appended to the ad request. This feature can be enabled or disabled, based on the feature setting that the user has selected on their device. If the user resets this features, a different Advertising ID is retrieved the next time it is enabled.

Using the Windows Advertising Id, we ensure that it is in user‰ЫЄs control if he wants to be targeted or not, thus respecting his/her privacy.

 

Detecting Location

The SDK provides an API call for geo-targeting in all the adView configuration.

adView.EnableLocationDetection = true;

This code enables the SDK to start the GeoLocator and get the Latitude-Longitude information from device GPS.

Best practices: PubMatic recommends enabling GeoLocator for better targeting.

 

If the application itself uses GeoLocation, this feature need not be enabled. The publisher can simply pass the Location information in
SetLocation(double latitude, double longitude) function of the AdRequest object.

For example:

adRequest.SetLocation(18.437645,73.625344);

Note: (For PubMatic API only) - In case publisher provides the location data, then he must set LocationSource field correctly. Otherwise default value of LocationSource is considered as ‰ЫчUser_Provided‰ЫЄ.

 

In-App Browser:

SDK provides API for an In-App Browser.

     adView.UseInternalBrowser = true;

If set to true, when the user clicks on an ad, the user remains within the app, and the link is opened in the custom browser page provided by the SDK.

If the in-App Browser is false, the links are opened normally in the native browser for in the device, after leaving the app context.

 

Logging

SDK provides logging api to print out the logs pertaining to each ad format on the visual studio console. There are three levels of reporting provided by the enum ‰ЫчPubMaticSDK.Common.LogLevel‰ЫЄ namely None, Debug and Error. Developer can get helpful information in case of errors by using this feature.

For example,

                adView.LogLevel = LogLevel.Error;

Attachments

    Outcomes