[IASDKCore.sharedInstance setGDPRConsentString:@"abcdef"];

Downloading and Setting Up the SDK

To download the DT Exchange iOS SDK, click here:

Starting the Process

• If you use the CocoaPods Dependency Manager, see Integrating with CocoaPods and then refer to Initializing the SDK.
• The DT iOS SDK requires, at minimum, an iOS 11 target and is fully compatible with iOS 17.

Step 1: Integrating the Libraries

1. Drag the IASDKCore library to your Xcode project.
   The Choose options for adding these files pop-up screen appears.
2. Select the Copy items if needed and Create Groups checkboxes.
3. From Application target→Build Phases, click Link Binary With Libraries to verify the linkage of the app target with the IASDKCore library.
4. If missing, drag the IASDKCore library to the Link Binary With Libraries section, which links your project with the IASDKCorelibrary and adds a required path to the Framework Search Paths.
5. Import the IASDK into the AppDelegate class:

#import <IASDKCore/IASDKCore.h>

Step 2: Initializing the SDK

SDK initialization is mandatory because the DT SDK relies on the Console configuration for functionality. Without this configuration, no ad units will display, and the SDK will not operate. DT recommends that you perform it at the app's initialization stage.

The following takes place during the initialization phase:

• Initialization of SDK.
• Remote configuration fetching, parsing, loading, and local configuration update.

1. Add the following code inside the method in AppDelegate class 

application:didFinishLaunchingWithOptions:

2. Run the following command:

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

Step 3: Configuring Apple Requirements

Adhering to Apple's requirements ensures that your app complies with its privacy guidelines, as described in ATS Configuration for DT Exchange SDK. 

Configuring Tracking Permission Alerts With ATT Framework for iOS 14+

The AppTrackingTransparency (ATT) framework requires a user authorization request for app tracking. The tracking authorization status is then returned based on the user's selection.

DT uses the ATT framework in iOS 14 and above to retrieve user authorization statuses. For more information, see App Tracking Transparency.

SKAdNetwork Attribution Solution

The SKAdNetwork API enables advertisers to measure app installs in a privacy-aware manner in iOS 14 and above. Configuring SKAdNetwork IDs is crucial to monetizing with DT Exchange since it allows  DSPs to credit your app with installs. DT recommends that you include SKAdNetwork IDs in the info.plist file to maximize revenue potential.

Getting the SKAdNetwork IDs

The SKAdNetwork IDs for DT and DT buyers are available in two formats. These files are regularly updated. Select one of the following links to retrieve the latest SKAdNetwork IDs:

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

Configuring the SKAdNetwork IDs 

The SKAdNetwork helps track app installs in a privacy-friendly way. Do the following to configure your app with SKAdNetwork IDs:

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

2. In the property list editor, click Add (+) beside a key and press Return.

3. In the field, type the key name SKAdNetworkItems.

4. From the pop-up menu in the Type column, select Array.

5. Create an array that contains one dictionary for each of DT's recommended SKAdNetwork IDs with the single-key SKAd Network Identifier . The string value for the key is the ad network identifier.

SKAdNetwork ID Manager

The SKAdNetwork IDs Manager tool identifies and manages SKAdNetwork IDs. This tool processes and deduplicates SKAdNetwork IDs for all buyers on DT Exchange and then generates a finalized Info.plist output for streamlining integration into your app. The tool enables you to add other SKAdNetwork IDs to your final Info.plist file.

To configure SKAdNetwork IDs, see Configuring a Source App.

Step 4: Adding Delegates

Delegates manage various events and interactions related to ads. Depending on your integration, add delegate information to your iOS integration.

Different delegates are required; select the following necessary delegates:

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

For further information, see Delegate Protocols. 

[IASDKCore.sharedInstance setGDPRConsent:YES]

[IASDKCore.sharedInstance setGDPRConsentString:@"abcdef"];

`IASDKCore.sharedInstance.CCPAString = `

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

IASDKCore.sharedInstance.CCPAString = nil;

IASDKCore.sharedInstance().lgpdConsent = .given
IASDKCore.sharedInstance().lgpdConsent = .denied

[[IASDKCore sharedInstance] setLGPDConsent:IALGPDConsentTypeGiven]; 
[[IASDKCore sharedInstance] setLGPDConsent:IALGPDConsentTypeDenied];

IASDKCore.sharedInstance().coppaApplies = .given

IASDKCore.sharedInstance.coppaApplies = IACoppaAppliesTypeGiven;

@property (atomic, nullable) NSString *userID*

IASDKCore.sharedInstance.userID = @"User_123456"

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

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