source 'https://github.com/CocoaPods/Specs.git'
target 'MyApp' do
  pod 'MobileFuseSDK'
end

@import MobileFuseSDK;

The MobileFuse SDK supports privacy configurations that can be managed using an IAB compatible US Privacy String, and IAB Consent Framework strings for GDPR. You can also notify the SDK whether your user subject to COPPA, due to them being under 13 years of age.

The following snippet demonstrates configuration for the US privacy and COPPA compliance:

MobileFusePrivacyPreferences *privacyPreferences = [[MobileFusePrivacyPreferences alloc] init];
[privacyPreferences setSubjectToCoppa:NO]; // Shound be YES if user is under 13 years of age
[privacyPreferences setUsPrivacyConsentString:@"<US Privacy String>"]; // e.g. 1YNN

[MobileFuse setPrivacyPreferences:privacyPreferences];

GDPR for European users

For your European users, you must supply an IAB-compatible privacy consent string. The following example shows how to declare consent for a user which is subject to GDPR due to being located in an EAA country. Note that this should be invoked on the same MobileFusePrivacyPreferences object as above.

MobileFusePrivacyPreferences *privacyPreferences = [[MobileFusePrivacyPreferences alloc] init];
[privacyPreferences setIabConsentString:@"<IAB Consent String>"];

[MobileFuse setPrivacyPreferences:privacyPreferences];

You must also ensure that you have implemented the Apple App Tracking Transparency Framework into your app before any ad calls. This sample code shows how you can request the authorization. If authorization has already been granted, then the callback will immediately fire with the correct status, therefore it’s advisable to call the requestTrackingAuthorizationWithCompletionHandler method every time your app launches.

#import <AppTrackingTransparency/AppTrackingTransparency.h>

// ...

- (void)requestAppTracking {
    [ATTrackingManager requestTrackingAuthorizationWithCompletionHandler:^(ATTrackingManagerAuthorizationStatus status) {
        switch (status) {
            case ATTrackingManagerAuthorizationStatusNotDetermined:
                NSLog(@"ATT - Request not determined");
                break;
            case ATTrackingManagerAuthorizationStatusRestricted:
                NSLog(@"ATT - Request restricted");
                break;
            case ATTrackingManagerAuthorizationStatusDenied:
                NSLog(@"ATT - Request denied");
                break;
            case ATTrackingManagerAuthorizationStatusAuthorized:
                NSLog(@"ATT - Request authorized");
                break;
        }
        
        // Run the initialization on our main thread:
        dispatch_async(dispatch_get_main_queue(), ^{
            [self initMobileFuseSdk];
        });
    }];
}

If you don’t have an App ID for the SDK, please ask your MobileFuse contact. You’ll be given a unique App ID for each app and each platform that you publish to.

// ...

- (void)viewDidLoad {
    [super viewDidLoad];
    [self requestAppTracking]; // Will call initMobileFuseSdk when ATT has been resolved.
}

- (void)initMobileFuseSdk {
    [MobileFuse initWithAppId:@"00000" withPublisherId:@"0000" withDelegate:self];
}

// IMFInitializationCallbackReceiver delegate implementation
- (void)onInitSuccess:(NSString *)appId withPublisherId:(NSString *)publisherId {
    NSLog(@"SDK Initialization successful");
}

- (void)onInitError:(NSString *)message forAppId:(NSString *)appId withPublisherId:(NSString *)publisherId {
    NSLog(@"SDK Initialization failed: %@", message);
}