This is the Windows SDK of
Latest commit 6daa7e6 Dec 4, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
Adjust new version 4.17.0 Dec 4, 2018
IntegrationTesting new version 4.17.0 Dec 4, 2018
WindowsPcl new version 4.17.0 Dec 4, 2018
WindowsPhone81 new version 4.17.0 Dec 4, 2018
WindowsStore new version 4.17.0 Dec 4, 2018
WindowsUAP10 new version 4.17.0 Dec 4, 2018
WindowsUap new version 4.17.0 Dec 4, 2018
doc new version 4.17.0 Dec 4, 2018
.gitignore git ignore visual studio stuff Sep 7, 2017
CHANGELOG.md CHANGELOG update Dec 4, 2018
MIT-LICENSE Version 4.13.0 Apr 27, 2018
README.md update README.md Sep 4, 2018
VERSION new version 4.17.0 Dec 4, 2018

README.md

Summary

This is the Windows SDK of adjust™. You can read more about adjust™ at adjust.com.

Table of contents

Example app

There are different example apps inside the Adjust directory:

  1. AdjustUAP10Example for Universal Windows Apps,
  2. AdjustWP81Example for Windows Phone 8.1,
  3. AdjustWSExample for Windows Store.

You can use these example projects to see how the Adjust SDK can be integrated into your app.

Basic integration

These are the basic steps required to integrate the Adjust SDK into your Windows Phone or Windows Store project. We are going to assume that you use Visual Studio 2015 or later, with the latest NuGet package manager installed. A previous version that supports Windows Phone 8.1 or Windows 8 should also work. The screenshots show the integration process for a Windows Universal app, but the procedure is very similar for both Windows Store or Phone apps. Any differences with Windows Phone 8.1 or Windows Store apps will be noted throughout the walkthrough.

Install the Adjust package using NuGet Package Manager

Right click on the project in the Solution Explorer, then click on Manage NuGet Packages.... In the newly opened NuGet Package Manager window, click on the Browse tab, then enter adjust in the search box, and press <Enter>. The Adjust package should be the first search result. Click on it, and in the right pane, click on Install.

Another method to install Adjust package is using Package Manager Console. In the Visual Studio menu, select TOOLS → NuGet Package Manager → Package Manager Console (or, in older versions of Visual Studio TOOLS → Library Package Manager → Package Manager Console) to open the Package Manager Console view.

After the PM> prompt, enter the following line and press <Enter> to install the Adjust package:

Install-Package Adjust

It's also possible to install the Adjust package through the NuGet Package Manager for your Windows Phone or Windows Store project.

Integrate the Adjust SDK into your app

In Solution Explorer, open the App.xaml.cs file. Add the using AdjustSdk; statement at the top of the file.

Here is a snippet of the code that has to be added in the OnLaunched method of your app.

using AdjustSdk;

sealed partial class App : Application
{
    protected override void OnLaunched(LaunchActivatedEventArgs e)
    {
        string appToken = "{YourAppToken}";
        string environment = AdjustConfig.EnvironmentSandbox;
        var config = new AdjustConfig(appToken, environment);
        Adjust.ApplicationLaunching(config);
        // ...
    }
}

Update Adjust settings

App Token & Environment

Replace the {YourAppToken} placeholder with your app token, which you can find in your dashboard.

Depending on whether or not you are building your app for testing or for production, you will need to set the environment parameter with one of these values:

string environment = AdjustConfig.EnvironmentSandbox;
string environment = AdjustConfig.EnvironmentProduction;

Important: This value should be set to AdjustConfig.EnvironmentSandbox if and only if you or someone else is testing your app. Make sure to set the environment to AdjustConfig.EnvironmentProduction before you publish your app. Set it back to AdjustConfig.EnvironmentSandbox if you start developing and testing it again.

We use this environment to distinguish between real traffic and test traffic from test devices. It is imperative that you keep this value meaningful at all times, especially if you are tracking revenue.

Adjust Logging

To see the compiled logs from our library in released mode, it is necessary to redirect the log output to your app while it's being tested in debug mode.

To do this, use the AdjustConfig constructor with 4 parameters, where the 3rd parameter is the delegate method which handles the logging, and the 4th parameter is the LogLevel:

