Your first campaign

Follow a first-pass walkthrough from a new campaign to a published test link in about 15 minutes.

This guided walkthrough gets you from a new campaign to a published test link in about 15 minutes. The end state is a simple Wheel game with one reward, a working test URL, and opt-in disabled for speed.

Keep the first pass simple

This walkthrough deliberately skips advanced setup such as opt-in, participation forms, notifications, and add-on tuning. The goal is to publish one working campaign first, then build on top of it.

Prerequisites

You can access Studio. If not, follow the access request process.
You have permission to create or edit campaigns in the organisation you are currently viewing.
You have one simple reward idea for testing, such as a coupon, voucher, or demo prize.

Main task

Open Studio and start a campaign

Log in to Studio and open Campaigns. Create a new campaign from a blank setup or from an approved template, depending on how your organisation usually starts new work.

Fill the campaign properties

Set the campaign title, slug, language, and timezone in the campaign properties area. The slug should be unique, and the language and timezone should match the audience you are targeting.

These values affect URLs, validation, and downstream content. If you are creating the campaign from a template, keep the right source language and confirm that the timezone still fits the target organisation.

Set the campaign dates

Open Settings, then the campaign dates area, and set the start date and end date. Campaign dates define the overall operating window for the whole campaign, so get these right before you add touchpoint-level exceptions later.

Add your first touchpoint

Open Touchpoints, click Add New Touchpoint, and choose New Wheel Game. This creates the interactive element players will open in Pages.

In OmniLab vocabulary, the touchpoint is the unit users actually play, scan, unlock, or open.

Configure only the minimum touchpoint details

Give the wheel touchpoint a clear player-facing title and keep the first setup intentionally light. You only need enough configuration to make the touchpoint understandable in a test run.

Create one simple reward

Open Rewards, then use Add New Reward or Create Reward to create a single reward for the wheel. At minimum, complete the reward title, icon, quantity, and winner messaging so validation has the basics it needs.

Link the reward to the wheel

Return to the wheel touchpoint and associate the reward you just created. OmniLab treats rewards as reusable campaign-level objects, then links them to the touchpoints that should distribute them.

Leave advanced options off for the first pass

Keep Terms & Conditions Settings, participation forms, and notifications disabled for now. This first campaign is about understanding the core flow, not about covering every production requirement.

Review validation before publishing

Click Publish to trigger OmniLab's validation checks. If the platform reports missing timezone, invalid dates, missing rewards, or missing required content, fix those blockers and run the check again.

At this stage, the most common issues are incomplete dates, missing touchpoints, or reward content that was left empty.

Publish the campaign

Once validation is clean, confirm Publish. The campaign is now available in the consumer-facing layer.

Open the test link and play once

Go back to Build -> Touchpoints, then use Share or Preview on the wheel touchpoint to open the live URL or QR code in Pages.

If the campaign uses a landing page, use the landing page URL or QR code there instead of the direct touchpoint link. Play through the wheel once so you can confirm the touchpoint, reward, and end-to-end experience behave as expected.

Result

You now have a first published campaign with one touchpoint, one reward, and a live test URL. That is enough to understand the basic Studio-to-Pages flow before you add consent, forms, notifications, or more complex reward logic.