Describe the buying setup, not just the network
Send the DSP or ad network name, buying method, placement format, target GEO and device mix. Explain whether you run the campaign directly or aggregate traffic from several sources. If several publishers are involved, describe how you can separate them in reporting and remove a placement when needed.
Specify the formats you want to discuss, such as display, native or video. A format named here is not automatic approval. Confirm both the source and the planned creative with the manager before buying traffic.
RevShare needs a different test plan
Cost per thousand impressions or cost per click describes your buying cost. It is not the affiliate program’s payment model. RevShare is based on attributed qualifying revenue under the agreed terms, so a low click cost alone does not establish a profitable campaign.
Agree the test budget, reporting period and a point at which you will review the campaign. Track spend, outbound clicks, attributed activity and qualifying revenue separately. A short test may not describe later revenue; do not substitute an assumed fixed CPA for the actual agreement.
Before discussing a percentage, work through the RevShare questions and calculation example.
Agree tracking before setting campaign macros
Provide your tracker name and the IDs you need to distinguish sources, placements and creatives. Ask which parameters and events are supported. If you need an S2S postback, confirm the event, identifier, endpoint format and test procedure before enabling it. This page does not promise a particular integration.
- Check one example URL after campaign macros have been replaced.
- Confirm that redirects retain the issued attribution parameters.
- Compare a defined test period using the same time zone in both reports.
- Record what to do if a placement’s clicks or events stop matching.
Record the identifiers, route and test evidence using the link and tracking checks.
A brief a buying team can send
Share this brief before campaign activation. The budget is your proposed test, not a revenue forecast or a commitment from the program.
For a structured first message, use the first-contact brief.
What should change when a test performs poorly?
First check attribution, destination availability and report timing. Then compare sources and creatives using the agreed identifiers. Ask the manager which data is needed for a review rather than increasing volume to compensate for an unexplained discrepancy. Keep a record of approved creative and source changes.
CTV and cross-device attribution
For connected-TV inventory, separate a completed video view from a measurable visit or registration. Describe the publisher or app, device environment, placement, frequency cap and how an adult viewer reaches the agreed page. If a QR code or a second device is involved, document that journey and agree which attribution evidence the programme can actually support. Do not report view-through estimates as confirmed affiliate registrations.
Separate inventory from delivery routes
Describe each test segment with a small inventory record rather than only a network name:
- Publisher: [site domain or app bundle ID], marked known or unavailable.
- Supply: [DSP/network] → [intermediary, if any] → [placement ID].
- Delivery: [format] → [browser, web view or documented second-device route]; creative [version].
Add the period, spend and defined click count for that segment. Keep different routes separate even when they use the same publisher. If a supplier cannot disclose an identifier, do not invent one: state the limitation and ask which reporting or exclusion controls are actually available.
Adding this source to an existing affiliate portfolio? Keep the current placement record and agree how the new 1xBet placement will be identified and checked. The existing-project guide walks through that sequence.