If you're planning to track events on your mobile apps, you'll need to configure them in the impact.com platform.
Create a mobile app tracker
You will need to have an app already created and available for installation in an app store before you can add a tracker for it on impact.com
From the left navigation menu, select [Menu] → Settings.
On the right, under Tracking, select Mobile Apps.
In the top right corner, select Add Mobile App.
On the Mobile App Settings screen, fill in the fields in each of the following sections:
Name: Add a name for your app.
Codes: Add custom codes to act as
EventTypeIds
for when your app sends in conversion data. (e.g., 123, 456, 789).Platform: Specify the app platform.
Other versions: If you've created mobile app trackers for other platforms, you can select them from the box next to Other versions.
Bundle ID (iOS) / Package Name (Android): Enter the unique identifier for your app (e.g.,
com.example.application
).SHA256 Fingerprints (Android): Enter the SHA256 fingerprints of your app's signing certificate (e.g.,
14:6D:E9:83:C5:73:06:50...
etc).Team ID (iOS): Enter the two-part string used to identify your app (e.g.
ABC123.com.example.application
).App ID (iOS): Enter the unique iTunes identifier for your app (e.g., the iTunes identifier for the iBooks app is
364709193
)Download URL: Enter the direct download URL where the app can be downloaded from the App Store (iOS) or Play Store (Android).
Select how you want to handle action reversals and modifications.
Process returns using the Pending Payouts screen: If you want to handle action modifications in the impact.com UI, select this option.
Automate returns processing (advanced): If you want to use an API, FTP, or SMTP to automate action modifications, select this option and choose one of the automated methods:
Use system web service (API): Use our API to submit conversion data directly to impact.com. You’ll need your account’s API Access credentials.
Upload file to system FTP server: Use our FTP server to submit conversion data in a CSV file.
Pull file from your own FTP server: Use your own FTP server and have impact.com pull your conversion data. We’ll need the following info:
Server URL — Select the correct protocol prefix and enter the server URL.
Username — Enter the username impact.com can use to access your FTP server.
Password — Enter the password for the FTP account impact.com can use.
Port — Enter the port to use when connecting to your FTP server.
Directory — Enter the directory where impact.com can find the file (e.g.,
/impact/returns
).
Email file to system SMTP server: impact.com will provide a unique email address to which you can send conversion data as a CSV attachment.
If you want to add advanced settings, select Show advanced settings.
If you want to add Order ID (OID) Duplication, toggle [Toggle on] Specify an OID duplication window, then add the duplication window.
If you want to add Client Costs, toggle [Toggle on] Add client costs, then select how you want to add incorporate client costs.
If you want to add Open-ended Locking, toggle [Toggle on] Lock actions by updating their status via web services or batch file uploads.
Select Save and Continue to move on to configuring payable events.
The Payable Events screen is where you can configure the app events for which you want to pay out.
App Installs: Installs are tracked and payable by default. (If you’re using a 3rd-party MMP, you’ll need to report app installs as an in-app event, as outlined in the option below.)
In-App Events: Configure the in-app events that you’ll pay out for:
Event Display Name — Input a descriptive event display name which will appear in your Template Terms.
Event Code — Input the case sensitive event code that impact.com will be receiving from your MMP.
Crediting Rule — Select either Install, which will credit the partner that drove the initial install to your app, or Last Click, which will credit the partner that drove the last referring click to your app prior to conversion.
Select Save.
There are a number of ways in which you can manage your existing mobile app trackers:
From the left navigation menu, select [Menu] → Settings.
On the right, under Tracking, select Mobile Apps.
Next to the tracker you want to edit, select [Menu] → View/Edit.
Make the changes you want to make.
Select Save.
From the left navigation menu, select [Menu] → Settings.
On the right, under Tracking, select Mobile Apps.
Next to the tracker you want to add disposition codes for, select [Menu] → manage Events.
In the top-right corner, select Add Event.
Next to In-App Events, select [Add Another Event].
Enter the Event Display Name. This is the name that will show up on contracts and template terms.
Enter the Event Code. This is the code that your app passes whenever the tracked event happens.
Select the Crediting Rule from the drop-down menu. You can either credit the event by an install or the last click.
Select Save.
From the left navigation menu, select [Menu] → Settings.
On the right, under Tracking, select Mobile Apps.
Next to the tracker you want to add disposition codes for, select [Menu] → Disposition Codes.
In the top-right corner, select Add Disposition Code.
Next to Disposition Code, select or enter the code you want to use.
If you want to use a common code, select it from the drop-down menu.
If you want to create your own code, enter the name next to Disposition Name.
Next to State Transition, select what you want the partner driving the action to see.
Next to Action Change, select what action, if any, will happen when this code is selected.
Select Save.
From the left navigation menu, select [Menu] → Settings.
On the right, under Tracking, select Mobile Apps.
Find the mobile tracker you want to delete, select [Menu] → Delete.
Read the warning message, then select I understand, continue.