40

Use form data in Customer.io

How it works

You can use form submissions to trigger campaigns and you can personalize messages using form submission data. This helps you talk to users who fill out your forms.

Each form submission also comes into Customer.io as an event called form_submit. You can use this event to create segments or complex campaign conditions in campaigns that aren’t necessarily triggered by the original form submission.

Trigger a campaign from a form

Form submission events can trigger campaigns, so you can start a conversation with people and foster conversions immediately when they fill out your form.

You can start a form-triggered campaign by going to Data & Integrations > Integrations > Forms and clicking Create campaign for the form that you want to trigger your campaign. This automatically populates a campaign trigger with your form name.

Or you can create a form-triggered campaign from the Campaigns menu:

1. Go to Campaigns and click Create Campaign.

2. Click Form submission.

   

   

3. Choose the form that should trigger your campaign.

4. Continue creating your campaign.

After you activate the campaign, each form submission will trigger a campaign.

Use form data in a message

When someone submits a form, Customer.io captures both the form fields and any URL parameters from the page. You can access these variables in messages using liquidA syntax that supports variables, letting you personalize messages for your audience. For example, if you want to reference a person’s first name, you might use the variable {{customer.first_name}}..

Form Fields come in as event properties and are mapped to customer attributes. You can reference form fields either way in campaigns that are triggered by form submissions, but the two names can be different!

• The event property ({{event.form_field_name}}) reflects the original form field name.
• The customer attribute ({{customer.attribute_name}}) reflects where that field was mapped during setup.

For example, if you mapped a form field called msisdn to phone, then you could access the event property as {{event.msisdn}} or the customer attribute at {{customer.phone}}—both represent the same value!

You might be able to use either event data or customer data, but there are situations when you should use one over the other:

• Use customer attributes when: You need to reference form data in campaigns that are not triggered by form submissions. Attributes may also have friendlier names than event properties.
• Use event data when: You need to reference URL parameters or fields that aren’t mapped to customer attributes. URL parameters are only available as event properties in campaigns triggered by form submissions. For example, if you want to reference a URL parameter from your form page called referred-by, you would use {{event.referred-by}}.