Integration

Connect the app's miles® SDK to all of your app's features to start driving your users and build retention.
​ iOS Integration 
​ You have the app's miles banner up and running. 
Now you need to integrate the SDK deeper into your application so that your user can:
- understand how the program works.
- discover all the functionalities that you slaved away at developing !
- be rewarded for consistently using your application's main features.
I. Connection 
1. Onboarding 
Skip to the Connect section if you intend to have everyone participate in the program by default 
An onboarding example
​
Purpose
The first thing that the user will see when clicking on the app's miles banner is the onboarding.
This onboarding has two purposes:
​ Present and explain the program
​ Ask the user their consent to take part in the program
Onboarding choices
There are up to 3 buttons on the onboarding, and you must attach a listener in order to redirect the user depending on their input.
The input of the user will affect the variable OPT_IN in the following way:
(default: APM_DEVICE_OPT_IN_NOT_SET)
​ OK: APM_DEVICE_OPT_IN_ACCEPT
​ Later: APM_DEVICE_OPT_IN_NOT_SET
​ Never: APM_DEVICE_OPT_IN_REFUSE
Example with AbstractViewController lifecycle
@interface AbstractViewController() <APMOnboardingUtilsListener>
​
//...
​
// Declare an instance of APMOnboardingUtils in your class
@property (strong, nonatomic) APMOnboardingUtils* onboardingUtils;
​
@end
​
@implementation AbstractViewController
​
-(void)viewDidLoad
{
    [super viewDidLoad];
    //...
​
    // Make AbstractViewController listen to onboarding delegate
    self.onboardingUtils = [[APMOnboardingUtils alloc] init];
    self.onboardingUtils.delegate = self;
}
​
- (void)viewDidAppear:(BOOL)animated
{
    [super viewDidAppear:animated];
    //...
 
    // Start listening
    [self.onboardingUtils registerNotifications];
}
​
- (void)viewWillDisappear:(BOOL)animated
{
    [super viewWillDisappear:animated];
    //...
 
    // Stop listening
    [self.onboardingUtils unregisterNotifications];
}
​
#pragma mark - APMOnboardingUtilsListener
​
-(void)apmOnboardingButtonOkClicked
{
    // User clicked "OK" -> "I want to participate".
    // TODO: If user not connected, redirect to login/create-account page.
    // Nothing to do if user connected
}
​
-(void)apmOnboardingButtonLaterClicked
{
    // User clicked "Later" -> "I'll decide later".
    // The SDK will continue showing the onboarding when clicking the banner
    // Nothing to do here in general
}
​
-(void)apmOnboardingButtonNeverClicked
{
    // User clicked "Never" => "Stop asking me, hide the banner"
    // Note: The user may change his mind, and it is recommended to have a button
    // that allows the user to get back in the program
    // TODO: (Optional) You can redirect to the page with that "Get back in the program" button
    // (with a little message saying "You can always change your mind by clicking this button")
}
​
@end
Connected or non-connected
There can be two different onboardings: 
for non-connected users
for connected users
Both of these onboardings only appear if the user has not decided whether they want to opt in or not.
An onboarding only appears if the optIn value is NOT_SET. 
If you want to force the optIn and still wish to present the program, it is better to use tutorials or walkthroughs (both can be configured in our BackOffice and require no code).
2. Connect 
In order to offer a seamless experience, app's miles doesn't have a login or create-account page. The login/create-account process for app's miles is parallel to yours. 
[APMUIServicesUser userClientConnect]
This method can both connect and create an account:
If an app's miles account already exists with the given userID, the method signs them in.
If no account exists, the method will automatically create their account and sign them in.
This method needs : « email », « userID » and « optIn »
– « email » is the email of user
– « userID » is a unique identifier in your database
– « optIn » is the RGPD OptIn
If you don’t want give the email, you can build a encrypted email with the userID: {userID}@{your-company-name}.com (e.g. 123456789@appsmiles.fr)
NSString* email = _textFieldEmail.text; //Required 
NSString* userId = _textFieldUserId.text; //Required 
​
//optIn, APM_DEVICE_OPT_IN_NOT_SET, APM_DEVICE_OPT_IN_REFUSE, APM_DEVICE_OPT_IN_ACCEPT 
NSNumber* optIn = APM_DEVICE_OPT_IN_ACCEPT; //Required 
​
[APMUIServicesUser userClientConnect:email 
                     partnerClientId:userId 
                               optIn:optIn 
                  userConnectSuccess:^(APMUser *user) {     
    NSLog(@"%@ --> connected !", user); 
} failure:^(NSError *error) {     
    NSLog(@"%@", error); 
}];
3. Logout 
The same way the login process is parallel to yours, so is the logout
[APMUIServicesUser userLogout]
[APMUIServicesUser userLogout:^{
    UIAlertView *alert = [[UIAlertView alloc] initWithTitle:@"Logout" message:@"Logout success" delegate:nil cancelButtonTitle:@"Ok" otherButtonTitles:nil];
    [alert show];
} failure:^(NSError *error) {
    UIAlertView *alert = [[UIAlertView alloc] initWithTitle:@"Logout" message:error.localizedDescription delegate:nil cancelButtonTitle:@"Ok" otherButtonTitles:nil];
    [alert show];
}];
II. Tagging plan 
1. Send an action 
In order to reward the user for an action, you need to place triggers in your application. You will need to follow the Tagging plan that your marketing team created with us.
Be careful with the spelling, an extra character like a 's' will change the tag
Call the method triggerAction to send a tag
#import <APM/APMHeaders.h>
​
.....
​
[[APM sharedInstance] triggerAction:@"display_product"]; //"display_product" --> actionName
Make sure to test each action by looking at the logs, especially for actions that are complex
Earn animation
2. Actions with properties
If your tagging plan requires the use of filters, you may need to send properties with your action.
Call triggerAction with a second parameter to send a tag with properties
– property.key : Property keys must be strings and must be in the tagging plan (e.g. « zipcode », « establishment »).
– property.value : Property values must be strings. (e.g. « 33000 », « restaurant »).
NSMutableDictionary* properties = [NSMutableDictionary dictionary];
properties[@"zipcode"] = @"33000";
properties[@"establishment"] = @"restaurant";
[[APM sharedInstance] triggerAction:@"write_review" properties:properties];
This example tag will match with the action « Write a review of a restaurant in Bordeaux ».
A tag may have multiple versions configured in our BackOffice. 
This is an unlikely scenario, but as an example, sending the same tag and properties 3 times may match with a different version each time.
3. User properties
Just like for 2. Send an action with properties, if your tagging plan requires the use of filters, you may need to send us userProperties so that we can offer filtered actions to the user.
Use the class APMUserPropertiesUtils to manager user properties fo user.
key : Property keys are strings. (e.g. « zipcode », « profession »).
value :Property values are strings. (e.g. « 33000 », « doctor »).
You can add user properties with the followings methods :
​Adding user properties 
-(void)addUserProperty:(NSString*)userProperty forKey:(NSString*)key;
-(void)addUserProperties:(NSDictionary*)userProperties;
Example:
// Single userProperty
[[APMUserPropertiesUtils sharedInstance] addUserProperty:@"premium" forKey:@"membership_level"];
// Multiple userProperties
NSMutableDictionary* userProperties = [NSMutableDictionary dictionary];
userProperties[@"zipcode"] = @"33000";
userProperties[@"membership_level"] = @"premium";
[[APMUserPropertiesUtils sharedInstance] addUserProperties:userProperties];
Adding a userProperty with a key that already exists will update it.
​Removing user properties
If a userProperty is no longer valid, you can remove it (example: user does not wish to be geolocated anymore)
-(void)removeUserProperty:(NSString*)key
-(void)removeUserProperties
Example:
// Single userProperty
[[APMUserPropertiesUtils sharedInstance] removeUserProperty:@"zipcode"];
// All userProperties
[[APMUserPropertiesUtils sharedInstance] removeUserProperties];
​Refreshing after a change 
If you have changed a userProperty that may have an impact on the actions that we can propose to the user, you will want to refresh the SDK (i.e. tell it to communicate with our API to get updated info).
You can do this by calling:
[[APMServices sharedInstance] refreshSDK:YES];
4. Action's deeplink 
We showcase one action above others (Challenge of the day). 
Each action can be configured in our BackOffice with a deeplink so that the user can go to the screen where they can perform the action.
Clicking on a suggested action's deeplink
To listen to the click on the "Let's go !"  button and get the deeplink URI, you need to use APMDeepLinkActionUtils and APMDeepLinkActionUtilsListener.
Example with AbstractViewController lifecycle.
@interface AbstractViewController() <APMDeepLinkActionUtilsListener>
​
//...
​
// Declare the APMDeepLinkActionUtils variable in your class
@property (strong, nonatomic) APMDeepLinkActionUtils* deepLinkActionUtils;
​
@end
​
@implementation AbstractViewController
​
-(void)viewDidLoad
{
    [super viewDidLoad];
    //...
 
    // Have the activity listen to deeplink events
    self.deepLinkActionUtils = [[APMDeepLinkActionUtils alloc] init];
    self.deepLinkActionUtils.delegate = self;
}
​
- (void)viewDidAppear:(BOOL)animated
{
    [super viewDidAppear:animated];
    //...
 
    // Start listening
    [self.deepLinkActionUtils registerNotifications];
}
​
- (void)viewWillDisappear:(BOOL)animated
{
    [super viewWillDisappear:animated];
    //...
 
    // Stop listening
    [self.deepLinkActionUtils unregisterNotifications];
}
​
#pragma mark - APMDeepLinkActionUtilsListener
​
-(void)apmDeepLinkActionButtonGoClicked:(NSString *)url action:(NSString *)action params:(NSMutableDictionary *)params
{
    // The user clicked the "Let's go" button.
    // The big badge will automatically close
    // TODO: Use the deeplink to navigate the user to the indicated screen.
}
​
@end
III. Advanced functions 
1. Show/Hide badge 
You can hide the badge if you have a screen where you don't want the user to be distracted (e.g. checkout).
You can hide the badge with the method:
[[APM sharedInstance] hideBadge];
And show the badge:
[[APM sharedInstance] showBadge];
Make sure to show the badge again once you leave the screen or the user may never see it again !
Day... Night...
While the badge is hidden, the SDK continues to work. If there are triggerActions, the notifications will happen once the badge is shown.
2. Activate debug logs​
Logs are quire useful, right ?
Here's how to unleash the (controlled) fury of debug logs:
[APM sharedInstance].debugMode = YES;
iOS logs from console.app
3. Listen for changes to a user
You can be notified when one of the user's attribute changes with the class APMServicesUserListener. 
Set a listener with:
[APMServices sharedInstance].servicesUserListener = self;
Get the callback with the method apmServicesUserChanged
#pragma mark - APMServicesUserListener
-(void)apmServicesUserChanged:(APMUser *)user
{
    NSLog(@"apmServicesUserChanged : %@", user);
}
4. RGPD
You can disabled some features for RGPD compliances
//Disabled localization of user for SDK app's miles
[[APMGeolocUtils sharedInstance] setGeolocEnabled:NO];