// ....
protected override void OnLaunched(LaunchActivatedEventArgs e)
{
    string appToken = "hmqwpvspxnuo";
    string environment = AdjustConfig.EnvironmentSandbox;
    var config = new AdjustConfig(appToken, environment,
        msg => System.Diagnostics.Debug.WriteLine(msg), LogLevel.Verbose);
    // ...
}
// ....

You can increase or decrease the amount of logs you see in tests by setting the 4th argument of the AdjustConfig constructor, logLevel, with one of the following values:

logLevel: LogLevel.Verbose  // enable all logging
logLevel: LogLevel.Debug    // enable more logging
logLevel: LogLevel.Info     // the default
logLevel: LogLevel.Warn     // disable info logging
logLevel: LogLevel.Error    // disable warnings as well
logLevel: LogLevel.Assert   // disable errors as well
logLevel: LogLevel.Suppress // disable all logs

Build and debug your app

From the menu, select DEBUG → Start Debugging. After the app launches, you should see the Adjust debug logs in the Output view. Every Adjust-specific log starts with the [Adjust] tag, like in the picture below:

Additional features

Once you have integrated the Adjust SDK into your project, you can take advantage of the following features.

Event tracking

You can use Adjust to track any event in your app. Suppose you want to track every tap of a button. You would have to create a new event token in your dashboard. Let's say that event token is abc123. In your button's Button_Click method, you can add the following lines to track the click:

var adjustEvent = new AdjustEvent("abc123");
Adjust.TrackEvent(adjustEvent);

Revenue tracking

If your users generate revenue by tapping on advertisements or making in-app purchases, then you can track that revenue through events. Let's say a tap is worth €0.01. You can then track the revenue event like this:

var adjustEvent = new AdjustEvent("abc123");
adjustEvent.SetRevenue(0.01, "EUR");
Adjust.TrackEvent(adjustEvent);

This can always be combined with callback parameters.

When you set a currency token, Adjust will automatically convert the incoming revenue into the reporting revenue of your choice. Read more about currency conversion here.

You can read more about revenue and event tracking in the event tracking guide.

The event instance can be used to further configure before you begin tracking.

Revenue deduplication

You can also add an optional purchase ID to avoid tracking duplicate revenues. The last ten purchase IDs are remembered, and revenue events with duplicate purchase IDs are skipped. This is especially useful for in-app purchase tracking. You can see an example below.

If you want to track in-app purchases, please make sure to call TrackEvent only if the purchase is finished and item is purchased. That way you can avoid tracking revenue that is not actually being generated.

AdjustEvent event = new AdjustEvent("abc123");

event.SetRevenue(0.01, "EUR");
event.PurchaseId = "{PurchaseId}";

Adjust.trackEvent(event);

Callback parameters

You can register a callback URL for the events in your dashboard. We will send a GET request to this URL whenever an event is tracked. You can also add callback parameters to the event by calling the AddCallbackParameter on the event instance before tracking it. We will then append these parameters to your specified callback URL.

For example, suppose you have registered the URL http://www.adjust.com/callback. Then, you would track an event like this:

var adjustEvent = new AdjustEvent("abc123");

adjustEvent.AddCallbackParameter("key", "value");
adjustEvent.AddCallbackParameter("foo", "bar");

Adjust.TrackEvent(adjustEvent);

In that case we would track the event and send a request to:

http://www.adjust.com/callback?key=value&foo=bar

It should be mentioned that we support a variety of placeholders, such as {win_adid}, that can be used as parameter values. In the resulting callback, this placeholder would be replaced with the Windows advertising ID of the current device. Also note that we don't store any of your custom parameters but only append them to your callbacks. If you haven't registered a callback for an event, these parameters won't even be read.

You can read more about using URL callbacks, including a full list of available values, in our callbacks guide.

Partner parameters

You can also add parameters to be transmitted to network partners that have been activated in your Adjust dashboard.

This works similarly to the callback parameters mentioned above, but can be added by calling the addPartnerParameter method on your AdjustEvent instance.

var adjustEvent = new AdjustEvent("abc123");

adjustEvent.AddPartnerParameter("key", "value");
adjustEvent.AddPartnerParameter("foo", "bar");

Adjust.TrackEvent(adjustEvent);

You can read more about special partners and these integrations in our guide to special partners.

Callback identifier

You can also add custom string identifier to each event you want to track. This identifier will later be reported in event success and/or event failure callbacks to enable you to keep track on which event was successfully tracked or not. You can set this identifier using the CallbackId property on your AdjustEvent instance:

