Map Customer.io fields to your Vyro form

When Customer.io sends a submission, Vyro stores each value against a field on your form. The keys inside the values object must exactly match your Vyro form field names — Vyro does not rename or translate them for you.

How mapping works

Every key in values is treated as a Vyro form field name.
The value is stored against that field, exactly as sent.
Keys that don't match a field on the form are rejected, and the whole submission fails. Send only fields that exist on the form.

Because the mapping is by field name, the work is done in your Customer.io webhook: set each JSON key to the matching Vyro field name.

Steps

Sign in at https://vyro.co/access.
Open the form you're sending to and note each field's name (not its display label — the name is the key Vyro uses).
In your Customer.io webhook body, set each key in values to one of those field names.

Map your Customer.io attributes to the values, for example:

{
  "form_id": "your-vyro-form-id",
  "showroom_code": "your-showroom-code",
  "values": {
    "first_name": "{{customer.first_name}}",
    "last_name": "{{customer.last_name}}",
    "email": "{{customer.email}}",
    "phone": "{{customer.phone}}",
    "postcode": "{{customer.postcode}}"
  }
}

Send a test submission and confirm the enquiry shows every value on the right field.

Result

Each value appears against its matching field on the enquiry. If you see a 400 error mentioning invalid keys, one of your keys doesn't match a field name — remove it or correct the spelling. See Troubleshoot Customer.io form submissions.

Map Customer.io fields to your Vyro form

How mapping works

Steps

Result

Related