Signal Math / Field guide

Creator metrics and delivery: connect audience signals to a usable file

Keep engagement, watch time, revenue, campaign cost, and delivery arithmetic separate while planning a creator deliverable.

Name the event and denominator first

Engagement, campaign cost, creator revenue, watch time, and file delivery describe different events. For example, 250 engagements from 10,000 views is 250 / 10,000 = 2.5%. Keep the event definition and view population visible; the percentage is not a quality score or a promise of distribution.

Watch time is audience-volume arithmetic: 10,000 views at 45 seconds each is 10,000 x 45 / 3,600 = 125 hours. Creator revenue is a separate scenario: 240 across 60,000 views is 240 / 60,000 x 1,000 = 4 per thousand views. Use the watch-time calculator and creator RPM calculator with their own definitions.

Worked example: bitrate, size, and transfer time

At 10 Mbps for 60 seconds, encoded data is approximately 10,000,000 x 60 / 8 / 1,048,576 = 71.53 MiB, before container overhead and other streams. A 1,024 MiB file transferred at 20 Mbps takes approximately 1,024 x 1,048,576 x 8 / 20,000,000 / 60 = 7.16 minutes before network overhead. These examples use decimal megabits and binary mebibytes; the calculators label the units rather than pretending a platform's upload result is guaranteed.

The production and signals hub links format, audience, text, and delivery tools. Destination specifications can change, and a general unit reference such as the NIST SI units reference is not a review of any platform's current requirements.

Before deciding on delivery

Use these calculations to organize inputs, then confirm the destination's current requirements and your own evidence.

Separate planning signals from outcomes

  • Record denominator, event definition, date range, and whether counts are unique or repeated.
  • Keep advertiser cost separate from creator compensation and entered revenue.
  • Check frame ratio, bitrate, codec, audio, file size, and destination requirements separately.
  • Do not present a scenario as observed reach, guaranteed earnings, or guaranteed acceptance.

Examples are illustrative and use one consistent currency, not market data or personalized financial advice. Displayed figures are rounded. See methodology and numeric limits before using your own inputs.