Windows Quick Start

Current Windows SDK Version 3.6.0

The TUNE SDK for Microsoft Windows provides application session and event logging functionality. This SDK is available in the form of a single .DLL file that you simply include in your project. Our SDK is compatible with all Windows-powered devices running Windows Phone 8, Windows 8.1 or Windows 10.

To begin logging sessions, first integrate the Windows SDK with your mobile app. After you initiate the “MeasureSession” method, you can log in-app events (such as purchases, game levels, and any other user engagement).

Follow this Quick Start to get the TUNE SDK up and running in no time.

Supported TMC Solutions

The TUNE SDK for Windows supports the following TUNE Marketing Console solutions:

  • Attribution Analytics
  • App Store Analytics

Downloading the SDK

The TUNE SDK for Windows is 38 KB in size and available via NuGet. Before you implement the TUNE SDK, make sure to add your app to the Attribution Analytics platform.

The TUNE SDK is also available as an open-source framework with libraries for session and event measurement. To access the open source SDK, please visit GitHub.


To implement the SDK:

  1. Add the MobileAppTracking NuGet package to your project.
  2. If your app is targeted for WP8, you should instead download the SDK from the MobileAppTracking site and add the WP8 DLL as a reference in your project, along with Json.NET and Bouncy Castle PCL.
  3. Declare a MobileAppTracker object and instantiate it in your app. Where you instantiate a new class is a decision that is unique to your application and code design. Generally, you perform this step during creation of the first page of your app.
    using MobileAppTracking;
    private MobileAppTracker mobileAppTracker;
    public MainPage()
        mobileAppTracker = MobileAppTracker.InitializeValues("your_advertiser_id", "your_conversion_key");
  4. Confirm that the package name for your app is the same as the package name specified in MAT. Note that for the store, the package name for your app is set to a new unique value upon publishing, so after you publish, change the package name on the site to match. For testing purposes, set the same “test” value in both the app and MAT. On Windows, MAT uses the following values for a package name: Windows Phone 8: WMAppManifest.xml -> Product ID.

Windows Universal: Package.appxmanifest -> Package name


For Windows Phone 8, enable the ID_CAP_IDENTITY_DEVICE capability in your WMAppManifest.xml file.



Things to Keep in Mind

The “your_advertiser_ID” and the “your_conversion_key” values correlate with the Advertiser ID and Conversion Key that MAT provides when you create your Mobile App in MAT. For information about the advertiser ID and conversion key, please visit Finding Advertiser ID and Conversion Key.

If your app already has a pre-existing user base (people who have already installed your app), TUNE has several options to flag these users as Pre-Existing Users to prevent attributing these users to a marketing partner. For information about migrating existing users, please visit handle existing users prior to SDK implementation.


Testing & Troubleshooting

To test the MAT SDK implementation in your mobile app, you can do so straight from the MAT platform itself rather than creating a test environment. Please visit Testing Your Mobile App.


Measuring Events

After you implement the MAT SDK in your mobile app and start logging sessions, you can move on to logging a wide variety of in-app events such as registrations and in-app purchases.

By logging and analyzing in-app events, you can more efficiently optimize both the functionality of your app and your advertising strategies. Bottom line? Understanding how your users interact with your mobile app directly impacts your ability to build effective and profitable advertising campaigns by enabling you to compare retention, engagement, and lifetime value (LTV) to your costs.

Or to build your own custom event, please visit Event Builder.

In-App Events