Survey Builder - User Guide

 1. What is a survey ad?

A survey ad is an interactive ad that asks the viewer one or more questions instead of just showing a picture. The viewer taps an answer, and the ad can react - show the next question, thank them, or send them to the advertiser's website.

Think of it like a mini "choose your own adventure" booklet that lives inside an ad slot:

• Each screen the viewer sees is a Page.
• Each button they can tap is an Answer.
• Tapping an answer decides what happens next.

You build the whole thing visually in the Survey Builder - no code. When you're done, the builder produces a single file (the "config") that our ad system delivers to real placements.

---

2. The three building blocks

Everything in a survey is made of just three things. Understand these, and you understand the whole tool.

Survey

└── Pages (the screens)

└── Answers (the tappable buttons)

└── Action (what tapping does)

Survey

The whole thing. It has a name (for your reference only - viewers never see it), a look (colors, fonts, logo), and a starting page.

Page

One screen. Most pages ask a question and offer a few answers. A special kind of page - a completion page - is the "thank you" screen at the end and has no question or answers.

• A page can show a question, some smaller supporting text, and up to 6 answers.
• A survey can have up to 10 pages.

Answer

One tappable button, with a label (the text the viewer sees) and an action - the single most important choice you make for each answer.

---

3. What an answer can do (the Action)

Every answer does exactly one of these when tapped:

This is what turns a flat list of questions into a flow. Because each answer picks its own next step, different answers can lead to different places - that's how branching ("if they pick A, ask X; if they pick B, ask Y") works.

One question per screen

A page is one question screen. There's no such thing as a second question on the same page - so "go to another question" always means Go to page: jump to another page (usually the next one). You can point it back at a page the viewer already saw (to loop), but normally it moves them forward.

Finish vs. Exit - they are not the same

These two both "end" the survey, but they do very different things. This trips people up, so read carefully:

Finish = "the survey is complete."

• It records the survey as submitted (fires the completion tracking).
• If you give the answer a completion page (a thank-you screen), the viewer is taken there. That screen just stays on display - it does not close itself or disappear. It sits there until the viewer closes the ad, navigates away, or the slot is refreshed by the site/app.
• If you didn't set a completion page, nothing new is shown - the viewer simply stays on the last question screen, with their choice still highlighted.
• Finish never removes the ad. The ad slot stays filled either way.

Exit = "close and dismiss this ad."

• It does not record a submission - it's a "close" / dismiss, like tapping an ✕.
• Inside a mobile app, it asks the app's ad SDK to dismiss the ad - the app takes the ad down (typically removing it, per how that app handles closes).
• On a website, it sends a "please close me" signal to the surrounding page. What the viewer actually sees then is up to that page: a well-behaved host collapses the slot (no gap); a host that ignores the signal leaves the survey sitting where it was. The survey itself does not blank out the slot or leave a white hole on its own - it only asks to be closed.

Rule of thumb:

• Use Finish for the natural end of the survey - especially paired with a thank-you completion page.
• Use Exit for a "close" / "no thanks" / ✕ button that should take the whole ad away.

A completion page has no built-in close. Because it just stays on screen, if you want viewers to be able to dismiss it, either turn on the survey's close (✕) button, or put a button on the completion page whose action is Exit.

What a completion page is for

The completion page is the survey's thank-you/end screen. The survey is already done and counted by the time it appears, so it's not for asking more questions - it's for wrapping up. It can carry buttons, and only two kinds belong there:

• Exit - a "Close" button. This is its prime use. Completion pages have no built-in close, so an Exit button is how the viewer dismisses the ad. Recommended.
• Open URL - a final CTA ("Visit our site", "Claim offer"). Reasonable - and the button's own event pixel lets you track that post-completion click.

What to avoid on a completion page:

• Go to page - sends the viewer back into the survey from the thank-you screen. It undoes the "finished" feeling and can create loops. Don't.
• Finish / Open URL and finish / Open URL and continue - the survey already finished on the way in. The completion is counted once (it won't re-count), so these just add pointless or confusing steps. Skip them.

In short: put a Close (Exit) and, if useful, one CTA (Open URL) on a completion page - nothing else.

Opening a website - same tab or new tab? When an answer opens a URL, you can choose same tab (the ad's page navigates to the website) or new tab (the website opens alongside). Same tab is the default.

---

4. Making it look right

You control the survey's appearance at two levels:

• Whole-survey look (the global style): background colour or image, font, text colours, button colours, corner roundness, logo. Set this once and every page inherits it.
• Per-page tweaks: any single page can override the global look - a different background for the last screen, say.

You also choose an answer layout - how the buttons are arranged:

And a transition - the little animation between pages (fade, slide, none…).

---

5. Building one, step by step

1. Name your survey and pick a size (the placement it will run in).
2. Add pages. For each page, type the question and add answers.
3. Wire the answers. For every answer, pick its action - which page it goes to, or whether it finishes/opens a link.
4. Set the starting page - which screen shows first.
5. Add a completion page - the "thanks!" screen (recommended).
6. Style it - colors, font, logo, per-page tweaks.
7. Preview - click through it exactly as a viewer would. The builder warns you if something is off (see below).
8. Publish - export the config.

---

6. What the builder checks for you

Before you can publish, the builder validates the flow. Two kinds of feedback:

• Errors (must fix - block publishing): a survey that doesn't work. For example: an answer points to a page that was deleted; a page has no question; the viewer could get stuck on a page with no way out; a page can't be reached from the start.
• Warnings (worth a look - don't block): things that are probably fine but might not be ideal. For example: no thank-you page; the placement is small, and a question might get cut off; the same tracking event is used in several places.

If you ever see one of these, the message names the exact page or answer so you can jump straight to it.

---

7. A few golden rules

• Every path must end. From any question, the viewer must eventually be able to finish or exit. The builder enforces this - you can't trap someone.
• Every page must be reachable. A page nobody can get to is flagged as an error. (Usually it means you forgot to point an answer at it.)
• Keep questions short on small placements. Long text gets cut off in tiny ad slots.
• Names are for you; IDs are forever. Renaming a page's title is fine and safe. The hidden ID underneath stays the same so your links don't break.

---

8. Glossary