Notification

Get personalized optimization tips, understand your account health and set up completion on the improved "My AdMob page".

Smart segmentation

Segment your users with Google Analytics & Firebase

You can use Google Analytics & Firebase to help you identify and monetize app users who are unlikely to spend in your app. Offering customized experiences based on the type of user can help you maximize your revenue.

Instructions

To segment your users and customize their ad experience, you’ll need to use:

  • Google Analytics Audiences to create audiences based on user purchasing probability  
  • Firebase Remote Config parameters to customize the showing and frequencies of ads.

Step 1: Set up

  1. Ensure you’ve implemented the Google Analytics for Firebase SDK and the Remote Config SDK into your app.
  2. Record the following events in Google Analytics. Choose the event that corresponds with your app type (i.e. gaming, utilities, or e-commerce). These will be used to predict purchasing probability. 
    • In_app_purchase events (commonly used for gaming or utilities apps)
      • For Android apps, you’ll need to first link your Firebase app to Google Play. 
      • For iOS, in_app_purchase events are automatically logged. 
    • Purchase events (commonly used for e-commerce apps)
      • Use Google Analytics custom events to record ‘purchase’ events.
Learn more about the best practices for using predictive metrics.

Step 2: Create audiences 

There are two options to create audiences of  of users based on their likelihood to purchase:

  1. Use predictive metrics: Google Analytics offers a “Purchase probability” metric that predicts the probability that a user who was active in the last 28 days will make a purchase within the next 7 days. You can use this metric to customize the Analytics audience.

    For example, to create an audience of the bottom 20% predicted purchasers, or the 20% that are unlikely to spend, you can configure the metric to customize the user range from 0 to 20%.

    We recommend using this option when your app has more than 1,000 purchasers in the past 28 days.
  2. Use historical first party data: You can also target users who have been in the app for the past X days but haven’t made a purchase. 
    To determine the X-day period, we recommend looking at the average time it took your past purchasers to make a purchase.

Step 3: Implement Remote config

  1. Show IAPs to predicted purchasers and ads for predicted non-purchasers. Give users who are not likely to purchase the option to watch an ad instead of making an in-app purchase.
  2. Extend frequency caps. Let users who are unlikely to spend see more ads; ads will likely be the only viable monetization option.
  3. Diversify format mix. Let your app monetize users with other ad formats that are not typically in your formats mix once you identify them as predicted non-purchasers. 

Was this helpful?

How can we improve it?
true
Show your support to promote DEI in Gaming by turning intentions into action!

Check out the newly launched Diversity in Gaming website, where you can find video stories and written pledges from global gaming developers. This campaign centers on 3 pillars: diverse teams, diverse games and diverse audiences showing how diversity is not just good for gamers, but for business as well. Show your support by taking the pledge to promote DEI in Gaming and share it on social!

Learn More

Search
Clear search
Close search
Google apps
Main menu
7522852860949004736
true
Search Help Center
true
true
true
true
true
73175