Allowed answers, and sharper Klaviyo attribution
Limit a Text field to a list of answers you choose, send UTM source data and a renamable discount code property to Klaviyo, and see first-time vs. returning revenue and conversion dates on experiments.
This release is about clean data: answers you can group, attribution Klaviyo can segment on, and revenue split the way you think about customers.
Allowed answers on a Text field
A free-text question like "What's your shoe size?" fills up with "9", "nine", "9 US" and "size 9", and none of it groups well in reporting. A Text field can now take a list of Allowed answers under Field Properties.
Type an answer and press Enter, or paste a list separated by commas or one per line, up to 100 answers. Shoppers see the list as suggestions while they type, and the field accepts only answers on the list. Matching ignores capitalization and extra spaces, and the answer is saved exactly as you spelled it. An answer that isn't on the list shows "Please choose one of: …", or your own Validation message.
Fields with allowed answers get the same counts and revenue breakdown in Responses as a choice question, starting from when you added the list.
See Allowed answers.
Klaviyo: know where each subscriber came from
The Submitted Formtoro Form event now includes utm_source, utm_medium, utm_campaign, utm_term and utm_content. They come from the link the shopper arrived on, or from the referrer when the link wasn't tagged (for example google / organic). The source is remembered for 30 days, so a shopper who lands from a campaign and subscribes a few days later still carries it.
These properties are stored on the event, not the profile. Use them to segment and split flows in Klaviyo, and keep in mind that a utm_source value alone doesn't mean the visit came from a paid ad. See Campaign attribution on the event.
Klaviyo: put the discount code where your flows expect it
If your flows already read the discount code from a property of your own, set Discount code property in the Klaviyo mapping for each form. Leave it blank to keep the default, ft_discount_code. The new name applies to codes issued from then on. See Rename the discount code property.
Formtoro also tells Klaviyo's onsite script who a shopper is when they subscribe, so their earlier anonymous browsing merges into the profile you just captured.
Smaller things
- First-time vs. returning revenue. The Revenue section of Analytics now splits store revenue into First-time and Returning customer revenue. See Reading the insights grid.
- Experiment dates and conversion. The experiment page shows when a test started and ended, and each arm shows Sub → conversion next to its opt-in rate: the share of signups who went on to buy. An arm can win on signups and lose on sales, and now you'll see it. See Reading the results.