var adjustEvent = new AdjustEvent("abc123");

adjustEvent.CallbackId = "Your-Custom-Id";

Adjust.TrackEvent(adjustEvent);

Set up session parameters

Some parameters are saved to be sent in every event and session of the Adjust SDK. Once you have added any of these parameters, you don't need to add them every time, since they will be saved locally. If you add the same parameter twice, there will be no effect.

These session parameters can be called before the Adjust SDK is launched to make sure they are sent even on install. If you need to send them with an install but can only obtain the needed values after launch, it's possible to delay the first launch of the Adjust SDK to allow for this behavior.

Session callback parameters

The same callback parameters that are registered for events can be also saved to be sent in every event or session of the Adjust SDK.

The session callback parameters have a similar interface to the event callback parameters. Except, instead of adding the key and its value to an event, they are added through a call to Adjust.AddSessionCallbackParameter(string key, string value):

Adjust.AddSessionCallbackParameter("foo", "bar");

The session callback parameters will be merged with the callback parameters added to an event. The callback parameters added to an event have precedence over the session callback parameters. Meaning that, when adding a callback parameter to an event with the same key to one added from the session, the value that prevails is the callback parameter added to the event.

It's possible to remove a specific session callback parameter by passing the desired key to the Adjust.RemoveSessionCallbackParameter(string key) method.

Adjust.RemoveSessionCallbackParameter("foo");

If you wish to remove all keys and their corresponding values from the session callback parameters, you can reset them with the Adjust.ResetSessionCallbackParameters() method.

Adjust.ResetSessionCallbackParameters();

Session partner parameters

In the same way that there are session callback parameters sent in every event or session of the Adjust SDK, there are also session partner parameters.

These will be transmitted to network partners for the integrations that have been activated in your Adjust dashboard.

Session partner parameters have a similar interface to event partner parameters. Except, instead of adding the key and its value to an event, they are added through a call to Adjust.AddSessionPartnerParameter(string key, string value):

Adjust.AddSessionPartnerParameter("foo", "bar");

The session partner parameters will be merged with the partner parameters added to an event. The partner parameters added to an event have precedence over the session partner parameters. Meaning that, when adding a partner parameter to an event with the same key to one added from the session, the value that prevails is the partner parameter added to the event.

It's possible to remove a specific session partner parameter by passing the desired key to the Adjust.RemoveSessionPartnerParameter(string key) method.

Adjust.RemoveSessionPartnerParameter("foo");

If you wish to remove all keys and their corresponding values from the session partner parameters, you can reset them with the Adjust.ResetSessionPartnerParameters() method.

Adjust.RresetSessionPartnerParameters();

Delay start

Delaying the start of the Adjust SDK allows your app some time to obtain session parameters, such as unique identifiers, to be sent on install.

Set the initial delay time in seconds with the DelayStart property in the AdjustConfig instance:

adjustConfig.DelayStart = TimeSpan.FromSeconds(5.5);

In this case, the Adjust SDK will not send the initial install session or any events created for 5.5 seconds. After this time has expired--or if you call Adjust.SendFirstPackages() in the meanwhile--every session parameter will be added to the delayed install session and events, and the Adjust SDK will resume as usual.

The maximum delay start time of the Adjust SDK is 10 seconds.

Attribution callback

You can register a delegate function to be notified of tracker attribution changes. Due to the different sources considered for attribution, this information cannot be provided synchronously. The simplest way is to create a single anonymous delegate function.

Please make sure to consider our applicable attribution data policies.

With the AdjustConfig instance, before starting the SDK, set the AttributionChanged delegate with the Action<AdjustAttribution> signature.

var config = new AdjustConfig(appToken, environment);

config.AttributionChanged = (attribution) => 
    System.Diagnostics.Debug.WriteLine("attribution: " + attribution);
    
Adjust.ApplicationLaunching(config);

Alternatively, you can implement the AttributionChanged delegate interface in your Application class and set it as a delegate:

var config = new AdjustConfig(appToken, environment);
config.AttributionChanged = AdjustAttributionChanged;
Adjust.ApplicationLaunching(config);

private void AdjustAttributionChanged(AdjustAttribution attribution) 
{
    //...
}

