Skip to content

View verification and payout eligibility

Ripple uses data from supported, connected creator platforms to follow campaign videos and calculate live estimates. A visible public view count is not automatically a paid campaign view: payment calculations use the performance data Ripple can collect and verify for the public video attached to the submission.

After a creator publishes and attaches the correct public video, Ripple can synchronize available data from the connected platform. A submission may show:

  • public views;
  • likes and comments;
  • engagement; and
  • a combined total when matching campaign videos are attached on more than one platform.

Metrics refresh automatically several times per day. There is no fixed refresh SLA, so recent views can take time to appear. Creators should keep the relevant social account connected and the video public.

Why Ripple does not pay every visible public view automatically

Section titled “Why Ripple does not pay every visible public view automatically”

Public platform counts can change, be delayed or be associated with a video that is not the campaign submission. Ripple therefore calculates using the data attached to the campaign workflow, subject to eligibility and the campaign’s CPM and payout cap.

This protects both sides:

  • creators get a clear connection between their published work, performance and estimate;
  • studios see spend based on campaign submissions rather than unrelated channel totals; and
  • Ripple can investigate material anomalies before a final payout is released.

A published submission must comply with the campaign rules that directly affect payment. In particular:

  • Embargo: publishing before the embargo time automatically sets the submission to payout-ineligible.
  • Required hashtags: required hashtags are part of the campaign brief and are checked by the studio during review (Ripple does not verify them automatically after publication).
  • Authentic traffic: bots, bought traffic and other artificial view manipulation make the submission ineligible for payment.
  • Correct campaign video: attach the real public campaign video from a connected account, rather than an unrelated URL or post.

An ineligible submission has a zero payout estimate. Eligibility is not restored merely by waiting for metrics to refresh.

Before contacting support, check the practical causes first:

  1. Confirm the correct public video is attached to the correct campaign submission.
  2. Confirm the video is public and its connected social account is still connected in Ripple.
  3. Wait for a normal synchronization cycle.
  4. Check whether your estimate has reached the campaign’s per-creator payout cap or shows an eligibility warning.

If the data remains incorrect, contact support with the campaign name, submission and public video link. Do not create duplicate submissions to force another sync.

For the payment timeline, see CPM, live estimates and final payouts. For a material concern or formal review, see Campaign disputes and Ripple review.