Create an App ad group and ad

  • App campaigns require ad groups and ads.

  • Create ad groups using AdGroupService and do not specify a type.

  • For APP_CAMPAIGN_FOR_ENGAGEMENT campaigns, you can optionally override the target CPA at the ad group level and must target an audience using AdGroupCriterion and a UserListInfo.

  • For APP_CAMPAIGN campaigns, you cannot override bid settings or add ad group criteria.

  • Add an ad group ad for each set of assets, using the appropriate ad info based on the campaign's advertising channel sub-type.

Each App campaign needs at least one ad group and a single asset-based ad per ad group before it can serve. Create these resources individually with their mutate services, or bundle them with the campaign in one atomic GoogleAdsService.Mutate request by using negative temporary IDs. Depending on the campaign subtype, you also configure ad group bid overrides and audience criteria.

Create an ad group and criteria

Create up to 100 enabled AdGroup resources per campaign by calling AdGroupService.MutateAdGroups or sending AdGroupOperation entries to GoogleAdsService.Mutate. Use separate ad groups to organize distinct creative themes or target segments, and leave the type field unset.

Configure ad group bid overrides

Ad group bid overrides depend on the campaign's advertising_channel_sub_type field:

  • APP_CAMPAIGN_FOR_ENGAGEMENT (optional): Override the campaign-level bid target on the ad group:
  • APP_CAMPAIGN and APP_CAMPAIGN_FOR_PRE_REGISTRATION: Leave the target_cpa_micros and target_roas fields unset. The API rejects target_cpa_micros on both subtypes, rejects target_roas on APP_CAMPAIGN, and ignores target_roas on APP_CAMPAIGN_FOR_PRE_REGISTRATION.

Configure ad group criteria

Add AdGroupCriterion resources with AdGroupCriterionService.MutateAdGroupCriteria (or AdGroupCriterionOperation in GoogleAdsService.Mutate) according to the campaign's advertising_channel_sub_type field:

  • APP_CAMPAIGN_FOR_ENGAGEMENT (required): Target an app-reengagement-eligible user segment by setting the user_list field to a UserListInfo object. Set the UserListInfo.user_list field to the resource name of an eligible UserList backed by your mobile app data.
  • APP_CAMPAIGN (optional): Provide audience signals by setting the audience field to an AudienceInfo object (at most one per ad group). Set the AudienceInfo.audience field to the Audience resource name, and leave the AdGroup.optimized_targeting_enabled field unset or true. Don't attach UserListInfo criteria to APP_CAMPAIGN ad groups.
  • APP_CAMPAIGN_FOR_PRE_REGISTRATION: Don't add AdGroupCriterion resources. Pre-registration campaigns don't support ad-group-level criteria.

Keep the following AdGroupCriterion restrictions in mind across all App campaigns:

  • Leave bid and bid_modifier fields unset on AdGroupCriterion resources. App campaigns don't support criterion-level bid overrides.
  • Keep the negative field set to false (or unset) on audience criteria, because you can't exclude audiences or keywords at the ad group level. To exclude audiences on APP_CAMPAIGN, add campaign-level CampaignCriterion resources with user_list and negative set to true (not supported on engagement or pre-registration). To exclude keywords at the campaign level, link a NEGATIVE_KEYWORDS shared set with a CampaignSharedSet resource (direct negative keyword CampaignCriterion resources aren't supported).

Create an ad group ad

Each App campaign ad group supports at most one AdGroupAd resource. Create the ad with AdGroupAdService.MutateAdGroupAds (or an AdGroupAdOperation in GoogleAdsService.Mutate), and populate the Ad field matching the campaign's advertising_channel_sub_type value:

  • For APP_CAMPAIGN, set the app_ad field to an AppAdInfo object with 2–5 headlines and 1–5 descriptions text assets. Optionally add up to 20 images, 20 youtube_videos, and 20 html5_media_bundles assets, plus mandatory_ad_text and app_deep_link fields.
  • For APP_CAMPAIGN_FOR_ENGAGEMENT, set the app_engagement_ad field to an AppEngagementAdInfo object with 2–5 headlines and 1–5 descriptions text assets. Optionally add up to 20 images and 20 videos assets (HTML5 bundles aren't supported). Also populate the Ad.final_app_urls field with at least one FinalAppUrl deep link matching the app's operating system.
  • For APP_CAMPAIGN_FOR_PRE_REGISTRATION, set the app_pre_registration_ad field to an AppPreRegistrationAdInfo object with 2–5 headlines and 1–5 descriptions text assets. Optionally add up to 20 images and 20 youtube_videos assets (HTML5 bundles aren't supported).

What's next