The delegate function will be called when the SDK receives the final install attribution information and also each time an attribution changes. Within the listener function you have access to the attribution parameter. Here is a quick summary of its properties:

  • string TrackerToken the tracker token of the current attribution.
  • string TrackerName the tracker name of the current attribution.
  • string Network the network grouping level of the current attribution.
  • string Campaign the campaign grouping level of the current attribution.
  • string Adgroup the ad group grouping level of the current attribution.
  • string Creative the creative grouping level of the current attribution.
  • string ClickLabel the click label of the current attribution.
  • string Adid the Adjust device identifier.

If any value is unavailable, it will default to null.

Session and event callbacks

You can register a listener to be notified when events or sessions are tracked. There are four listeners: one for tracking successful events, one for tracking failed events, one for tracking successful sessions and one for tracking failed sessions. You can add any number of listeners after creating the AdjustConfig object:

var config = new AdjustConfig(appToken, environment,
    msg => System.Diagnostics.Debug.WriteLine(msg), LogLevel.Verbose);

// Set event success tracking delegate
config.EventTrackingSucceeded = adjustEventSuccess =>
{
    // ...
};

// Set event failure tracking delegate
config.EventTrackingFailed = adjustEventFailure =>
{
    // ...
};

// Set session success tracking delegate
config.SesssionTrackingSucceeded = adjustSessionSuccess =>
{
    // ...
};

// Set session failure tracking delegate
config.SesssionTrackingFailed = adjustSessionFailure =>
{
    // ...
};

Adjust.ApplicationLaunching(config);

The delegate function will be called after the SDK tries to send a package to the server. Within the delegate function you have access to a response data object specifically for the event. Here is a quick summary of the successful session response data object fields:

  • string Message the message from the server or the error logged by the SDK.
  • string Timestamp timestamp from the server.
  • string Adid a unique device identifier provided by Adjust.
  • JSONObject JsonResponse the JSON object with the reponse from the server.

Both event response data objects contain:

  • string EventToken the event token, if the package tracked was an event.
  • string CallbackId the custom defined callback ID set on event object.

If any value is unavailable, it will default to null.

And both event and session failed objects also contain:

  • bool WillRetry indicates that will be an attempt to resend the package at a later time.

Disable tracking

You can disable the Adjust SDK from tracking any activities of the current device by calling setEnabled with the parameter set to false. This setting is remembered between sessions.

Adjust.SetEnabled(false);

You can check if the Adjust SDK is currently enabled by calling the isEnabled function. It is always possible to activate the Adjust SDK by invoking SetEnabled with the enabled parameter set to true.

Offline mode

You can put the Adjust SDK in offline mode to suspend transmission to our servers, while retaining tracked data to be sent later. While in offline mode, all information is saved in a file, so be careful not to trigger too many events while in offline mode.

You can activate offline mode by calling SetOfflineMode with the parameter true.

Adjust.SetOfflineMode(true);

Conversely, you can deactivate offline mode by calling SetOfflineMode with false. When the Adjust SDK is put back in online mode, all saved information is sent to our servers with the correct time information.

Unlike disabling tracking, this setting is not remembered between sessions. This means that the SDK is in online mode whenever it is started, even if the app was terminated in offline mode.

Event buffering

If your app makes heavy use of event tracking, you might want to delay some HTTP requests in order to send them in one batch every minute. You can enable event buffering with your AdjustConfig instance:

var config = new AdjustConfig(appToken, environment,
    msg => System.Diagnostics.Debug.WriteLine(msg), LogLevel.Verbose);

config.EventBufferingEnabled = true;

Adjust.ApplicationLaunching(config);

GDPR right to be forgotten

In accordance with article 17 of the EU's General Data Protection Regulation (GDPR), you can notify Adjust when a user has exercised their right to be forgotten. Calling the following method will instruct the Adjust SDK to communicate the user's choice to be forgotten to the Adjust backend:

Adjust.GdprForgetMe();

Upon receiving this information, Adjust will erase the user's data and the Adjust SDK will stop tracking the user. No requests from this device will be sent to Adjust in the future.

SDK signature

An account manager must activate the Adjust SDK signature. Contact Adjust support (support@adjust.com) if you are interested in using this feature.

If the SDK signature has already been enabled on your account and you have access to App Secrets in your Adjust Dashboard, please use the method below to integrate the SDK signature into your app.

