Third-party Data Integration
|
Collect
If your app is running overseas ads to acquire new users and you want to differentiate the channel sources of overseas users and integrate the analysis of advertising platforms and user behavior within your app, it is recommended to use the "Third Party Data Integration" feature in Sensors Analystics - Channel Track.
Current Situation of Overseas Attribution
Overseas markets attach great importance to user privacy protection policies, and most overseas media channels (such as Google Ads/Meta Business/TikTok Business, etc.) have very strict advertising regulations, and they do not directly open monitoring and attribution interfaces to domestic channels.
Meanwhile, overseas media channels cooperate with overseas attribution service providers such as Appsflyer and Adjust. Therefore,SensorsData integrates with these attribution service providers and indirectly obtains overseas media channel information through the already-attributed activation data provided by these service providers.
Integration Principle Introduction
1. SensorsData integrates with the SDK of the attribution service provider. When the attribution service provider SDK reports user behavior, it includes the unique user identifier ofSensorsData. After receiving user behavior, the attribution service provider independently completes overseas channel attribution.
2. Users configure data receiving and feedback functions in SensorsData's backend and the attribution service provider's backend. The attribution service provider continuously feeds back attribution data toSensorsData‘s analysis system in real-time.
3. After receiving the data,Sensors Analystics's system logs and records each attribution result based on SensorsData E-U rules, allowing SensorsData to query overseas channel attribution results based on the unique identifier when reporting user behavior.
Core Integrated Functions
1. Supports receiving raw data at the user level from the attribution service provider, and stores the data according to the event-user data format as needed.
2. Supports recording each newly acquired attribution result from the attribution service provider and associating it with the user behavior reported bySensorsData SDK.
3. Supports adding all channel message fields that the attribution service provider can feedback as needed, to meet the flexible analysis needs of users.
Comparison with the Old Version
The new version of "Third Party Data Integration" has basically the same customer demands as the original "Overseas Attribution" service, but in order to better integrate external data with the product experience, the new version has made important upgrades in data flow and product functions.
Details are as follows:
1. In terms of data connection, the "Device ID matching" is upgraded to "Shenze User ID Matching". The coverage of user behavior is wider, and the accuracy is higher.
Due to the impact of overseas user privacy protection policies, the availability of valid device IDs is scarce, and the accuracy and coverage of "Device ID Matching" are limited. After adopting "Sensors Data User Identity Matching", the Sensors Data ID can be included when reporting user behavior on the Mobile Measurement Platform (MMP), significantly increasing the number of users with data connectivity.
2. In terms of data reception, after successful matching, only the "Channel Matching Result Activation Event" was written, but now it can be upgraded to write "Any MMP Callback Event" on demand. The data source reception is more complete, facilitating data comparison and analysis.
Originally, only the "Channel Matching Result Activation Event" ($ChannelMatchedInstall) was written after a successful match. Now it can be upgraded to configure MMP callback events and corresponding Sensors Data storage events as needed.
It should be noted that receiving and writing events will consume the billing event volume in the Sensors Analytics package, so it is recommended to configure it as needed.
3. In terms of attribution analysis, it has been upgraded from relying on the overseas channel source in the "Channel Matching Result Activation Event" to independently generating a "Third-Party Attribution Record Table". It supports querying the overseas third-party attribution results for any user behavior reported by Sensors Data.
Originally, only the channel source corresponding to the successful activation event was recorded. After the upgrade, every attribution result of MMP can be recorded, and subsequent user behavior can be queried with related overseas channel sources.
4. Due to the closure of Branch's China business in Q3 2023, the new version no longer supports data integration with Branch as an MMP platform. It is recommended that customers choose to switch to AppsFlyer or Adjust as needed.
Note
Due to the significant differences between the new and old versions in terms of product features and data flow, the following steps are required after the upgrade:
1. Stop sending and receiving data from the old version
2. Reconfigure the client SDK and data receiving function according to the new version process
3. The new version does not support the migration of historical data
Note: The content of this document is a technical document that provides details on how to use the Sensors product and does not include sales terms; the specific content of enterprise procurement products and technical services shall be subject to the commercial procurement contract.
Popular Searches