App publisher and Meta account relationship
Describe the app, publisher, advertising-account relationship and proposed Facebook or Meta placements. State which countries and languages the test targets and whether the app is under your control. Treat each new app and account arrangement as a proposal requiring its own review, rather than assuming blanket acceptance.
Provide evidence of ownership or permission to represent the source. Share the actual countries and languages reached, separating measured audience data from estimates.
Keep ads, store pages and app screens consistent
Show the advertisement, store listing, application screens and registration journey as one consistent experience. Identify the promoted product clearly. Do not use hidden WebViews, surprise destination changes, fabricated accounts or borrowed identities to present a gambling-related offer as a different type of application.
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
Prepare an event plan that distinguishes click, install, first app session and agreed downstream events. Explain the chosen attribution method and its limitations across devices and privacy settings. Compare partner reports and acquisition data at an aggregate level, documenting expected timing differences instead of silently merging incompatible totals.
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
Send ownership evidence, application identifiers, sample creative, store links and proposed markets. Check current Meta advertising policies, any required written permission or certifications and the relevant store rules. Confirm eligibility for the actual product and geography before committing production work or advertising spend.
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 this page mean every app campaign is accepted? No; the source, market and user journey are assessed individually. Should an old approved creative be reused unchanged? Review its claims, destination and current permissions first. New versions or changed placements may require an updated brief.
A small, documented test can answer practical questions, but it does not guarantee approval or earnings. Record changes so results can be interpreted accurately.