An App Secret is set by calling setAppSecret on your AdjustConfig instance:

var config = new AdjustConfig(appToken, environment,
   msg => System.Diagnostics.Debug.WriteLine(msg), LogLevel.Verbose);

config.SetAppSecret(secretId, info1, info2, info3, info4);

Adjust.ApplicationLaunching(config);

Background tracking

The default behavior of the Adjust SDK is to pause sending HTTP requests while the app is in the background. You can change this in your AdjustConfig instance:

var config = new AdjustConfig(appToken, environment,
    msg => System.Diagnostics.Debug.WriteLine(msg), LogLevel.Verbose);

config.SendInBackground = true;

Adjust.ApplicationLaunching(config);

Device IDs

The Adjust SDK offers you possibility to obtain some device identifiers.

Windows advertising identifier

This retrieves a unique ID used to provide more relevant advertising on the Windows platform. When a user turns the advertising ID feature off on their device, this will be an empty string.

Get the Windows advertising ID by calling the GetWindowsAdId method:

var windowsAdid = Adjust.GetWindowsAdId();

Adjust device identifier

For each device with your app installed on it, the Adjust backend generates a unique Adjust device identifier (adid). In order to obtain this identifier, you can make a call to following method on the Adjust instance:

string adid = Adjust.GetAdid();

Note: You can only make this call in the Adjust SDK v4.12.0 and above.

Note: Information about the adid is available after an app installation has been tracked by the Adjust backend. From that moment on, the Adjust SDK has information about the device adid and you can access it with this method. So, it is not possible to access the adid value before the SDK has been initialized and installation of your app has been tracked successfully.

User attribution

This callback is triggered as described in the attribution callback section. It provides information about new attributions whenever there is a change. In case you want to access information about your user's current attribution whenever you need it, you can make a call to the following method of the Adjust instance:

AdjustAttribution attribution = Adjust.GetAttribution();

Note: You can only make this call in the Adjust SDK v4.12.0 and above.

Note: Information about a current attribution is available after app installation has been tracked by the Adjust backend and an attribution callback has been triggered. From that moment on, the Adjust SDK has information about your user's attribution status and you can access it with this method. So, it is not possible to access a user's attribution value before the SDK has been initialized and an attribution callback has been triggered.

Push token

To send us the push notification token, add the following call to Adjust once you have obtained your token or whenever its value is changed:

Adjust.SetPushToken(pushNotificationsToken);

Pre-installed trackers

If you want to use the Adjust SDK to recognize users whose devices came with your app preinstalled, follow these steps.

  1. Create a new tracker in your dashboard.

  2. Set the DefaultTracker property of your AdjustConfig:

        var config = new AdjustConfig(appToken, environment,
            msg => System.Diagnostics.Debug.WriteLine(msg), LogLevel.Verbose);
        config.DefaultTracker = "{TrackerToken}";
        Adjust.ApplicationLaunching(config);

