Campaigns overview

A campaign is the configuration unit that ties together who gets asked, when they are asked, what they receive if they participate, and how the collection page looks and behaves. Each campaign has a unique slug used in public collection URLs (for example, paths under your app’s /r/ route). You can run multiple campaigns at once—for different products, customer segments, or incentive strategies—and point each integration at the campaign that should receive automated requests.

Campaign settings fall into a few groups. Incentives define the type and value of the reward (such as a percentage discount or a coupon from a pool) and how that reward is delivered (for example, automatically through Shopify or Stripe, or manually). Timing controls how many days to wait after a trigger event before sending the first request, whether follow-up reminders run, and delays for optional external review prompts. Collection page options shape the customer-facing form: copy, rating, media uploads, and disclosure text where incentives are used.

Campaigns can be linked to an integration so that Shopify fulfillments or Stripe payments create testimonial requests in the background. You can also create requests through the API by specifying the campaign. Inactive campaigns stop generating new requests from integrations, but existing requests and testimonials remain in your account for history and reporting.

Best practice is to name campaigns clearly (for example, “Post-purchase — 10% coupon”) and document internally which integration default points where. After any change to incentives or legal disclosure, run a test submission to confirm the customer experience and the reward delivery both match expectations.