Website ownership and the real traffic source
Identify the website owner, PWA domain, product purpose and how visitors reach the site. A PWA is a browser-based experience that may be installed where supported; it should not be presented as an app-store listing or confused with paid app acquisition. Explain the real source behind each visit.
Provide evidence of ownership or permission to represent the source. Share the actual countries and languages reached, separating measured audience data from estimates.
Voluntary installation and the registration path
Demonstrate the landing page, optional installation prompt, installed experience and registration path. Let visitors understand what installation changes and how to remove it. Avoid system-warning imitations, forced installation, hidden redirects or a suggestion that installing the PWA guarantees access, platform approval or earnings.
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
Define how an approved attribution identifier is retained across browser visits and the installed experience, subject to user choices and applicable requirements. Test return visits and avoid double-counting an installation as a second user. Distinguish installation, engagement and registration rather than combining them into one conversion.
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
Provide a working preview, screenshots, event map and the source’s audience evidence. Check browser behavior, product permissions, local requirements and any third-party service rules. If notifications are proposed, explain their separate permission request, purpose and withdrawal process; installation alone must not be treated as consent to marketing.
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
Does a PWA replace approval of the traffic source? No; both the acquisition method and product journey require review. Must every visitor install it? No; describe a usable voluntary experience. If a technical behavior differs by device, include that limitation in the brief rather than promising identical support.
A small, documented test can answer practical questions, but it does not guarantee approval or earnings. Record changes so results can be interpreted accurately.