Review & Proof Collection
Audience: Marketers, admins, and submitters
This section covers the part of HighAdvocacy a submitter actually sees: a three-step guided flow that turns “write a review” from a blank page into something they can finish in a few minutes.
The flow is:
- Choose a platform from the campaign’s configured list (review platforms like G2 or Capterra, social platforms like LinkedIn or X).
- Write the review or post, with AI Assist if the marketer has enabled it for the campaign, or from scratch otherwise.
- Claim the reward by submitting proof (a URL, a screenshot, or both).
Submitters move through the same three-step strip whether they opened the campaign through the embedded widget or the hosted webpage; both surfaces use the same component.
How AI Assist drafts reviews using the campaign goal and submitter-selected chips, plus how to configure it as a marketer.
AI-assisted review flowWhat counts as valid proof, the required fields, file rules, and why submissions get held up.
Proof submission rulesWhat marketers configure
- Platforms. Pick from 14 supported review and social platforms (G2, Capterra, TrustRadius, Gartner Peer Insights, Clutch, Trustpilot, Google, GetApp, Software Advice, Product Hunt, AppSumo, LinkedIn, X, Facebook).
- Reward per platform. Type and value: credits, discount, cash, gift card, or custom. See Rewards.
- AI Assist (optional). A one-sentence campaign goal plus eight editable chips that submitters can pick before generating a draft. AI Assist can be toggled on or off mid-campaign and only affects new sessions.
- Distribution. Widget on the product, hosted webpage, or both. See Widget vs webpage campaigns.
What submitters do
- Open the campaign through your install or shared link.
- Pick a platform card. Each card shows the platform name, an AI Draft badge if applicable, how many fields are required, and the reward amount.
- Optionally select chips (multi-select, at least one required to generate) and click Generate my draft. The textareas are always editable, so submitters can write from scratch and ignore chips entirely.
- Copy the draft and post it on the external platform. For LinkedIn and X, a one-click composer link pre-fills the platform’s compose screen with the current draft text.
- Return to the campaign and submit proof. Either a URL or a screenshot is enough. They do not need to provide both.
What happens after submission
- The submission is created with the reward details snapshotted at that moment. See Reward versioning.
- A “submission received” email goes to the submitter within 5–10 minutes (if enabled). See Submission status emails.
- Configured team alerts fire to Slack, Microsoft Teams, Discord, Zapier, email, or a custom webhook. See Notification integrations.
- An Owner, Admin, or Member can approve or reject the submission. Approval triggers an approval email; rejection triggers a rejection email with the optional reason.
- Approved submissions land in the Proof Library automatically.
Related docs
- Campaigns
- Testimonials: testimonial collection uses a different flow inside the same campaign
- Social Advocacy: for post-writing and engagement campaigns
- Troubleshooting: for permission errors, upload failures, and validation issues
Last updated on