All Products
Search

This Product

    Quick Tracking:Introducing and configuring the SDK

    Document Center

    Quick Tracking:Introducing and configuring the SDK

    Last Updated:Sep 25, 2025

    Basic SDK information

    SDK name

    Version number

    The md5 value.

    QTCommon

    Latest version: 1.7.3

    Update logs: iOS SDK update logs

    275e4bef3ffc919ca5e865a2d06140e9

    UMAPM_P

    2.2.0

    Update logs: iOS SDK update logs

    dd01741c718e44ea8f5ffe38ccc53c11

    UMEFS_P

    2.2.1

    Update logs: iOS SDK update logs

    44193d525e848c3e010e8b7f3ec81cba

    Integrate the QuickTracking SDK

    CocoaPods

    1. Add

      pod 'QTCommon'
pod 'UMAPM_P'
pod 'UMEFS_P'

    2. Open a terminal and switch to the project directory

    3. Run the pod install or pod update command

    4. If the latest version cannot be pulled, run the pod repo update first, and then run the pod install or pod update

    IDFA description

    1. By default, the SDK collects the idfa identifier to analyze and verify data more accurately. For the case that the application itself does not obtain idfa, it is recommended to configure the application as follows when submitting it to the AppStore: (in order to avoid being rejected by Apple for "the application does not contain advertising functions, but obtains the advertising identifier IDFA".)

    image

    1. The Quick Tracking SDK does not actively apply for the IDFA permission. If your app does not apply for the IDFA permission, Quick Tracking does not trigger the pop-up window of the client permission application. Therefore, you must configure the application in your app.

    2. If the user does not agree to collect IDFA, set a custom field or return an empty string. For more information, see 2.1 Device ID Settings. In this way, the Quick Tracking SDK does not collect IDFA.