We have amplitude connected but are missing things in the events stream.
First, the FeatheryStepLoad event is not fired. In this screenshot you can see that it’s in amplitude but only because I manually added it. It’s also why there are no properties. Notice it says “Planned” under the event name vs “Live”.
Compare this to the FeatheryStepSubmit which does have properties:
Second, for FeatheryStepSubmit, it’s good that the formId and stepId are there, but there should be values for the answer data too. Otherwise we cannot filter by those that answered a given question a certain way (and did not complete the survey). See previous screenshot and you can see there are no answer properties.
Lastly, the FeatheryFormComplete also does not have any properties except formId. So we can identify the form but not any of the answers.
Suggestions:
- The
formIdshould be an iD and not the name since that is changeable. Should have bothformIdandformNamewhere the formId is truly the ID in feathery. Much easier to ensure we don’t have any brittleness. - Ditto about
stepIdbut not sure if ID makes sense here vs always calling thisstepName? (e.gstepId":"How did you hear about us?"smells wrong) - For the form data itself, perhaps every completion event (whether step or form completion) you use amplitude’s nested properties feature and add a nested property for every step data. So on a
FeatheryStepCompleteit would be 1 additional property. ForFeatheryFormCompleteit would be 1 property for each step in the form. This allows it to scale well but you also then have enough context in the properties to understand the form submission and each step.
stepData1: {
'id': '123',
'onboarding_first_name': 'Joe',
'onboarding_last_name': 'Burrow',
}
stepData2: {
'id': '456',
'onboarding_how_did_you_hear_about_us': 'Search engine'
}
stepData3: {
'id': '789',
'where_selling_currently': ['Etsy', 'Other']
}
Note:
- Amplitude only supports single level of nesting
- Within the nested props, it does support arrays (so solves issue of multi valued step questions like in
stepData3above - Amplitude has a nice feature that you opt into as a property level for “property splitting” which then tells them to split JSON nested and arrays. Nothing for you to do on this, but just info you may want to include in your docs for customers: https://help.amplitude.com/hc/en-us/articles/9623000954907-Cart-analysis-Use-object-arrays-to-drive-behavioral-insights#h_01GGX3KMYSJX6EBW6WHRC7PEMH
Update: I thought of another way to do the event props above which is based on this: https://help.amplitude.com/hc/en-us/articles/9623000954907-Cart-analysis-Use-object-arrays-to-drive-behavioral-insights#h_01H9REGFGH7EQPT5EKKCE865AE
formData: [
{
<step data>
{
]
however the downside of this is taht this approach is meant for more ecommerce situations where the property values between objects in the array are identical. In Feathery’s case each step can have varying # of questions on a page and different types of answers so think this isn’t ideal approach becuase you’d lose the linking between question and answer on a given step. e.g. think of a step where you ask for first and last name, the way that object would be modeled would be odd.
formData: [
{
'id': '123',
fieldId: ['onboarding_first_name', 'onboarding_last_name']
fieldValue: ['Joe', 'Burrow']
},
{
'id': '456',
fieldId: ['onboarding_how_did_you_hear_about_us'],
fieldValue: ['Search engine']
},
{
'id': '789',
fieldId: ['where_selling_currently'],
fieldValue: ['Etsy', 'Other']
}
]
for the 2nd and 3rd question this works because it’s a single question essentially. But for the first one, it’s a bit odd since you can’t specficially get the field value for the first question since they are independent data structures within that object now. Again, this approach is meant for shopping carts, where the field values aren’t meant to cross referenced like survey data.
While “name” questions are a little unusual for this because it’s so open ended and analysis in amplitude (or any product analytics tool won’t be looking at name values). But even if I construct a scenario where we are asking someone “Where did you first see our ad?” and “Where did you last see our ad?”:
formData: [
{
'id': '456',
fieldId: ['where_seen_ads_first', 'where_seen_ads_last'],
fieldValue: ['Search engine', 'Twitter']
},
{
'id': '789',
fieldId: ['another_question],
fieldValue: ['Foo']
}
]
in the above, you have no idea which answer corresponds to each question.
