Microsoft.BingAds.UETSdk.Win32 1.2.0

Prefix Reserved
dotnet add package Microsoft.BingAds.UETSdk.Win32 --version 1.2.0                
NuGet\Install-Package Microsoft.BingAds.UETSdk.Win32 -Version 1.2.0                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Microsoft.BingAds.UETSdk.Win32" Version="1.2.0">
  <PrivateAssets>all</PrivateAssets>
  <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets>
</PackageReference>                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Microsoft.BingAds.UETSdk.Win32 --version 1.2.0                
#r "nuget: Microsoft.BingAds.UETSdk.Win32, 1.2.0"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Microsoft.BingAds.UETSdk.Win32 as a Cake Addin
#addin nuget:?package=Microsoft.BingAds.UETSdk.Win32&version=1.2.0

// Install Microsoft.BingAds.UETSdk.Win32 as a Cake Tool
#tool nuget:?package=Microsoft.BingAds.UETSdk.Win32&version=1.2.0                

Microsoft.BingAds.UETSdk.Win32.lib

Overview

Welcome to the Bing Ads UET (Universal Event Tracking) SDK! This software development kit provides you with the necessary tools and libraries to implement UET tracking capabilities in your Win32 applications. UET enables you to track and measure user interactions and events, allowing you to gain valuable insights and optimize your application's performance.

Documentation

For detailed instructions and comprehensive documentation on the UET SDK, please refer to the official UET SDK documentation.

The documentation provides information on:

  • SDK initialization and configuration options.
  • Methods and APIs for event tracking.
  • Custom event creation.
  • Retrieving and analyzing event data.

Using the UET SDK

Initialize UET SDK at application level on app launch

First, we initialize the SDK with three arguments:

  1. registryKey A globally unique name for your app.
  2. productId Your Microsoft Store product ID.
  3. tagId Your UET tag ID.

The definition for this constructor is:

C++ Sample Code

UETSdk(const std::wstring &registryKey, const std::wstring &productId, long tagId);

For example, assume we have an app named ContosoDesktop with store ID 88888ASDF and UET tag ID 123456, then in app launch we would create the UET SDK instance like:

//include header file
#include <UETSdk.h>

// Defined elsewhere
using namespace Microsoft::BingAds::UETSdkWin32;

UETSdk* uetSdk = NULL;

// At app launch, create the UET SDK instance
uetSdk = new UETSdk(L"ContosoDesktop", L"88888ASDF", 123456);

Track event goals in your app

uetSdk->TrackGoal(L"click", L"Buy Coins", L"Other", 5, L"USD");

C# .Net Sample Code

using Microsoft.BingAds.UETSdk;
....
UETSdk sdk = new UETSdk("your_registry_key","your_product_ID", your_UET_tag_ID);

sdk.TrackGoal("click", "Buy Coins", "Other", 5, "USD");
...

Remove the registry when uninstalling

The UET SDK reads and writes to the registry at HKEY_CURRENT_USER\Software\{registryKey} to determine first app launch.

You must clean up the registry at HKEY_CURRENT_USER\Software\{registryKey} when uninstalling your application.

If the registry is not cleaned up, the SDK will not send the firstLaunch event when the app is reinstalled and opened.

Troubleshooting SDK

SDK logs all important events to EventViewer under Windows Logs -> Application.

Notes on registry
  • {registryKey} is the name of your application passed in when creating the UET SDK. For instance, if you set registryKey as ContosoDesktop, as in the example above, then the registry path is HKEY_CURRENT_USER\Software\ContosoDesktop.
  • HKEY_CURRENT_USER is for the user currently logged into Windows. By using this path the app does not need to be run as administrator to modify the registry.
Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
.NET Core netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.0 is compatible.  netstandard2.1 was computed. 
.NET Framework net46 is compatible.  net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
native native is compatible. 
Tizen tizen40 was computed.  tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.
  • .NETFramework 4.6

    • No dependencies.
  • .NETStandard 2.0

    • No dependencies.
  • native 0.0

    • No dependencies.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
1.2.0 947 6/25/2024
1.1.0 363 3/21/2024
1.0.4 384 11/9/2023