In App campaigns, you’re able to optimise your targeting and bidding for specific campaign objectives like getting more app users or more in-app actions from your new users, and even a target return on your ad spend. This article describes the different optimisation and bidding options available, and how to set those bids based on your objectives.
Before you begin
If this is the first time you're using an App campaign, it's best to start by reading about App campaigns. When you're ready to create your campaign, you can follow the instructions in Create an App campaign.
How it works
When you create your App campaign, you can choose to optimise your campaign based on which type of user is most valuable to you. Before you can optimise for in-app actions, you'll need to set up those actions as conversion events within Google Ads, or using Firebase. Learn more about mobile app conversion tracking.
The simplest way to track all of your app conversions is to use Google Analytics for Firebase for your app reporting. After you've linked Firebase and Google Ads, you'll be able to bid for in-app events that you've set up as conversions. Learn more about tracking mobile app conversions with Firebase.
Bidding strategies for App campaigns
Let’s take a look at how you can plan your campaign strategy around specific bidding types.
All bidding strategies for App campaigns are 'Target' strategies which seek to deliver the selected performance over the period of your in-app event’s conversion window. Auction fluctuation may cause performance that is above and below your target in a given day; however, the campaign will seek to deliver the selected performance over time. Learn more about Optimising conversion windows for App campaigns.
Focus on getting more installs (target cost per install and Maximise conversions campaigns)
For campaigns focused on app installs, you can choose to set a bid or not set a bid. If the tick box to set a bid is ticked, this is called a target cost-per-install (Target CPI) campaign. It lets you choose how much you're willing to pay to acquire a new user for your app.
When you set your bid, you're telling Google Ads the average amount that you'd like to spend each time someone installs your app. Bear in mind that your budget will be used to get as many installs as possible at your set amount. So, if you set your average daily budget for £100 and your target cost per install is £2, you're aiming for about 50 installs per day from your ads.
If the Cost Per Install tick box within Campaign Settings isn't ticked, this is called a Maximise conversions campaign. This campaign type will automatically set the right bids for you to provide you with the highest install volume at scale for your campaign’s budget.
Focus on driving selected in-app actions (target cost per action campaigns)
For campaigns focused on in-app actions, you'll set a target cost for driving in-app events. This is called the target cost per action (target CPA). It lets you choose how much you're willing to pay for a new user for your app who is more likely to complete the in-app event that you selected.
When you set your bid, you're telling Google Ads an average amount that you'd like to spend each time someone installs your app and performs the specific in-app action. Bear in mind that your budget will be used to get as many installs as possible at your set amount. So, if you set your average daily budget for £300, and your target cost per action is £10, you're aiming for about 30 actions per day from your ads.
Focus on driving pre-registrations
For campaigns focused on pre-registrations, you’ll set a bid for pre-registrations of your app or game. This is called the target cost-per-pre-registrations. It lets you choose how much you’re willing to pay to get a new user to pre-register for your app or game.
When you set your bid, you’re telling Google Ads the average amount you’d like to spend each time someone pre-registers for your app. This campaign type uses the target CPA bid strategy to help you get the most conversions at or below your target cost-per-pre-registration
Determine your bid strategy for in-app actions
When it’s time to pick a bid strategy, use a budget-weighted average of your existing in-app action bids as a starting point. This section will walk you through how to find that average.
- In your Google Ads account, click the Campaigns icon
.
- Click the Insights and reports drop-down in the section menu.
- Click Report editor.
- Click the plus button
, then select Table.
- Enter 'Conversion' in the search field, then drag Cost / all conv. into the centre of the page.
- Click the filter icon
, enter 'Conversion' in the search field, select Conversion action name, then click Apply.
- Find the action that relates to your campaign optimisation strategy, then look at the 'Cost/all conv.' column for that action to see your average.
, enter 'Conversion' in the search field, select Conversion action name, then click Apply.Use the Bid Guidance widget
The Bid Guidance widget is designed to help you set the right bids to achieve your App campaign goals.
Learn more About bidding tools for App campaigns
Focus on hitting a return on ad spend (target return on ad spend)
This bid strategy is recommended if you seek a specific return on ad spend from your app campaigns.
For campaigns focused on achieving a return on ad spend, you'll set a target return on ad spend value as a percentage of value per spend. It lets you choose what pound value you want back for every pound that you spend.
When you set your target ROAS, you're telling Google Ads the average value that you want back for every pound spent. Bear in mind that your budget will be used to get as much value as possible at your set amount. So, if you set your average daily budget for £300 and your target ROAS is 20%, you're aiming for about £60 of value from your ads over the time window associated with your in-app event.
Depending on your campaign’s daily budget, it's important to note that a trade-off exists between your target ROAS and campaign scale. A higher ROAS target will narrow the pool of potential installs, whereas a lower ROAS target will typically enable the campaign to have more potential to scale.
Setting a recommended initial Target ROAS if you're currently using target cost-per-action campaigns
If you've run target cost-per-action (tCPA) campaigns in the past, your historically achieved return on ad spend (ROAS) is recommended to be used to calculate your initial tROAS target.
When creating your target ROAS campaign, we recommend the below steps to set an initial target ROAS that's reflective of your tCPA campaign’s historical performance. This will assist the campaign to initialise appropriately.
- First, identify your biddable in-app event’s conversion window.
- Then, identify your comparable* campaign’s performance over the duration of that window (for example, for a 30 day window, only look at metrics more than 30 days old).
- *Campaign that is promoting the same App ID, using the same biddable event, with the same location/language targeting settings.
- To do so, enable the 'conv. value/cost' column.
- Your achieved ROAS (conv. value/cost) for the comparable campaign is a recommended starting target ROAS.
Note: This final step in understanding your starting tROAS target may not be applicable to all campaigns.
- Make sure that you factor in your target inflation rate (if applicable) in setting your initial ROAS target:
- Within your historical target CPA campaign: if your target CPA is consistently higher than your campaign’s actual cost per action, you will want to apply a similar modifier to your prospective Target ROAS bid.
- For example, if your campaign’s actual cost per action is £3, and your target CPA is set to £6, you'll need to apply a 50% modifier to your evaluated ROAS to appropriately set a starting target ROAS bid.
- Make sure that you factor in your target inflation rate (if applicable) in setting your initial ROAS target:
After a baseline volume in your campaign has been established, you may choose to adjust your tROAS target. Target ROAS will aim to hit your intended ROAS target over the period of your in-app event’s conversion window.
