When you first implement Attribution Analytics as your mobile app attribution and analytics solution, make sure that the SDK is set up properly to log user interaction with your mobile app. Using test profiles, you can use a single device to:
- Log duplicate installs for testing
- Log duplicate events for testing
- Log multiple attributions using a single click
Advanced users: Depending on your Frequency Capping for Events settings for an event, setting up a test profile for your device enables Attribution Analytics to test the logging of additional events without enforcing this setting. For information about this setting, please visit Frequency Capping for Events.
Adding a Test Profile
Before you start testing your mobile app, first setup a test profile for your test mobile device because TUNE only allows one install per mobile app per unique device ever. By setting up a test profile, you can test for proper functionality with the same device.
NOTE: We have deprecated support for Windows devices. Contact Support with any questions related to this change.
To set up a test profile:
- In the navigation (on the left side), under Applications, expand Testing, and then click Test Profiles.
- On the Test Profiles page (on the right side), in the upper-right corner, click Create Test Profile.
- In the Create Test Profile dialog box, complete the following fields.
- Test Profile Name [REQUIRED]
- Enter a name for the test profile. If different individuals are testing, consider using their names.
- Test Profile Type [REQUIRED]
- Click the appropriate platform that your mobile app runs on: iOS, Android, Fire, or Other.
- Device Identifier(s) of Choice [REQUIRED]
- Depending on the platform selected, provide at least one identifier for your test device. You don’t need to create a test profile for each supported platform because you can simply provide device identifiers for both platforms simultaneously in one test profile. Installs associated with a test profile have the same tracking ID.
- Test Profile Name [REQUIRED]
After you add a Test Profile, TUNE starts to compare each click, install, and/or event request with the test profiles. If one of the identifiers from the Test Profile matches the identifiers in the request, then TUNE handles it according to the status specified for the Test Profile: Active – process all conversions; or Inactive – reject all conversions.
Including Test Data in Reporting
After you setup a test profile in Attribution Analytics and run a test (for example, perform a mobile app install on your test device), you must include test data in your reports (else you will not see the test install event because by default, Attribution Analytics excludes test data from reporting). To include test data in your reports:
- In the navigation, under the Reporting section, click the desired type of report (for example, Actuals, Cohort, Retention, or Logs).
- On the report page, next to the date time in the upper-left corner, click Edit.
- In the parameters and filters panel, scroll down to the Filter section at the bottom, remove the Test Data: Exclude filter, and then click Apply as shown in the following screenshot.
Things to Keep in Mind
1. Android Test Profile – You must specify a device identifier (such as Android ID, Device ID, or Google Ad ID) to create the test profile. When creating your measurement URLs, append the identifier used to create the test profile to the measurement URL. We recommend using the Google Advertising ID (AID) because eventually Android ID and Device ID will likely be deprecated. For example:
For more information about the Google AID, please visit Google’s Advertising Identifier.
2. iOS Test Profile – You must specify either the iOS Identifier for Advertisers (IFA) or Identifier for Vendors (IFV) to create the test profile. If you use IFA, then your app needs to explicitly set the IFA in the iOS SDK. When creating your measurement URLs, append the “ios_ifa” used to create the test profile to the measurement URL. For example:
Note: While you can use IFA for attribution but not IFV, you can use IFV with a test profile because the IFV value remains the same from test to test, and always collected and included with each request to log events (such as an install or in-app event). For more information about IFA and IFV, please visit IFA vs IFV when to use which one and why. If your SDK implementation is not setup to collect IFA, then use IFV or Device IP to setup a test profile.
3. All Platforms Test Profile – To setup a test profile that works on multiple mobile platforms, you must specify either the TUNE ID (generated by the SDK), User ID (specified by advertiser), or Device IP. If your SDK implementation includes your own User ID with each logged event, then you can include this value and it works as a device identifier (such as iOS IFA, or Google AID).
Our SDKs also generate an ID known as the TUNE ID, which you use for logging post-install events on the server side. For information about loading the Event Request URL (server-side or client-side), please visit measuring events server-side after the install.
If you want to set all devices for an office into testing mode, then create a Test Profile and enter the IP address for your office. TUNE treats all requests from the IP address as though they belong to the same Test Profile.
To lookup the IP address for your office:
- Connect to your office WiFi network.
- Open a browser window and visit http://www.whatismyip.com/.
- Create a test profile with ONLY the IP address that appears in your browser.
4. Test Profile Statuses – You can set one of two status levels for Test Profiles:
- Inactive – Reject all conversions from these devices.
- Active – Process all conversions and don’t check for duplicate installs/events.
Note: TUNE logs update events (from devices with an active Test Profile) as installs.
5. Global Test Profiles – If you’re a publishing partner or ad network who works with multiple TUNE clients, then you can setup global test profiles that work for all clients using the alpha publisher interface.
Test profiles in the TUNE Partner Center are all setup as global test profiles. Advertising partners using the alpha publisher interface only need to create one test profile for their device and it applies to all advertisers they work with.
If you don’t have access to the TUNE Partner Center, then please send an email to firstname.lastname@example.org and we can set you up with access. For more information about the TUNE Partner Center, please visit Getting Started with the TUNE Partner Center .