Introduce the IQL Test Drive Program

When a user signs in to your application, you need to provide them with a choice to opt into the IQL Test Drive program. Once your users opt-in, you can present them with exciting auto insurance offers, customizing your Ads based on user performance. It's a great opportunity for you to entice the user to sign up by offering discounts for good driving behavior.

Your users will be able to monitor their own driving performance on the application and improve their driving behavior to earn better discounts. IQL keeps users motivated to bring down their insurance burden while emphasizing safe driving on our roads.

This section includes the following topics:

1.0. IQL Opt-in User Flow

When a user interacts with your application or program, you need to be able to distinguish between new and returning users. Returning users fall into different categories, as follows:

Users who have switched to a new phone.
Users who have uninstalled and reinstalled your application.
Users who have opted out of the program and want to rejoin.

In order to provide a seamless experience, we recommend using a slightly different messaging for returning users. Additionally, you can improve user experience by pre-filling forms or skipping screens entirely, as most of the necessary data will already be available to you. By implementing these strategies, you can differentiate new and returning users and provide a more tailored, user-friendly experience.

Here's an example of how a user opts in to the IQL program:

Retrieving and Storing Existing User Data

To enhance the user experience, it is important to retrieve and store any existing user data in the application. You can achieve this by deploying the driverInfo endpoint, to retrieve existing user data and save it within the application. Additionally, maintaining different states for the user can also help provide a better user experience.

enum UserState: String {
    case new
    case returning
    case unknown
}

We recommend that you call the driverInfo API to retrieve the user details and save the data locally in your application. By doing this, you can avoid calling this endpoint again, and enhance the application's performance.

class EntryViewController: BaseViewController {
    ...
    override func viewDidLoad() {
        ...
        if core.driveInfoRepository.getUserState() == .unknown {
            self.core.driveInfoRepository.fetchDriverInfo(completionBlock: nil)
        }
    }
}
class DriverInfoRepository: AbstractDriverInfoRepository {
    func fetchDriverInfo(completionBlock: ((Bool) -> Void)? = nil) {
        guard let driverId = coreReferance.loginRepository.currentUser?.driverId else {
            fatalError("User id doesn't exist")
        }
        apiManager.getDriverInfoDetails(driverId: driverId) { driverInfoData in
            if driverInfoData != nil { // this case is for returning user
                self.saveDriverInfoDetails(driverInfo: driverInfoData!)
                self.saveUserState(userState: .returning)
                completionBlock?(true)
            } else {
                self.saveUserState(userState: .new)
                completionBlock?(false)
            }
        } onFailure: { failureResponse in
            DDLogDebug("Failure - \(failureResponse)")
            DDLogDebug("End: Get Driver Info failed")
            self.saveUserState(userState: .unknown)
            completionBlock?(false)
        } onError: { error in
            DDLogDebug("Error - \(error)")
            DDLogDebug("End: Get Driver Info Error")
            self.saveUserState(userState: .unknown)
            completionBlock?(false)
        }
    }
}
class API {
    ...
    func getDriverInfoDetails(driverId: String,
                              onSuccess: ((_ driverInfo: DriverInfoDTO?) -> Void)?,
                              onFailure: ((_ failureResponse: FailureResponse) -> Void)?,
                              onError: ((_ error: APIError) -> Void)? ) {
        executeGetRequest(endpoint: .driverInfo,
                          pathParams: ["driver_id": driverId],
                          onSuccess: onSuccess,
                          onFailure: onFailure,
                          onError: onError)
    }
    ...
}

Retrieving Driving Insights for Returning Users

In order to provide a personalized experience for returning users, we recommend that you retrieve the user's existing driving insights, by using the driverStatus Endpoint. Once the data is retrieved, make sure it is saved within the application for easy access.

In addition to persisting the data, it's important to provide a reactivation experience for returning users. This could involve displaying their previous driving insights and offering personalized recommendations based on their previous behavior.

In the case of a new user, you could provide a new user experience by introducing the program and its features and getting started guidance. Use the following code snippets to retrieve and persist driving insights data for returning users.

class ExplainerViewController: BaseViewController {
    ...
    override func viewDidLoad() {
        ...
        checkDriverInfoStatus()
    }
    func checkDriverInfoStatus() {
        let userState = core.driveInfoRepository.getUserState()
        switch userState {
        case .new:
            // For a new user, we don't need to call the DriverStatus API.
            self.removeIndicatorView()
            break
        case .returning:
            // For a returning user, we need to call the DriverStatus API
            core.driveInfoRepository.fetchDriverStatus { success in
                if success {
                    self.iqlDriverStatus = self.core.iqlDriverStatusRepository.getDriverStatusDetails()
                    DispatchQueue.main.async {
                        self.updateReactivationData()
                    }
                }
                self.removeIndicatorView()
            }
            break
        case .unknown:
            // For an unknown user, we need to call the DriverInfo API again and call the same method to check for userState and update the DriverStatus details.
            core.driveInfoRepository.fetchDriverInfo { isReturningUser in
                if isReturningUser {
                    self.checkDriverInfoStatus()
                } else {
                    self.removeIndicatorView()
                }
            }
            break
        }
    }
}
class DriverInfoRepository: AbstractDriverInfoRepository {
    ...
func fetchDriverStatus(completionHandler: @escaping (Bool) -> Void) {
    guard let driverId = coreReferance.loginRepository.currentUser?.driverId else {
        fatalError("User id doesn't exist")
    }
    coreReferance.api.getDriverStatus(driverId: driverId) { driverStatus in
        self.coreReferance.iqlDriverStatusRepository.refreshDriverStatus(driverStatus: driverStatus)
        completionHandler(true)
    } onFailure: { failure in
        DDLogDebug("Failure - \(failure)")
        DDLogDebug("End: Update driver status Failed")
        completionHandler(false)
    } onError: { error in
        DDLogDebug("Error - \(error)")
        DDLogDebug("End: Update driver status Error")
        completionHandler(false)
    }
}
    ...
}
class API {
    ...
    func getDriverStatus(driverId: String, onSuccess: ((_ driverStatus: IQLDriverStatus) -> Void)?, onFailure: ((_ failureResponse: FailureResponse) -> Void)?, onError: ((_ error: APIError) -> Void)? ) {
        executeGetRequest(
            endpoint: .getDriverStatus,
            pathParams: ["driver_id": driverId],
            onSuccess: onSuccess, onFailure: onFailure, onError: onError)
    }
    ...
}

2.0. IQL Reference Application UX Screens

Here is the overall design implementation for the IQL Reference Application:

3.0. Publisher Integration Testing Checklist

Follow the below-given integration testing checklist while testing the user onboarding experience in your application:

Opt-in Process: Ensure that the program opt-in section is prominently displayed and easy to locate. This section should enable the user to provide their consent to be part of the IQL program.
How the Module Works: Ensure that there is a clear and concise explanation of how the program works and how the user will benefit from it.
FAQ: Ensure that the FAQ section (if provided) is easily accessible and contains accurate and helpful information for all users.
Program Activation: Ensure that the user experiences a clearly understandable, error-free capture user information flow.
Program Cancelation: If the user cancels program activation, be sure to display cancelation confirmation that reminds them of the value they are losing by canceling. Give your users an opportunity to reconsider.

PreviousUser Onboarding Experience NextEnable Zendrive SDK