Home / Blog / Klaviyo and Brevo Properties
Send Klaviyo and Brevo custom properties from on-site forms
A capture form can collect far more than an address: quiz answers, a size, a budget, a hidden campaign name from the URL. Whether that data reaches Klaviyo or Brevo depends on one thing: the field name you send must match the property name the platform expects. Most missing data is a naming mismatch or a property that was never created, not a broken integration.
Key takeaway: decide the property names first, use the platform's own key in the field name, send one test submission, then look for the property on the contact record. An empty property after a test is a naming problem, and guessing wastes more time than the test.
The short answer
- Custom properties are created by the first event. Platforms usually create a property when a value arrives for the first time. An empty field sends nothing, so the property never appears and the integration looks broken.
- Names must match exactly. A field called
Skin typeand a property calledskin_typeare two different things. Pick the platform's existing key, or create the property first. - Test with a real value. One submission with a distinctive value is worth more than an hour of settings review: you can search for the value on the contact record.
What usually gets lost, and why
| Data | Why it disappears | Fix |
|---|---|---|
| Quiz answers | Answers are stored in the widget session but not mapped to fields | Map each answer to its own property instead of concatenating them into one text value |
| Hidden fields | Left empty because nothing fills them | Populate from the URL parameter or a fixed value, and check the field is sent even when empty |
| Campaign source | Written into a note or an email body rather than a property | Send it as a property so segments can use it |
| Consent state | Kept in the tool but never forwarded | Map the consent mode and timestamp to properties, which is what lets a segment exclude people who never agreed |
| Numeric values | Sent as text, so comparisons behave oddly | Keep numbers numeric: a budget of "500" should not arrive as "500 euros" |
Klaviyo: profile properties
Klaviyo stores custom data on the profile as properties, and segmentation can filter on them. Three practical rules:
- Use snake_case keys. Lowercase with underscores, no spaces, no accents. It survives exports and API calls without escaping.
- Send a list only when you mean a list. A single-choice answer is one value, not an array. Arrays are for multi-select answers and for things like tags.
- Create the property before the campaign. If the first send relies on a property that has never received a value, the segment is empty. Submit one test with a real value before you build the flow.
Brevo: contact attributes
Brevo calls them attributes and requires them to exist in the contact model before you can use them in a template or a segment. The same three rules apply, with one addition: check the type. An attribute declared as a number refuses a text value, and the submission may be accepted while the value is dropped.
Attribute names in Brevo have their own conventions and reserved names for standard fields. Keep custom names distinct from the reserved ones, and do not reuse a name with a different meaning across forms.
The test that settles it
- Choose one property and one distinctive value, for example
quiz_result = dry-skin-42. - Submit the form once with a test address you control, on the published page rather than a preview.
- Search the platform for
dry-skin-42in the contact search, not only on the contact record: a value that exists as an event but not as a property is a mapping problem. - If nothing appears, check the field name in the tool, then the property name in the platform, then the integration log in that order. Ninety per cent of failures are the first two.
- If it appears as an event only, your integration sends events but not profile properties. Fix the mapping rather than building segments on events you cannot filter reliably.
Segments worth building on day one
- Consent state: people who agreed to marketing, so a campaign never goes to the rest.
- Source: quiz, chat, content lock, checkout. It tells you which capture path produces buyers, not just addresses.
- Answer based: one segment per main answer, which is what makes the first campaign feel written for the reader instead of broadcast.
If you are still deciding which capture path to build, our guide to list growth without forms or popups compares them, and the zero-party data quiz guide covers the question sequences that produce usable answers.
Honest limits
Mapping is a contract, and contracts drift. A designer renames a field, a marketing manager edits a quiz, and the property silently stops arriving. Keep a written list of the fields each form sends, check it after every form change, and run the distinctive value test again. Also expect a delay: most integrations are near real time, but the contact record is not always refreshed at the same moment as the event, so give it a minute before declaring a failure.
Send the answers where you can use them.
GrowthTools maps each captured field to a destination property, so quiz answers and consent state land on the contact record.
Create your free accountQuestions
Usually because the answers are stored in the widget but not mapped to profile properties. Map each answer to its own property with a snake_case key, then submit one test with a distinctive value and search for that value on the contact record. If it appears as an event but not as a property, the integration is sending the event without the profile fields.
Yes in practice: Brevo calls them attributes and they must exist in the contact model before you can use them in a template or a segment. The difference that catches people is type: an attribute declared as a number will not keep a text value, even if the form submission appears to succeed.
Not always, since many platforms create it on the first event that carries a value. But an empty field sends nothing, so the property can stay invisible for weeks. Create it first when a campaign or a template depends on it, and check the type while you are there.
Usually seconds to a couple of minutes for the event, with the contact record refreshing shortly after. If nothing has arrived after five minutes, treat it as a mapping problem rather than a delay, and check the field name and the property name before anything else.
Run the distinctive value test on one form.
Create a free account, map one property, submit a test, and confirm it on the contact before you build a segment.
Create your free accountPublisher: GrowthTools by Seinsights. Product demonstrations are illustrative; results depend on your site and campaign.
Create your free account