Tag your app for app engagement campaigns
In order to run a "Display Network only - Mobile app engagement campaign" for iOS apps, you need to tag your app so Google Ads can make sure to show your ads to your current users. This tag sends information to Google Ads and allows you to create more complex remarketing lists, and count specific in-app actions as conversions.
Before you begin
If you're promoting an Android app, and you just want to show ads to people using your app in general, or people using a specific version, you’re ready to create your "Mobile app engagement" campaign.
If you're promoting an iOS app, or you'd like to use more sophisticated targeting methods for Android, follow the steps below.
How to set up remarketing for iOS app engagement campaigns
For mobile apps, you can use a process called tagging to notify Google Ads when someone does a specific action in your app. Notifications can come either from code integrated directly into your app, or from an app analytics tool where you may already be tracking these actions. The following steps help you set up your app to track and record these actions.
Step 1: Define specific in-app events that you’d like to track as conversions
One important reason to tag specific actions in your app is for conversion tracking, which lets you see how many actions were driven by clicks on your ads. Before tagging your app, you’ll need to create labels for specific in-app actions that you care about, called conversion events. Here’s how:
- Click Tools, and select “Conversions” from the drop-down menu.
- Define a conversion event for specific actions people might take in your app.
Detailed instructions on setting up conversion tracking for your mobile app.
Note
The same tagging process that lets Google Ads track the conversions from your ads will also allow you to generate remarketing lists to reach users who have done specific things in your app.
Step 2: Make sure your app is tagged so that Google Ads can show ads to the right audience
You or your app developer will need to make sure that your tagging is set up, or that Google Ads can receive information about how people use your app in another way. Currently, there are two ways to do this:
- Option 1. Set up a server-to-server feed from an app analytics or tracking package.
- Option 2. Add a new conversion tracking and remarketing code tag to your app.
Keep in mind, your targeting options will differ based on how you complete the tagging process. Depending on how your app sends information to Google Ads, you may not be able to use certain remarketing lists.
Remarketing lists available by tagging method
| Tagging method | Operating system | Remarketing lists available |
|---|---|---|
| No new tagging required | ||
| Link to Google Play | Android only (Google Play) |
The above options use data imported from Google Play |
| Use your existing data from Google Ads iOS download tracking (code tag or server-to-server) | iOS only |
|
| Tagging required | ||
| Add the newest tag version to your app and re-release your app (Google Ads conversions + remarketing SDK version 3.2.0 for iOS and version 2 for Android) | iOS and Android |
|
| Set up a server-to-server feed from your app analytics or tracking package into Google Ads | iOS and Android |
|
Important
You’ll need to complete Option 1 or 2 above in order to run app engagement campaigns on the Display Network. See more detailed tagging instructions for app developers.
Step 3: Check to make sure your tags are working
You can check to make sure that your app has been tagged successfully using the tag validation tool in the Shared Library. It shows which apps are already sending remarketing data to Google Ads, and which data they're sending. Here’s how to find it:
- Go to the Shared Library, and click Audiences.
- In the upper corner there is a box labeled “Remarketing tag”.
- Click View tag details to see the data your tag is collecting.
- If your tag doesn’t appear in the validation tool, or remarketing lists are empty, then your tag isn’t working yet, and your campaign won't run. If that's the case, try going over Step 2 with your developer.
* Nguồn: Google