The Conversion Tracking SDK allows you to measure the impact of app promotion campaigns.
- As an advertiser, you can tag the events you'd like to track in your app, and then work with Ad Manager to see how many of these conversions are being driven by direct sale campaigns.
- As a publisher, you can tag any event in your app to be tracked as a conversion. When users perform the tagged action after interacting with an ad, the event will be recorded and viewable in Ad Manager Conversion Reporting.
By using the SDK to tag user activity in your app (e.g., purchases or progress in a game), publishers can then use Ad Manager Audience Solutions to reach certain users with ads. This will allow you to focus on users who have completed those specific actions by displaying re-engagement ads in the future.
Track in-app conversions
The Application downloads (counter) activity types (one for iOS, one for Android) track conversions for the initial launch of a mobile application. In their apps, advertisers include a small snippet of code that pings Ad Manager upon the app's first launch. If a user has recently viewed and/or clicked one of that advertiser's ads in an Ad Manager publisher's app, Ad Manager will count that as an app download conversion.
You'll need to create separate activity groups and snippets to track iOS and Android conversions.
Important: This feature only works with in-app ads. Conversions are not counted if the ad is initially viewed on the web (desktop or mobile) and the application is subsequently downloaded. Here are examples of conversion snippets:
iOS (to be included in your application delegate's
application:didFinishLaunchingWithOptions:method);[DCTConversionReporter reportWithConversionID:@"<activity id>" value:nil /* or price of app if desired */ isRepeatable:NO];Android (to be included in your application's main activity):
DoubleClickConversionReporter.reportWithConversionId( this.getApplicationContext(), "<activity id>", null, null /* or price of app if desired */, false);
Track in-app audience segments
Users can be added to Ad Manager audience lists within an application in one of two ways: based on ad requests, or based on activities.
Audience membership changes based on ad requests are triggered at the time of the ad request, assuming that the Ad Manager segment is configured with a matching targeting rule. You don't need to take any action within your application to enable this behavior.
When you want to add a user to an audience segment on a screen where you're not showing ads (e.g., a shopping cart), you can report on an activity that can be used as a signal for populating the audience segment. This is the in-app equivalent to the web-based audience pixel tags. To properly trigger the segment membership through the activity, you will need to configure the activity with ad unit and custom targeting key/value pairs matching the targeting rule of the Ad Manager segment.
Here are examples of conversion snippets:
iOS (to be included in your application delegate's
application:didFinishLaunchingWithOptions:method);[DCTActivityReporter reportWithAdUnitID:@"DFPAudiencePixel" publisherProvidedID:@"<id>" customParameters:nil /* or key value pairs if desired */];Android (to be included in your application's main activity):
DoubleClickAudienceReporter.reportActivity( this.getApplicationContext(), "DFPAudiencePixel", /* key value pairs, if desired */);
Confirm your setup
When you go into your app and carry out the conversion event that you've defined, you should see messages similar to the following logged at the Info level:
I/GoogleConversionReporter( 1557): Pinging: [...]
I/GoogleConversionReporter( 1557): Ping responded with response code 200
The HTTP 200 response code indicates that the conversion was successfully reported to Google Ads.