Replace {TrackerToken} with the tracker token you created in step 2. Please note that the dashboard displays a tracker URL (including http://app.adjust.com/). In your source code, you should specify only the six-character token and not the entire URL.

  1. Build and run your app. You should see a line like the following in Debug Output:

    Default tracker: 'abc123'
    

Deep linking

You can set up the Adjust SDK to handle any deep links (also known as URI activation in Universal apps) used to open your app. We will only read Adjust-specific parameters.

If you are using an Adjust tracker URL with an option to deep link into your app from the URL, there is the possibility to get information about the deep link URL and its content.

Hitting the URL can happen when the user has your app already installed (standard deep linking scenario) or if they don't have the app on their device (deferred deep linking scenario). In the standard deep linking scenario, the Windows platform natively offers the possibility for you to get the information about the deep link's content. The deferred deep linking scenario is something that the Windows platform doesn't support out of the box and, in this case, the Adjust SDK will offer you the means to get the information about the deep link content.

Standard deep linking scenario

If a user has your app installed and you want it to launch after hitting an Adjust tracker URL with the deep_link parameter in it, you need to enable deep linking in your app. This is done by choosing a desired unique scheme name and assigning it to the specific handler method in your app, which runs once the app opens after the user has clicked on the link. This is set in the Package.appxmanifest, and here's how you indicate that your app handles your unique URI scheme name:

  1. In the Solution Explorer, double click package.appxmanifest to open the manifest designer
  2. Select the Declarations tab, and in the Available Declarations drop down, select Protocol and then click Add.
  3. Choose a name for the URI scheme (the name must be in all lowercase letters),
  4. Press Ctrl+S to save the changes to package.appxmanifest.

Here, we added a protocol with the assigned unique scheme name of myapp;

Next thing you have to set up is the OnActivated event handler, which handles the activated deep link event.

In your App.xaml.cs file, add the following:

// ...
protected override void OnActivated(IActivatedEventArgs args)
{
    if (args.Kind == ActivationKind.Protocol)
    {
        var eventArgs = args as ProtocolActivatedEventArgs;
        if (eventArgs != null)
        {
            // to get deep link URI:
            Uri deeplink = eventArgs.Uri;
            
            // ...            
        }
    }
    base.OnActivated(args);
}
// ...

You can find more information in the official Microsoft documentation: URI activation handling

With this now set, you need to use the assigned scheme name in the Adjust tracker URL's deep_link parameter if you want your app to launch once the tracker URL is clicked. A tracker URL without any information added to the deep link can be built to look something like this:

https://app.adjust.com/abc123?deep_link=adjustExample%3A%2F%2F

Please bear in mind that the deep_link parameter value in the URL must be URL encoded.

With the app set as described above, after clicking this tracker URL. your app will launch along with OnActivated event handler, inside which you will automatically be provided with the information about the deep_link parameter content. Once this content is delivered to you, it will not be encoded, although it was encoded in the URL.

Deferred deep linking scenario

The deferred deep linking scenario occurs when a user clicks on the Adjust tracker URL with the deep_link parameter in it but does not have the app installed on the device at the time of click. After that, the user will get redirected to the Microsoft Store to download and install your app. After opening it for the first time, the content of the deep_link parameter will be delivered to the app.

In order to get information about the deep_link parameter content in a deferred deep linking scenario, you should set a delegate method (DeeplinkResponse) on the AdjustConfig object. This will get triggered once the Adjust SDK gets the information about the deep link content from the backend.

// ...
var config = new AdjustConfig(appToken, environment,
    msg => System.Diagnostics.Debug.WriteLine(msg), LogLevel.Verbose);

config.DeeplinkResponse = deepLinkUri =>
{
    if (ShouldAdjustSdkLaunchTheDeeplink(deepLinkUri))
    {
        return true;
    }
    else
    {
        return false;    
    }
};

Adjust.ApplicationLaunching(config);
// ...

Once the Adjust SDK receives the information about the deep link content from the backend, it will deliver it to you through this delegate and expect the bool return value from you. This return value represents your decision on whether the Adjust SDK should launch the OnActivated event handler to which you have assigned the scheme name from the deep link (like in the Standard deep linking scenario) or not.

If you return true, we will launch the event handler and the exact same scenario which is described in the Standard deep linking scenario chapter will happen. If you do not want the SDK to launch the OnActivated event handler, you can return false from this delegate (DeeplinkResponse), and, based on the deep link content, decide on your own what to do next in your app.

Reattribution via deep links

Handling of deep links (URI activation on UAP) used to open your app is essential if you are planning to run retargeting or re-engagement campaigns with deep links. For more information on how to do that, please check our official docs.

If you are using this feature, in order for your users to be properly reattributed, you need to make one additional call to the Adjust SDK in your app.

Once you have received the deep link content information in your app, add a call to the Adjust.AppWillOpenUrl method. By making this call, the Adjust SDK will try to find if there is any new attribution information inside of the deep link, and, if there is any, it will be sent to the Adjust backend. If your user should be reattributed due to a click on an Adjust tracker URL with deep link content in it, you will see the attribution callback in your app being triggered with new attribution information for this user.

The call to Adjust.AppWillOpenUrl should be done in the OnActivated method of your app, like this:

using AdjustSdk;

public partial class App : Application
{
    protected override void OnActivated(IActivatedEventArgs args)
    {
        if (args.Kind == ActivationKind.Protocol)
        {
            var eventArgs = args as ProtocolActivatedEventArgs;

            if (eventArgs != null)
            {
                Adjust.AppWillOpenUrl(eventArgs.Uri);
            }
        }
        //...
    }
}

License

The Adjust SDK is licensed under the MIT License.

Copyright (c) 2012-2017 Adjust GmbH, http://www.adjust.com

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.