At a glance
| Field | Detail |
|---|---|
| What | Choose a Google Ads campaign, inventory scope and bidding goal for acquiring app users through YouTube. |
| Who it matters to | App buyers deciding between automated app acquisition and a controlled Shorts placement test. |
| Where | YouTube, including Shorts; App campaigns also serve across other Google properties. |
| When it applies | When planning acquisition or evaluating whether a video campaign's reported conversions match the intended app outcome. |
| Action | Specify the acquisition event, placement requirement and attribution basis before choosing the campaign. |
YouTube app install ads involve separate decisions about the campaign, where it serves and which event it optimizes toward. Our suggested starting point is the app outcome: decide whether the test needs new users, a meaningful in-app action or a particular placement. Then check which campaign supports that requirement and how its results will be measured.
Choose the campaign around the decision
Google's Shorts campaign comparison assigns different jobs to different campaign types. App install and re-engagement campaigns address app acquisition and existing users respectively; video view campaigns address consideration and views, while video reach campaigns address awareness. A Shorts placement therefore does not establish that a campaign is buying installs. Keep the acquisition and awareness questions separate in the brief and readout.
Google's App campaign documentation for Shorts is explicit: App campaigns serve across Google inventory and cannot buy only YouTube Shorts. Their coverage includes Search, Google Play, YouTube, Discover and the Google Display Network. For a buyer, our interpretation is that this is an automated acquisition option with Shorts access, rather than a way to isolate a Shorts placement experiment.
| Buying approach | Supported purpose | Control or limitation | Suggested review |
|---|---|---|---|
| App campaign for installs | Acquire app users and optimize toward supported app conversions. | Shorts is part of broader inventory; Shorts-only buying is unavailable. | Check the selected app conversion and the scope of the campaign readout. |
| Demand Gen | Drive engagement and action with selectable channels. | Manual channel controls can select Shorts; this control alone does not establish an app-install bidding setup. | Verify the conversion goal and destination before treating it as an acquisition alternative. |
| Video view or video reach campaign | Pursue consideration, views or awareness. | The stated objective differs from app acquisition. | Evaluate against the objective selected, keeping app outcomes distinct. |
Decide whether placement isolation is necessary
Google's Demand Gen channel controls operate at the ad group level. Manual selection can isolate YouTube Shorts, and reporting can separate YouTube formats. Google also recommends automatic selection across channels for most advertisers and cautions that restricting delivery may reduce overall efficiency.
For a placement question, we suggest documenting why isolation matters before choosing it. A campaign intended to learn about Shorts has a different scope from an acquisition campaign allowed to seek conversions across inventory. Compare each result against its stated objective; a format breakdown and a campaign total answer different questions. Avoid assuming that a control documented for Demand Gen also exists in App campaigns.
Match AI bidding to the app event
Google's App campaign bidding guide distinguishes target cost per install, target cost per action and target return on ad spend. These pursue installs, selected in-app actions and value-based returns respectively. The guide also warns that selecting multiple actions can create a blended cost target for events with different values.
Our suggested check is to name the event the bid is meant to buy. If the business decision concerns paying users, report that outcome alongside installation volume. An install target and a purchase target answer different questions; choosing automated bidding does not make them interchangeable. Check account availability too: Google identifies Maximize conversions for in-app actions and Maximize conversion value as limited-access beta options in this documentation. Do not build a plan around presumed access.
Align the destination and attribution readout
Adjust's Google Ads setup guidance recommends App campaigns when the goal is app installs. It describes a separate web-to-app measurement setup, including Discovery / Demand Gen, and warns that Google Ads might not claim attribution for some web-to-app users. Treat that distinction as a measurement check: if the proposed journey uses a website before the app, review that path with whoever owns the integration before comparing its results with direct app acquisition.
The AppsFlyer attribution model records an acquisition install after download and first launch, using first launch as the install timestamp. AppsFlyer contrasts this with engagement-time reporting by ad networks and download-time reporting by app stores. Our suggested comparison therefore starts with the event definition and date basis, rather than assuming identically labeled totals describe identical cohorts. This does not establish any campaign's incremental contribution or profitability.
What to review
- Write down whether the decision concerns acquisition, post-install behavior, awareness or placement learning, and match the campaign objective to it.
- Check whether Shorts-only delivery is essential; confirm the selected campaign actually supports the required control.
- Record the app event used for bidding, its business meaning and any account eligibility limits before approving the test.
- Trace the destination through any website and app handoff, and verify the applicable measurement setup.
- Align install definitions and reporting dates before comparing platform and measurement reports.
Use outcome planning to define the buying decision. Review the event-to-report path when agreeing on the event and reporting basis for the test.



