Define the user-facing placement
Share the app identifier, the relevant screen or content section, the proposed audience countries and language. Explain whether the destination opens in a browser, an in-app view or another agreed environment. Identify the person who can approve an app update and change the placement after release.
Provide a simple journey diagram or written sequence from the placement to the destination. Include any intermediate page you control. A clear sequence is more useful than asking for “full tracking” without specifying which events the project needs to observe.
Agree the supported technical contract
Ask which links, identifiers and reporting events are actually available for the proposed account and destination. If a postback or another integration is required, agree its format and test procedure through the appropriate programme contact. Do not infer support from an unrelated app or a third-party tracker’s feature list.
- App and placement owner.
- Expected destination and opening behaviour.
- Identifiers that need to survive the journey.
- Supported event definitions and reporting boundaries.
- Contact responsible for testing and release approval.
Plan the first release and its observation
For an illustrative release, keep one placement and one agreed link version, document the app version and check the actual route on the relevant devices. Record the observations using non-personal test identifiers. If a result differs from the specification, capture the affected step before changing several components together.
Contact @manager_1xBetpartners with the source and integration brief. The commercial conversation uses RevShare, and technical availability needs account-specific confirmation. Keep the measurement plan proportionate to the launch: a simple verified journey can provide a stronger starting point than an elaborate integration whose events and responsibilities have never been agreed.