Proof submission rules

Proof is the evidence that a submitter actually completed the action you asked for. It is what makes a reward defensible and gives your team something to verify before approving.

This page covers what counts as valid proof for each kind of campaign, what fields are required, and the validation rules submitters run into in practice.

What counts as proof

Proof shape depends on the campaign type and platform:

Review and social-post campaigns (G2, Capterra, LinkedIn, X, etc.): a URL to the published review or post, or a screenshot, or both. Either one is sufficient. The submitter does not need to provide both.
Single engagement (like, follow, reshare, comment): a screenshot of the completed action. Reshare and comment also require a URL pointing to the resulting repost or comment. Like and follow are screenshot-only; they are verified by what the screenshot shows.
Bundled engagement (multiple actions for one reward): one or more screenshots in a multi-upload gallery, plus the URLs that the enabled actions require (reshare URL if reshare is enabled, comment URL if comment is enabled).
Video testimonial: a recorded video from inside the submitter flow, plus star rating, name, and email.
Text testimonial: the testimonial body inside the configured character minimum and maximum, plus star rating, name, and email.

Required submitter fields

These apply across all campaign types unless noted:

Email is always required. It is how submitters receive their status update emails.
Name is required on new testimonial submissions (video and text) on the redesigned collection page. Legacy testimonials may not have a name on record.
Star rating (1–5) is required on every new testimonial submission. Legacy testimonials may not carry a rating.
URL fields, when shown, must be a valid URL format. Most submitters paste a full https:// link to the published review, post, repost, or comment.
Character minimum and maximum apply to text testimonials. Marketers set both; minimum cannot be greater than maximum.

Validation submitters see

The flow does not silently fail. When a submission cannot continue, the submitter sees a specific validation message instead of a blank or rejected button:

Missing required fields (rating, name, email)
URL not in valid format
Text body below the configured minimum characters
Text body above the configured maximum characters
Screenshot file type not supported
For X drafts, exceeding the 280-character limit
For bundled engagement, missing a required URL when the matching action is enabled

The Submit button is also held inactive until the minimum requirements are met. For review and social-post claims, that means a screenshot or a URL has been provided.

Common reasons a submission gets blocked

AI generation failed. If the AI service is unavailable, the submitter sees a pre-cached marketer-approved fallback draft, never a raw error. The flow continues; they can still post and claim.
Camera or mic permission denied. Video testimonials need browser permission for camera and microphone. Without them, the recording surface cannot start.
Recording interrupted. If a video recording is interrupted mid-flight, the submitter is shown a retry path. In-memory recordings are not expected to persist if they refresh the page.
Stale draft after marketer edits. If a marketer edits the campaign while a submitter is mid-session, the submitter continues with the configuration they started on. New sessions see the latest config.

Marketer-side responsibilities

Before launching, make sure:

The platforms you selected match the kind of proof you can actually verify.
For social campaigns, every action you enabled (reshare, like, comment, follow) has the URL set it needs. Reshare defines the post URL; like and comment inherit it; follow has its own company-page URL.
Reward copy is clear so submitters know what they earn before they start.
AI Assist is configured if you want submitters to start from a draft. Without it, the textareas are blank.

When reviewing a submission, check the proof against the campaign rules: did they post on the right platform, did the URL resolve, does the screenshot match the action, and does the testimonial meet the character minimum.