Quick Tracking:Introducing and configuring the SDK

Basic SDK information

1 Quick integration

In the background of QuickTracking, dedicated integration code is generated for each App, which can be integrated according to the guidance in the product. Check whether you have used the Umeng + SDK. If you have used the SDK, change the SDK file path in a timely manner. For more information, see 1.6 in this document.

1.1 into the product background

1.2 Find Application Organization

1.3 find application

1.4 click "To Integrate"

1.5 Click to obtain the exclusive integration code

1.6 check whether it conflicts with Umeng + SDK

Note that you need to check whether you have already used the Umeng + SDK. If you have already used it, be sure to set the change SDK file path.

2 Integration code details

If the preceding page cannot be reached due to specific reasons, you need to view the document before you can integrate it. The specific integration code is as follows:

2.1 Parameter Preparation

appkey: obtained from the application list

Collection domain name: obtained in the "Management Console-Collect Information" module

2.2 introduce the SDK

If you run the pod setup command on the terminal, it takes a long time to pull the latest pod library.

$ pod setup

Cocoapods integration can flexibly configure the required SDK. If the project target is named "QuickTrackingDemo", the following SDK can be added, such as the format of Podfile root directory the project:

target 'QuickTrackingDemo' do     
pod '<Quick Tracking SDK name>' 
end

Note: We recommend that you use the pod update command to directly update new items because the pod search command may fail to find new items.

Quick Tracking Base Library

//QuickTracking statistical analysis SDK
pod 'QTCommon', '~> 1.6.6.PX'// Specify the version number.
 
// You can add the UMCCommonLog in the basic Logstore to the project for development and debugging. 
pod 'UMCCommonLog'

Note: UMCCommonLog is used to debug the SDK and related features during the development phase. You can remove the SDK before you publish the app.

2.3 manual integration

Dependent libraries:

Obtain the operator ID by

CoreTelephony.framework
    
libz.tbd Data Compression
    
libsqlite3.tbd Data Cache
     
SystemConfiguration.framework to determine the network status

libc++.tbd C++ Standard Library 

Engineering configuration:

2.4 introducing header files

#import <QTCommon/QTCommon.h>
# import <UMCommonLog/UMCommonLogManager.h> // You need to add 

the

3. Verify the configuration of the tag

Add your URL Scheme to the project. The URL Scheme is located in the project settings target -> tab Info ->URL Types. The scheme:atm.yourappkey. Call function [QTMobClick handleUrl:url] in AppDelegate to receive URL

AppDelegate calls:

- (BOOL)application:(UIApplication *)application openURL:(nonnull NSURL *)url options:(nonnull NSDictionary<UIApplicationOpenURLOptionsKey,id> *)options
{
    if ([QTMobClick handleUrl:url]) {
        
      return YES;
    }

    return YES;
}

SceneDelegate calls:

- (void)scene:(UIScene *)scene willConnectToSession:(UISceneSession *)session options:(UISceneConnectionOptions *)connectionOptions {

    for (UIOpenURLContext *context in connectionOptions.URLContexts) {
        [QTMobClick handleUrl:context.URL];
    }
}

- (void)scene:(UIScene *)scene openURLContexts:(NSSet<UIOpenURLContext *> *)URLContexts {

    [QTMobClick handleUrl:URLContexts.allObjects.firstObject.URL];
}

4 IDFA description