Interactive campaigns are one of the most effective ways to gather first-party data from potential customers. When someone plays your game, they're often happy to share their details in exchange for a chance to win — giving you permission-based data you can act on.

Minigames (formerly Adact) makes that data instantly useful in Optimove. When a live campaign includes a registration (lead) form, the details each participant submits are sent to Optimove automatically through the Customer API — creating or updating a customer for every entry, with no manual export or import.

This guide walks you through how the integration works, the one requirement your form must meet, what data can be sent, and a worked example.

Requirement: The registration form must include an Email field. Optimove uses the participant's email address as the Customer ID, so without it a submission has no identifier and can't be sent.

Step-by-Step: How to Send Registration Data to Optimove

Step 1: Add a registration form with an Email field

In your Minigames campaign, add a registration form and make sure it includes an Email field. This is what lets you collect participant emails — and, because Optimove uses the email as the Customer ID, it's what makes the whole integration work.

Step 2: Choose which details to collect

Decide what you want to gather from each participant. You have two kinds of fields to work with:

Predefined fields — Email, Full name, and Country. Turn on the ones you want to collect. Each maps to a fixed attribute in Optimove (see How the integration works below).
Custom fields — for anything beyond the predefined set, add your own field. Custom fields come in several types, including text input, dropdown (select), checkbox, and multi-line text, so you can collect exactly the information you need.

Step 3: Map each custom field to an Optimove attribute

Every custom field has a Database field name setting. Minigames sends that field to the Customer API using the Database field name as the attribute name. Set it to the exact name of the Optimove customer attribute you want the data to land in.

Important: A Database field name must match a customer attribute that already exists in your Optimove account, and the name must match exactly. If it doesn't, the Customer API rejects the whole submission and the participant is not added. Confirm the attribute exists — and that the spelling matches — before you take the campaign live.

Step 4: Take the campaign live

Once your campaign is live, the integration runs on its own. Every participant who completes the registration form is sent to Optimove automatically — creating a new customer or updating an existing one, keyed on their email address. There's nothing further to configure and nothing to export.

How the Integration Works

Each time a participant submits the registration form on a live campaign, Minigames sends an upsert request to the Optimove Customer API. "Upsert" means create-or-update: if a customer with that email already exists in Optimove, their record is updated; if not, a new customer is created. The participant's email is used as the Customer ID, and every other form field is sent as a customer attribute.

Predefined fields

If you've turned them on, the three predefined fields map to these fixed attribute names:

Registration form field	Attribute sent to Optimove	Notes
Email	`Email`	Required. Also used as the Customer ID.
Full name	`Username`	Sent as a single value (see the note below).
Country	`Country`	Sent as the country name.

Note: The predefined Username attribute isn't part of every account's customer schema. If Username isn't a valid attribute in your account, submissions that include the Full name field will be rejected. If you want to capture a participant's name but don't use a Username attribute, leave the Full name field off and add a custom field mapped to an attribute you do have (for example, a first-name attribute).

Custom fields

Custom fields are how you send anything beyond the predefined set. Each one is sent using its Database field name as the attribute name and the participant's input as the value. Because you control the Database field name, you control exactly which Optimove attribute a field populates — as long as that attribute already exists in your account.

Use Case Examples

Lead generation: Run a prize wheel or quiz with a registration form to collect participant emails, then follow up in Optimove with a welcome or nurture campaign.
Enriching segmentation — collecting gender: Suppose you want to target participants by gender. Confirm a Gender attribute exists in your Optimove account, then add a custom dropdown field to the form and set its Database field name to Gender. Once the campaign is live, every participant is sent to Optimove with their selected gender stored on the Gender attribute — ready to build Target Groups around.
Location-based targeting: Turn on the Country predefined field to capture where participants are based, then tailor offers or send times by region.

Troubleshooting

Participants aren't appearing in Optimove. The most common cause is a field whose attribute name doesn't match a valid customer attribute in your account — either a custom field's Database field name, or the predefined Username attribute where it isn't part of your schema. When that happens, the Customer API rejects the submission with an "Invalid attribute name" validation error. Check every field's attribute name against your account's customer attributes, correct any mismatch, and submit a fresh test entry.

Confirm the form has an Email field. Without one there's no Customer ID, so nothing is sent to Optimove.