App identity and acquisition method
A Google App campaign proposal needs a real, identified application, its store listing, owner and target operating systems. State whether you control the app and advertising account or work under documented authorization. Separate a plan to buy installs from organic store optimization and from a browser-installed PWA.
Provide evidence of ownership or permission to represent the source. Share the actual countries and languages reached, separating measured audience data from estimates.
From advertisement to store and app session
Map the path from the advertisement to the store, installation, app session and any permitted registration destination. The app should deliver the experience described in its listing and creative. Do not use a nominal utility app, hidden destination switching or an unrelated category to disguise the advertised activity.
Show the complete journey, including the page before registration. Every message and destination should match the approved offer and explain what the visitor can expect.
For related preparation questions, consult the In-App traffic guide.
Agree attribution and meaningful metrics
Agree an event map and the tools that connect ad interaction, install, app events and partner reporting. Explain attribution windows, deduplication and material reporting limitations. Separate installs from qualified activity; a cheap install is not evidence that the acquisition source fits the partnership.
Agree the reporting period, definitions and tracking method before delivery. Clicks alone do not establish partner quality; compare the complete funnel without exposing personal user information.
Record the identifiers, route and test evidence using the link and tracking checks.
Prepare a reviewable launch brief
Share the application identifier, store URLs, creative concepts and a testable event specification. Check current Google advertising and store policies, market eligibility and required gambling-related certifications. Campaign creation, app publication and policy approval are distinct checks; none should be treated as automatic authorization for the others.
Discuss the proposal with Ilya Sato at @manager_1xBetpartners. Cooperation is based on RevShare; suitability, current terms and permitted markets require individual confirmation before launch.
For a structured first message, use the first-contact brief.
Practical questions before starting
Is this the same as ASO? No: ASO concerns the store presence and organic discovery; App campaigns purchase distribution. Is a working event enough to launch? Only after its meaning and reporting match the agreed funnel and the source, application, market and materials have been reviewed.
A small, documented test can answer practical questions, but it does not guarantee approval or earnings. Record changes so results can be interpreted accurately.