Data & feedback
Senders fill in a form to send their gift. What it asks, which consent boxes appear beside it, and how long the answers live are yours to configure.
Who is this gift from?
Sender form
Two fields stay off until you enable them.
Where it acts
At the end of a recording, the sender types their name and email — not because a banner asked, but because the gift has to reach someone.
The form closes the recording: sender details, a recipient address when needed, then your consent lines.
The consent list is declared in the platform’s general settings.
A viewer’s page carries the sender’s name and email — never the recipient’s details or the consent answers.
A read on /messages returns the stored form data to a key with the right scope.
How it works
The video is recorded. The form comes next, before the gift is sent.
Sender details, then one line per consent you declared, under the mandatory box.
# scope: messages:readGET /api/v3/messages/msg789{ "state": "released", "data": { "senderName": "John", "senderEmail": "john@example.com" }}Example response, from the API reference.
Each answer is written onto that recording and read through the API.
Good to know
Everything below is either a setting someone has to make, or a limit worth knowing first.
The consent list is one setting; showing it in the journey is another. Declared without its service enabled, a line never renders.
Both start disabled, and only the embeddable widget renders them. A declared country is not the country resolved from the sender’s IP.
At the end of your retention window the journey is archived: form data and stored IP addresses leave with the video file.
Optional fields follow the services enabled on the platform, and an integrator can force others from the widget.
Settled at scopingUnder the fields the gift needs sits the newsletter line you declared: the order gave you a transaction, the recording a person who agreed.
Two platforms
A retail programme and an employee programme run on two platforms. One declares two consent lines; the other asks for nothing beyond an email.
Example brands and answers, for illustration.
FAQ
Sender first name, last name and email, a recipient email or phone when delivery needs one, and the answer to each consent box you declared. Birth date and declared country stay off unless you enable them.
You do. Each line takes its label from a translation string you write, per consent and per language.
Per message. Each recording keeps its own record of which boxes were ticked, so consent stays tied to the moment it was given. There is no per-individual register.
For the length of your retention window. At archiving, the form data and stored IP addresses go with the video — read out anything you need to keep before then.