ネイティブPCアトリビューションについて
Native PC runs across Windows devices, through the installation of an .EXE or .MSI file extension.
This is different than the AppsFlyer Windows SDK 2.4.1 which works with installs from the Microsoft App Store, Windows phones, and UWP.
Apps running on PC can integrate with AppsFlyer via S2S API or SDK to receive attribution data and performance measurements about which sources and campaigns drive app open and in-app events. Marketers rely on these insights to measure and optimize marketing activities.
アトリビューションフローの例
The following is an example flow that highlights the most important steps in a user journey from ad engagement to attribution. これには、AppsFlyerが推奨するクロスプラットフォームのランディングページが含まれています。 Note: While we recommend using the cross-platform landing page, you can also use direct attribution links
- Marketing touchpoint: Customers interact with your brand through online or offline marketing touchpoints. These can include, email and newsletters, social media, mobile web, and more.
- Game landing page: A game landing page directs customers to your download app page. This step is important for collecting UTM and other URL parameters to attribute customers from the click/install to the original media sources or to your owned media sources.
The landing page is also useful because it provides links to the various platforms your game supports. For example, you can also have links to your Xbox, Microsoft store, and Steam page on your landing page. - App page: This is the URL to your Native PC app page that hosts your app for customers to download.
- Game install: The user installs the game, triggering attribution and the recording of in-app events and sessions.
Integration procedures
The following table lists the tasks required to integrate your PC app with AppsFlyer.
Note: Adding team members and setting up reports in Data Locker are not mandatory.
| Task | Actions | Who's involved |
|---|---|---|
| App setup | Marketer | |
| SDK integration with your app (via S2S or SDK) |
There are two methods of integration you can use: S2S and SDK. For the S2S method, integrate the AppsFlyer API into your app with commands to report the following events to AppsFlyer.
Note:
For the SDK method, there are three versions: native C++, Unreal, and Unity. Note: 既存のユーザーベースがあり、最初のセッションをインストールではなくセッションと見なす場合、開発者は |
アプリディベロッパー |
| Cross-platform landing page setup |
Recommended: A cross-platform landing page running the AppsFlyer Smart Script lets you perform web-to-app attribution. It's most recommended when your campaign promotes an app that's also available on other platforms, like Epic and Steam. ネイティブPCの場合、次のパラメーターが必要です:
次のパラメーターは必須ではありませんが、推奨です:
|
マーケター(開発者の支援が必要な場合があります) |
| リンクの設定 |
|
マーケティング担当者 |
| レポートの設定 / データの表示 | 詳細:ダッシュボードとレポートでのデータの可用性 | マーケター / データエンジニア |
Removing AppsFlyer data when uninstalling the app
To remove all AppsFlyer SDK data when uninstalling the app, please ask your developer to perform the steps specified here.
特性と制限
| Trait | 注記: |
|---|---|
| Retargeting(リターゲティング) | 現在サポートされていません |
| コストデータ | Send cost data via Cost Import using the upload file by email method. You can also send data via API for Google, Meta, or TikTok. |
See also