Put the raid and the read on one clock
Record the incoming raid time, broadcast identity and sponsor segment start and end. Note the time zone used by the recording and analytics. Twitch describes its Analytics Overview stream data as using the viewer’s local time zone; an exported record or third-party dashboard may present time differently.
Do the conversion once and retain the original value beside it. A report that places the raid before a read using one clock and after it using another cannot support a reliable delivery discussion.
The average-viewer buying guide explains why the measurement window matters. A raid is another reason to keep the purchased interval separate from a channel’s overall audience history.
A raid notice describes an event
Twitch’s raid guidance explains that a creator can send an audience to another channel after a stream. The event helps explain a change in viewing context. Its displayed participant information is not, by itself, a record of how long each person stayed or which part of the paid segment they watched.
Retain the notice as evidence of the event. Keep any supplied viewing statistics in their own fields, with their original labels and windows. Do not turn the raid figure into sponsor reach by changing the column heading.
The same caution applies when no raid arrives. An agreed broadcast is not automatically incomplete because an hoped-for audience transfer did not occur. If a separate raid placement was part of the order, identify that commitment explicitly.
Use an event-and-placement record
| Record | Capture | Keep separate |
|---|---|---|
| Broadcast | Channel, stream date and time zone | Channel history |
| Raid event | Observed time and supplied event label | Retained or unique audience |
| Sponsor read | Accepted start and end timestamps | Whole-stream average |
| Viewing evidence | Source, metric and window | Registrations or deposits |
Attach the underlying source where the parties can review it. A brief note explaining a timestamp correction is more useful than silently adjusting the report until the numbers appear to align.
When scoping a casino streamer campaign, decide whether the contract buys a read, a sponsored session or an additional audience-transfer action. Those are separate acceptance questions even when they happen during one broadcast.
Talk to us
Pick a 30-minute slot, or DM us on Telegram.
Scope the read and any separate audience-transfer commitment on their own terms.
Pricing is scoped to your brief. We reply within one working day.
An illustrative raid arrives after the read
Imagine a fictional read ends at 20:31 and an incoming raid appears at 20:35, on the same verified clock. The later audience context cannot establish how many people saw the earlier read. The team keeps the sequence visible in the report.
If the creator voluntarily repeats the product explanation afterwards, record the repeat and its actual timing. Confirm whether it satisfies an existing obligation or is extra work. Do not rewrite the original schedule as though the first read happened later.
This example supplies a reporting decision, not a normal raid pattern or an estimate of conversion. A different sequence needs its own review of the available evidence.
Treat traffic anomalies as review questions
A sudden change may deserve investigation, but a raid is not proof of artificial traffic. Equally, an announced raid does not certify every audience number in the report. Use the event to ask a narrower question about the relevant interval.
Avoid collecting private viewer identities to make the report look conclusive. Ask for the least intrusive source that answers the contracted measurement question. If compatible audience evidence is unavailable, state that limitation.
The creator campaign reporting guide separates delivered placements from business outcomes. A raid event cannot establish a registration, first deposit or incremental customer without the separately agreed measurement evidence.
Make the next brief explicit about repeats
Decide before broadcast whether a late raid changes the plan. The brief can name who may authorize another read, what factual copy remains approved and how any extra work is recorded. It should not compel the creator to turn every arrival into an improvised promotion.
After the stream, close the placement record first. Then describe the raid as context for the observed window. That gives the buyer a defensible account of what happened and gives the creator a clear basis for reconciling the order.
Frequently asked questions
Can the raid count be reported as sponsor reach?
Only evidence that actually supports that claim should carry it. A raid notice alone does not establish unique sponsor viewers or their time spent watching the read.
Does a raid prove a viewership spike was genuine?
It provides event context, not a complete audit of every reported audience figure. Keep the event and the measurement evidence separate.
Should a creator repeat the sponsor read after a raid?
Agree that decision in the brief, including who can approve a repeat and how it is recorded. A raid does not automatically change the accepted order.
Results from campaigns our team has run
Web3 game · gaming creators, streams and events
Illuvium
6,550 new players and 24,000+ followers
Read the Illuvium caseCrypto exchange · KOLs on X, YouTube and TikTok
Binance
4,245 new users and more than $510M in trading volume, double the target
Read the Binance caseCrypto banking · influencers and growth
Swissmoney
32,000+ users onboarded and CPA cut 4x
Read the Swissmoney case
3betmedia launched in 2026; most of these campaigns ran before the name existed. See all 19 cases.
Sources and further reading
The decision aids and fictional examples are original production guidance. Primary references support their stated platform or policy facts. Actual permissions, applicable rules and campaign outcomes need their own evidence and responsible review.
