Collect Viewer Data

Combine Input Field, Submit Form, and Form Data to collect viewer submissions

Use this guide when an MP5 experience needs to collect information from a viewer, such as lead details, preferences, quiz answers, feedback, registration data, or requests.

The usual setup combines three parts:

• Input Field connector in Studio, so the viewer can type a value.

• Submit Form connector in Studio, so a viewer action submits one or more values.

• Form Data in Platform, so submissions can be reviewed or exported when the project is configured for Blings form collection.

Form collection depends on project and account configuration. Confirm the data collection plan, consent language, storage expectations, and compliance requirements before launch.

Collection Flow

1

Decide What to Collect

List each value the viewer should submit. Give each value a stable field name such as email, phone_number, preferred_plan, feedback_message, or quiz_answer.

2

Design the Input State

In Studio, make sure the visual scene has enough room for the input layer, placeholder text, validation message, submit button, and success state.

3

Configure Input Field Connectors

Add an Input Field connector for each typed value. Confirm the target text layer, field name, placeholder, single-line or multiline behavior, empty-state behavior, and text fit.

4

Configure the Submit Form Connector

Add a Submit Form connector to the button, hotspot, or interactive layer that submits the form. Include every field that should be submitted.

5

Choose Submission Handling

Choose whether values are saved in Blings Form Data or handled by custom code. Match this decision to the integration, security, and compliance plan.

6

Test the Full Viewer Flow

Preview the MP5, enter values, submit, test required and empty fields, confirm success behavior, and check that submission does not break other player interactions.

7

Review Submissions in Platform

Open Platform Form Data when the project uses Blings form collection. Confirm that test submissions appear with the expected field names and values.

Example Setup

Viewer field	Studio connector	Submit behavior	Platform result
Email address	Input Field named email	Included in Submit Form connector	Saved as an email column or field in Form Data.
Plan preference	Input Field or choice-based interaction named preferred_plan	Included in Submit Form connector	Saved with each submission for follow-up or export.
Feedback message	Multiline Input Field named feedback_message	Included in Submit Form connector	Available for review with the rest of the form submission.

QA Checklist

Before publishing a data-collection flow, confirm:

• Field names are stable and approved by the team that will use the data.

• Placeholder copy explains what the viewer should enter.

• Required and optional fields are handled intentionally.

• Long values, empty values, and mobile keyboard behavior are tested.

• The submit layer is clickable and clearly connected to the form.

• Success and failure states are controlled.

• Form Data or custom handling receives test submissions.

• Consent, privacy, and retention expectations are covered.

Deep Dives

Input FieldSubmit FormData, Catalog, and Forms