Mobile-Specific Parameters for FTP or Email Conversion Reporting

Take the PXA course

Conversions that occur on your mobile apps 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 apps in impact.com that you'll need when creating your CSV file, and the mobile-specific parameters you can include in that file.

The primary 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.

Find your System App ID & Event Code values

1. From the top navigation bar, select [User profile] → Settings.

2. In the right column, under Tracking, select Mobile Apps.

   • Take note of the values under the System App ID column for your mobile apps. These are submitted under ActionTrackerId in your CSV file.

   
3. Hover over the app, then select [More] → Manage Events.

   • Take note of the values under the Event Code column. These are submitted under EventCode in your CSV file.

Mobile-specific parameters

Note: Parameters listed below are in addition to the standard parameters for submitting conversions (e.g., ClickId, CustomerId). 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.

Parameter reference table

Parameter	Required/Optional	Description
EventCode	Required when submitting mobile conversions	Custom identifier for the event that occurred in your mobile app that you want to report (e.g., INSTALL).
GoogleAid	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.
AppleIfa	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.
AppleIfv	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.
AppPackage	Optional	Package name for the mobile app the user installed.
AppVer	Optional	Version of the mobile app. Only for mobile conversions.
AppInstallRef	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 clickid={clickidvalue}.
DeviceMfr	Optional	Primarily used for mobile in-app conversions, this is the manufacturer of the device the user converted on.
DeviceModel	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.
DeviceCarrier	Optional	Carrier of the mobile device.
DeviceOs	Optional	OS of the mobile device.
DeviceOsVer	Optional	Optional.

Sample CSV

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