At a glance
| Field | Detail |
|---|---|
| What | Decide how to connect pre-registration advertising with launch campaigns and install reporting. |
| Who it matters to | App advertisers preparing a release or launching in additional countries. |
| Where | Google Ads pre-registration uses Google Play on Android; TikTok lists website and TikTok Instant Page destinations. |
| When it applies | Before release and when moving from pre-registration reporting to acquisition reporting. |
| Action | Review country eligibility, destination behavior, and conversion definitions before scheduling the handoff. |
App pre-registration needs a launch handoff plan that connects the campaign destination, the release calendar, and the outcome being counted. Our suggested approach is to document those decisions together, so an encouraging pre-launch result does not become an unsupported claim about installed or active users.
Start with country eligibility and the destination
Google’s pre-registration campaign documentation limits the product to Android phones and tablets and excludes child-directed apps. The app cannot already be available for installation or purchase in the targeted country. Its target cost-per-pre-registration bid optimizes exclusively for pre-registrations. These boundaries make release status a buying constraint, rather than simply a scheduling preference. Google Ads product documentation.
Google’s setup instructions require pre-registration to be enabled in Play Console and an APK uploaded to a release track. They also say delivery stops automatically in locations where the app launches. For a staggered release, our suggested check is to review the handoff country by country rather than treating the campaign as having a single worldwide stopping point. Google Ads setup instructions.
Play Console adds an important timing detail: the 90-day pre-registration window starts separately when each country first becomes available for pre-registration. Failure to launch within the allowed window in any participating country can terminate pre-registration across all countries. Review the release calendar before enabling another market. Play Console guidance.
Compare the approaches before reusing a launch plan
| Decision or approach | Source-backed capability | Limitation | Suggested check |
|---|---|---|---|
| Google Ads pre-registration | Sends people to the Google Play listing and optimizes for pre-registration. | Android scope; country release status affects eligibility. | Match targeted countries to their current release status. |
| TikTok pre-registration | Lists Website and TikTok Instant Page as optimization locations. | OS eligibility and detailed counting rules are not specified on that documentation page. | Verify the actual destination and counted action. |
| TikTok launch acquisition | App Install campaigns send people to Google Play or the Apple App Store. | The overview lists several optimization goals without establishing every account’s eligibility. | Review the goal available for the intended launch campaign. |
TikTok’s optimization-location documentation describes pre-registration through a website or TikTok Instant Page. That establishes a different destination choice from Google’s store-linked campaign. It does not establish an identical registration event, attribution basis, or automatic launch-day transition. Those details are not specified in the cited documentation; check them in the proposed campaign setup before adopting the same reporting labels. TikTok optimization locations.
For acquisition after release, TikTok’s App Promotion overview lists click, install, in-app event, and value optimization options. Our recommendation is to write down the intended launch outcome separately from the pre-registration outcome, then confirm the relevant setup and eligibility. A click goal and an in-app event goal should have distinct success criteria in that plan. TikTok App Promotion overview.
Keep registrations, downloads, and first opens distinct
Google explains that Ads can retain a pre-registration conversion after someone unregisters, while Play counts users who remain pre-registered. Ads may also record another conversion when someone unregisters and later pre-registers following another ad interaction. A discrepancy therefore calls for a definition review before a quality conclusion. Google Ads reporting distinctions.
Play Console defines its pre-registration Conversions metric as pre-registered users who installed within 14 days of availability. That population includes installations through early access and other pre-launch testing. Separately, Play describes launch notifications and conditional automatic installation on eligible devices. Neither description establishes that every pre-registered user will open the app. Play Console metric definitions.
Adjust defines an install as a download followed by the first app open; a download without an open does not count. It also defines attribution windows as the periods during which clicks or impressions remain eligible for attribution. Those definitions make its install report a different readout from a pre-registration count or store download report. Adjust attribution documentation.
Our suggested reporting plan is to keep each stage labeled with its event definition, population, and reporting period. Review the measurement data path to document which system supplies each result. Use the resulting distinctions to investigate gaps without assuming that differently defined totals should match.
What to review
- Check each country’s pre-registration start date, release status, and planned production launch against Play’s timing rules.
- Review the Google Play listing or TikTok destination as a prospective user would encounter it.
- Confirm the counted pre-registration action and the intended launch campaign goal separately.
- Compare Ads, store, and measurement reports only after recording their event definitions and included populations.
- Keep early-access installations identified when interpreting Play’s pre-registration conversion metric.
- Check first-open measurement before using launch downloads as evidence of app usage.



