Registering WebView

Starting from NAM iOS SDK version 8.2.0, any WKWebView that may display ads via the NAM Web SDK must be registered. This is a key feature for improving ad targeting accuracy and enhancing ad revenue in your app by enabling communication with websites that use the Web SDK.

If you are using WKWebView, including in web apps, you must apply the GFPAdManager.register(_:) interface. If there are N web views, you must apply it to all N web views.

How to Register a WebView

Apply GFPAdManager.register(_ webView: WKWebView) to the target web view. All subsequent ad targeting operations are handled automatically within the SDK.

• It is recommended to register the WebView before rendering it.
• This operation does not modify any settings on the WebView instance, nor does it store or retain a reference to the WebView instance.

Swift

let webView = WKWebView()
GFPAdManager.register(webView)

Objective-C

WKWebView *webView = [[WKWebView alloc] init];
[GFPAdManager registerWebView:webView];

WebView Cookie Policy Configuration

The Cookie Accept Policy of the WebView must be set to at least .onlyFromMainDocumentDomain; .always is recommended whenever possible.

Swift

HTTPCookieStorage.shared.cookieAcceptPolicy = .always

Objective-C

[NSHTTPCookieStorage.sharedHTTPCookieStorage setCookieAcceptPolicy:NSHTTPCookieAcceptPolicyAlways];

Checking WebView Registration Status

Swift

GFPAdManager.examineWebViewStatus(webView) { javaScriptError, results in
    let isRegistered = results["isRegistered"] as? Bool ?? false
}

Objective-C

[GFPAdManager examineWebViewStatus:self.webView completion:^(NSError *javaScriptError, NSDictionary *results) {
    BOOL isRegistered = [results[@"isRegistered"] boolValue];
}];