Conversions that occur on your mobile app(s) can be submitted as a CSV file to impact.com via FTP or Email, similar to standard web conversions. This article shows you where to find identifiers for your mobile app(s) in impact.com that you'll need when creating your CSV file, and the mobile-specific parameters you can include in that file.
The primarily difference from standard web conversion reporting is retrieving the System App ID and Event Code values from the impact.com platform—these are needed when submitting conversions to be tracked by your mobile apps. The System App ID value is submitted as the ActionTrackerID value in your CSV file.
impact.com recommends submitting these mobile-specific parameters when available—they can help with more accurate attribution and expand the data available in reports.
From the left navigation menu, select
[Menu] → Settings.In the Tracking column, select Mobile Apps.
Take note of the value(s) under the System App ID column for your mobile app(s). These are submitted under
ActionTrackerIdin your CSV file.
Under the actions column, select
[Drop-down menu] → Manage Events. Take note of the value(s) under the Event Code column. These are submitted under EventCodein your CSV file.
Note
Parameters listed below are in addition to the standard parameters for submitting conversions (e.g., ClickId, CustomerId, etc.). Refer to Submit Conversion Data via FTP or Email to learn more about the process of creating a CSV file and submitting it to impact.com.
| Required when submitting mobile conversions | Custom identifier for the event that occurred in your mobile app that you want to report (e.g., |
| Required, unless another attribution source is provided | Google Advertising ID associated with the mobile device the customer converted on. Used for attribution purposes. Typically only available for Android in-app conversions. |
| Required, unless another attribution source is provided | Apple ID for Advertising (IDFA) associated with the mobile device the customer converted on. Used for attribution purposes. Typically only available for iOS in-app conversions. |
| Required, unless another attribution source is provided | Apple ID for Vendors (IDFV) associated with the mobile device the customer converted on. Used for attribution purposes. Typically only available for iOS in-app conversions. |
| Optional | Package name for the mobile app the user installed. |
| Optional | Version of the mobile app. Only for mobile conversions. |
| Optional | Only for Android conversions. Install referrer passed from the Google Play Store when the app is installed. Usually, the value passed from impact.com tracking links will be |
| Optional | Primarily used for mobile in-app conversions, this is the manufacturer of the device the user converted on. |
| Optional | Model of the device the user made the conversion on. If the conversion was done through the web, this value is automatically determined from the user agent passed. |
| Optional | Carrier of the mobile device. |
| Optional | OS of the mobile device. |
| Optional | Optional |
CampaignId,ActiontrackerID,EventCode,EventDate,OrderId,ClickId,Amount,Category,Sku,Quantity,AppleIfa,AppleIfv,AppPackage,AppVer,DeviceModel,DeviceOsVer 1000,8882,INSTALL,2038-01-19T03:14:07-00:00,T52324111211,QiiWXOVnrQ3SQHl24jQjyxBGUkmzfJ3i1VHrWM0,0,,,1,EA7583CD-A667-48BC-B806-42ECB2B48606,EA7583CD-A667-48BC-B806-42ECB2B48607,com.example.myapp,10.0.1,iPhone 12,14.4