Run a Quest Campaign
Prepare quests, audience, rewards, and a Web Hub V2 experience in a persistent campaign workspace.
Start a draft
Open Campaigns, choose Run a… and Run a Quest Campaign. Name it to create a saved draft. Creating the draft does not create quests or send messages. Move freely between the workspace sections and use Save changes for Details and Audience.
Reuse the quest library
Create a quest with the existing editor, copy a saved quest template, or attach an existing quest. Campaign-created quests use the campaign dates and audience. Attached quests share the existing record: edits apply everywhere, and their independent availability stays unchanged. Quests remain visible in Gamification’s quest library, with campaign links and a campaign filter. Removing a campaign-owned draft quest does not make it independently available.
Preview the member experience
Add at least one quest, save Details, and choose Preview & refine hub experience. Harbor creates a draft Web Hub V2 page using the existing quest widget, with a preview of real draft quests and rewards. Refine and save it in the visual editor, then return to the campaign. Later campaign detail edits do not overwrite the authored page. Refresh the preview after changing quests. Web Hub V2 must be enabled before publication.
Review and publish
Review the readiness checks and exact effects. Publishing reveals the page to signed-in members immediately. Campaign-owned quests open at the configured start time and close at the end time, if set. The server evaluates the saved audience segment when members participate or claim rewards. Published dates and audience are locked. Repeating publication does not create duplicate pages, groups, or sends.
Prepare messages separately
Compose Hub, email, push and Discord DM messages inside Notifications using the existing editors. Each message starts as a draft. Publishing never sends or schedules messages. After publishing, select recipients and explicitly schedule each message at least one minute ahead. Return a pending message to draft to change its schedule; once delivery starts, use Messaging to manage delivery. The workspace shows delivery, failure, open and click counts. Messages are manually addressed and scheduled; playtest acceptance does not automatically send one.
Results and archiving
Results count unique member–quest completions of campaign-owned quests within the campaign window. Repeat claims are not counted again; attached independent quests are excluded because their participation may originate elsewhere. Totals cover all participants; the table shows the latest 100. Archiving closes campaign-owned quests and archives the hub page. Attached independent quests and already scheduled messages retain their separate settings.
Agent implementation notes
Quest Campaigns use the admin-authenticated POST /dash/campaign/quest-workflow endpoint with action create, get, save, attach, remove, preview, publish, or archive and the normal AccountTarget. Records remain canonical Quest, Notification, QuestGroup, and WebHubPageMeta records. CampaignQuestLink represents attachments; Quest.CampaignId represents immutable campaign ownership. This dashboard endpoint does not automatically grant a new external API or MCP tool.