Additional SDK integration guide

Attribute mobile users to TV ads aired in specific locations and at specific times.

Measure the uninstall rate of users coming from different sources. Uninstall measurement can help you to analyze and optimize your campaigns according to this significant KPI.

Learn how to set up uninstall measurement.

In pre-install campaigns, app owners contract with device manufacturers (OEMs) to pre-install their apps. 

With AppsFlyer, you can easily attribute installs of pre-installed apps. When users launch your app for the first time, AppsFlyer attributes the install to the preload partner as a media source.

By default, at least 5 seconds must pass between two app launches to count as two separate sessions. Learn more about counting sessions.

Setting a high value to the custom time between launches can impair APIs that rely on session data, such as deep linking.

You can manually report user sessions. This can be useful for utility apps that run in the background.

Some 3rd party services, such as email service providers, wrap links in emails with their own click recording domains. Some even allow you to set your own click recording domains. If OneLink is wrapped in such domains, it might limit its functionality.

To overcome this issue, your developer needs to configure the app using these APIs:

AppsFlyer supports the measurement of push notification campaigns from all vendors, including Google Cloud Messaging and Apple push notification services.

Learn more about push notification measurement.

Allowing your existing users to invite their friends and contacts as new users to your app can be a key growth factor for your app. With AppsFlyer, you can attribute and record installs that originate from user invites within your app.

Learn more about user invite attribution.

App owners that use App Links or Universal Links for deep linking (without OneLink), can configure the SDK to attribute sessions initiated via the domain associated with their app (Android/iOS).

For example:

• A user searches Google and clicks on your domain, www.example.com.
• If the user doesn’t have the app installed, they are directed to the website (www.example.com).
• If the user has the app installed on their device, they are deep linked into the app associated with www.example.com. The session is attributed to the media source (pid parameter) configured in the SDK. 

Developer documentation is available as follows:

• Android SDK reference
• iOS SDK reference

Tip! OneLink Smart Script can help app owners convert website visitors to app users.

In some instances, you might need to instruct your developer to set the AppsFlyer SDK to stop or limit data collection, (for example, to comply with GDPR and CCPA regulations). There are different methods to preserve the privacy of users on the SDK. For more information about the various methods, see Privacy preserving methods in the SDK article.

In some cases, advertisers may want to stop sharing user-level data with ad networks/partners for specific users. Reasons for this include: 

• Privacy policies such as CCPA or GDPR
• User opt-out mechanisms
• Competition with some partners (ad networks, third parties)

Data sharing with partners is controlled via the setSharingFilterForPartners method:

As part of the EU Digital Marketer Act (DMA) legislation, big tech companies must get consent from European end users before using personal data from third-party services for advertising.

To comply with the legislation, Google requires AppsFlyer customers to include specific consent fields when sending events originating from EU end-users to Google. The AppsFlyer SDK (Android - v6.13.0+, iOS - v6.13.1+) can send the necessary consent data with each event to meet this requirement.

The SDK offers two alternative methods for gathering consent data:

• Through a Consent Management Platform (CMP): If the app uses a CMP that complies with the Transparency and Consent Framework (TCF) v2.2 protocol, the SDK can automatically retrieve the consent details.

  OR

• Through a dedicated SDK API: Developers can pass Google's required consent data directly to the SDK using a specific API designed for this purpose.

To implement user consent data collection for DMA compliance see our Dev Hub guides:

Use the strict-mode SDK to completely remove IDFA collection functionality and AdSupport framework dependencies (for example, when developing apps for children).

If you market apps for children, your developer needs to install the strict-mode SDK instead of the regular SDK. Note: IDFV remains available.

To disable the AdSupport and iAd frameworks, the SDK provides the following setters: