Notification permission and inventory origin
Identify the publisher or network, inventory type and who obtained notification permission. Explain the countries, devices and audience-selection method, distinguishing web notifications from other formats marketed as push. A large subscriber count is not enough without a credible account of consent and the source of the inventory.
Provide evidence of ownership or permission to represent the source. Share the actual countries and languages reached, separating measured audience data from estimates.
A clear notification and matching destination
Show the exact title, image, message and destination a subscriber would see. Use an identifiable sender and an honest call to action. Do not imitate operating-system alerts, invent account problems or suggest a personal message when the notification is an advertisement. The landing page should continue the same offer.
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 DSP and media-buying guide.
Agree attribution and meaningful metrics
Agree separate identifiers for inventory segments and creative variations where supported. Compare delivery or impression definitions, clicks, engaged sessions and registrations. Watch for repeated or accidental clicks, and explain frequency settings. A high click-through rate does not establish genuine intent if the creative misleads the reader.
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 sample creatives, the permission flow, withdrawal instructions and the proposed source breakdown. Confirm current network policies, product eligibility and permitted markets before launch. Keep notification frequency proportionate to expectations, and respect withdrawal across the relevant system rather than adding the same person back through another list.
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
Can a purchased subscriber list be treated as automatically eligible? No; permission, rights and audience expectations still need evidence. Is this the same as an in-page advertisement? Not necessarily. Describe the actual delivery mechanism so review and reporting reflect the format the visitor really receives.
A small, documented test can answer practical questions, but it does not guarantee approval or earnings. Record changes so results can be interpreted accurately.