Initializing the SDK

[IASDKCore.sharedInstance initWithAppID:@"YOUR APP ID"
                        completionBlock:^(BOOL success, NSError * _Nullable error) {}
                        completionQueue:nil];

For details of advanced SDK init integration, click here.

Locating your Spot ID App ID

Make sure you enter the correct credentials. Follow the instructions below to find your Spot ID and App ID:

From the Inventory window, select the app for which you want to locate the ID.

The Spot ID is located in brackets, next to the spot name.  Click on it to save the ID to the clipboard.

To locate the App ID, click the three horizontal dots at the end of the row and then click Integration Options:

The Info window opens and your App ID and SDK information is displayed:

Step 3: Apple Requirements

There are some additional Apple Requirements.  Click here to review the requirements.

Configuring Tracking Permission Alerts With ATT Framework for iOS 14+

The AppTrackingTransparency (ATT) framework works by presenting an app-tracking authorization request to the user. The tracking authorization status is then returned based on the user's selection.

According to Apple, apps must use the AppTrackingTransparency framework if they collect data about end-users and share this with other companies for purposes of tracking across apps and websites.

Fyber uses the ATT framework, in iOS 14 and above, to retrieve users' authorization statuses.  For more information about ATT, click here. 

SKAdNetwork Attribution Solution

Apple created the SKAdNetwork API for advertisers to measure app installs in a privacy-aware manner in iOS 14 and above. Configuring SKAdNetwork IDs is a crucial aspect of monetizing with Fyber Marketplace since it allows our DSPs to credit your app with installs. It is highly encouraged that all of Fyber's recommended SKAdNetwork IDs are added to your info.plist to maximize your revenue potential.

To configure your app with SKAdNetwork IDs,

1. Select  Info .plist  in the Project navigator in Xcode.

2. Click the Add button (+) beside a key in the property list editor and press Return.

3. Type the key name SKAdNetworkItems.

4. Choose Array from the pop-up menu in the Type column.

5. Create an array that contains one dictionary for each of Fyber's recommended SKAdNetwork IDs using the single key  SKAd Network Identifier . The string value for the key is the ad network identifier.
6. To discover the SDAdNetwork IDs, you can also use Fyber’s SKAdNetwork IDs Manager. This tool processes and deduplicates SKAdNetwork IDs for all buyers on Fyber Marketplace, and then generates a finalized Info.plist output for you, for easy integration into your app. The tool also lets you add any other SKAdNetwork IDs you have to your final Info.plist

For more information, refer to the Apple specification for configuring SKAdNetwork IDs.

SKAdNetwork IDs

The SKAdNetwork IDs for both Fyber and Fyber buyers are available in two formats. These files are regularly updated.  The most up-to-date SKAdNetwork IDs can be found here:

• SKAdNetwork IDs in JSON format
• SKAdNetwork IDs in XML format

Step 4: Adding Delegates

Depending on your integration, you must add delegate information to your iOS integration at this point.

Different delegates are required. Have a look below and select the necessary delegates.

Click here for details of: 

• Global Ad Delegate Protocol
• Unit Delegate
• Video Content Delegate
• HTML / MRAID Delegate

Initializing the App

Initialization is an expensive operation. We recommend performing it at the initialization stage of the app.

The previous SDK had no requirement to explicitly initiate it (as opposed to the Android version SDK). It initialized itself dynamically (lazy loading) on the first code request to the SDK itself.

We defined the initialize process as mandatory because the Fyber SDK relies on the Revenue Console configuration. Without this configuration, no ad unit is shown and the SDK will not work.

The following takes place during the initialization phase:

• Initialization of all installed modules
• Local configuration load process (in case it is not a first runtime)
• Remote configuration fetching, parsing, loading and local configuration update.

GDPR

The General Data Protection Regulation of the European Union requires you to scope your user's consent. A user could be within the GDPR scope for your app when one or all of the following apply:

• The user is currently located in the EU
• The user has registered with the app as an EU resident
• The app is specifically targeted to EU users

We recommend you consult with a legal advisor to determine the best approach for your business. It is also highly recommended to collect user consent with a certified Consent Management Platform (CMP).

For a full list of CMPs, click here.

Once you have collected the user’s consent, you can pass it into the SDK using the following API of setGDPRConsent:, e.g:

[IASDKCore.sharedInstance setGDPRConsent:YES]

GDPRConsent is a boolean. It is true if you have the user’s consent. If you do not have the user's consent, it is false.

GDPRConsentString is a string.

It is highly recommended to use the 2nd option of passing a consent string per the IAB's Transparent & Consent Framework by using a valid CMP (Consent Management Platform). This is the most common form of consent communication worldwide and is crucial in order to enjoy ad monetization in the EU. Using the boolean option is inferior and will eventually be deprecated during 2020.

We recommend that the first time you gather the user’s consent, you pass it onto the SDK before starting the SDK. The SDK then takes the user’s consent into consideration when initializing. In the following sessions, you need only call the API if the user updates their consent.

Setting Consent String

To set the GDPR Consent String, use the: setGDPRConsentString:
The consent string is passed as is.

Example

[IASDKCore.sharedInstance setGDPRConsentString:@""];

More information on GDPR can be found under the GDPR Resource Page and FAQs.

CCPA

The intention of the California Consumer Privacy Act of 2018 (CCPA) is to protect the personal information of California residents. CCPA applies to all companies doing business in California. If a California resident uses an app developer’s mobile app, CCPA applies to the developer and every company that processes the personal information of the app’s users.
CCPA came into effect on 1 January 2020.

For more information on Fyber and CCPA, refer to Fyber’s Resource Page.
For more information about CCPA, refer to the IAB CCPA Compliance Framework.

CCPA API

Once you have the CCPA string, you can pass it to the SDK using the following API:

API

`IASDKCore.sharedInstance.CCPAString = `

Example

IASDKCore.sharedInstance.CCPAString = @"1YNN";

To determine what value to use for the US Privacy String, refer to the IAB document here.
Example values:

• When CCPA does not apply (for example if the user is not a resident of California) you can either skip this API or use the following value 1---
• If the user choses NOT to opt out, and is ok with advertising as usual, you can use 1YNN
• If the user chooses to restrict advertising and opt out, you can use 1YYN

To clear the CCPA provided data, just pass a nil.

Clear Privacy Setting

IASDKCore.sharedInstance.CCPAString = nil;

Step 6: Setting a User ID (Optional)

Follow these steps for setting a User ID.

Setting a User ID

We have added an API for setting a User ID.

There is no need to pass it on every session as we cache it on the device.

To reset it from a device, pass a nil or an empty string.  The User ID is sent as is, without any validation or modification. 

@property (atomic, nullable) NSString *userID;

Example:

IASDKCore.sharedInstance.userID = @"User_123456";

Introspection (reflection) integration

Class IASDKCore = NSClassFromString(@"IASDKCore");
SEL sharedInstanceSelector = NSSelectorFromString(@"sharedInstance");
SEL setUserID = NSSelectorFromString(@"setUserID:");
id sharedInstance = [IASDKCore performSelector:sharedInstanceSelector];

[sharedInstance performSelector:setUserID withObject:@"User_123456"];