What a campaign includes

A HighAdvocacy campaign is one set of strategy, branding, and reward rules that can run on two channels at once: the embedded widget and the hosted webpage. You configure each campaign once and choose which channels it ships through.

Every campaign holds:

A campaign name and the objective behind it (volume, coverage, retention, or your own variation).
The target review platforms submitters are being directed to.
Branding pulled from your workspace profile (logo, brand name, and primary color) which is shared across both channels.
Channel-specific copy: widget headline and subtext for the embedded experience, hero title and hero subtitle for the hosted webpage. If you put in invalid copy on the webpage fields, the system falls back to safe defaults and shows a non-blocking notice.
Reward configuration and reward versioning rules (see reward versioning).
Channel state: widget on or off, webpage on or off. Both default to on for new campaigns; at least one channel has to be on for the campaign to be active.
The hosted webpage URL, which is generated once and stays stable for the life of the campaign.

The Campaigns list with channel state badges so users can read campaign state at a glance

Recommended setup flow

Campaign creation runs through three steps with progressive disclosure. Start from the Campaigns list and click Create campaign.

Strategy & Rewards. Name the campaign, set the objective, pick the target review platforms, and configure the reward (and reward versioning behavior if needed). The company domain field on this step is prefilled from your account profile but is editable per campaign; it is used for trust and display context only, not for DNS hosting.
Design. Set the widget headline and widget subtext, and set the hero title and hero subtitle for the hosted webpage. The shared branding (logo, brand name, primary color) comes from your workspace profile. Use the inline preview to flip between widget and webpage, and between desktop and mobile, while you edit. The preview reflects unsaved changes live.
Distribution & Install. Confirm channel state (widget and webpage both default to on), copy the install code for the widget, run the widget test installation if you embedded the code on a real site, and copy the hosted webpage link. Publish when ready.

Campaign activation is blocked when both channels are off. Make sure at least one channel toggle is on before publishing.

The first step of the builder so users see what configuration happens up front The Design step with the inline preview surface so users understand the channel and device switches

Editing a live campaign

After a campaign is published, open it from the Campaigns list to edit. The channel toggles for widget and webpage move from the Distribution & Install step into the top campaign header area so you can change channel state without going back through the builder.

Edits are scoped to the campaign: you can change strategy, design copy, and reward fields. Branding (logo, brand name, primary color) still comes from the workspace profile, so updating brand identity in workspace settings is what updates the campaign visuals.

The hosted webpage URL is locked. The URL is generated once per campaign and stays stable across edits and across enable/disable cycles. Regeneration is not supported, so any link you already shared continues to work as long as the webpage channel is on.

Make small, intentional changes. Use the inline preview after each edit to confirm the widget and webpage both render the way you expect, and switch the device preview between desktop and mobile before saving.

The channel toggles in the campaign header on a live campaign so users know where to flip channels after publish

Mid-flight change behavior

Mid-flight changes do not retroactively rewrite the experience for people already partway through a submission. New visitors see the new version. People already in flight may continue with the version they started on. This matters most for prompts, limits, and rewards.

For rewards specifically, HighAdvocacy uses reward versioning to keep promises consistent. Once a submitter has started a flow under one reward version, that promise stays in effect for them, even if you update the reward field later. New submitters see the new version. For the full mechanic, see reward versioning.

Rules of thumb when editing a live campaign:

Copy edits are safe. Fixing a typo, sharpening the headline, or rewriting the hero subtitle is low-risk because anyone in-flight continues on the version they started.
Reward changes are higher-stakes. Plan the new version first, then update the field; the previous reward promise stays with anyone already in flight.
Avoid toggling both channels off, even briefly. Both-off blocks campaign activation and disables your hosted URL (the URL shows a branded unavailable state, not a 404).
Channel toggles take effect immediately for new visitors. Existing in-flight submitters complete the flow they started on.

Pause vs deactivate

HighAdvocacy treats “paused” and “no active channels” as different operational states.

Pause the campaign. Use this when you want to stop new submissions everywhere but keep the campaign configuration intact for later. The campaign moves out of an active state in the Campaigns list.
Turn off a single channel. Flip the widget toggle off and leave webpage on (or the opposite) when you want to keep collecting through one surface and stop the other. The campaign stays active as long as at least one channel is on.
Turn both channels off. This blocks campaign activation. The hosted webpage URL serves a branded unavailable state page (not a 404), so anyone who clicks the link still sees a polite “not currently accepting submissions” surface rather than an error.

For most short interruptions (a quick copy fix, a reward update, a holiday window) pausing or flipping a single channel is the cleaner move. Keep both-off for rare cases where you want the campaign fully dark but not deleted.

Duplicate a campaign

Duplicating a campaign is a single-click action from the Campaigns list. The duplicate carries over campaign strategy, branding, channel configurations, and channel states. It does not carry over submissions or analytics history; those stay with the original.

Use duplicate when you want to:

Run the same play on a new platform (clone the original, change the target platform).
Test a variant of the copy without rewriting the live campaign.
Spin up a regional version with the same strategy but different distribution.

After duplicating, rename the campaign so it does not collide with the original in the Campaigns list, then walk it through the same three builder steps to confirm the channel toggles, copy, and reward all match what you want for the new variant.

Both channels stream submissions into the same backend. Use the source filter on the submissions view (All, Widget, Webpage) to break out where submissions are coming from. There is no separate per-channel analytics dashboard in V1, but the source marker is on every submission row in the submissions table.

For the widget, share the install code with whoever maintains the page the widget should appear on. The install code is on the Distribution & Install step during creation and stays accessible from the campaign after publish. The widget test installation flow is retained from the existing model; use it to confirm the widget renders correctly on your site after embedding.

For the hosted webpage, copy the link from the Webpage Link card and share it in customer emails, success messages, outreach sequences, or social posts. The URL is stable across edits and channel toggles. Hosted webpages are noindex by default, so they will not be picked up by search engines. That is intentional, since they are meant to be shared with a known audience.

For a deeper comparison between the two channels and which to lead with, see widget vs webpage campaigns.