Organize your CRM using custom properties that automatically map responses to creators
What are Properties
Vurvey allows users to create custom attributes, called Properties, to help collect and organize data collected from campaigns. Once a property is set, all responses will automatically map to each creator record. This saves time, but also provides a direct connection to the way that the data has been collected. Let's look at how to start creating properties, and then review some common use cases.
Properties can be created in the Creators tab or directly under campaign questions. We will focus this article on creating them under campaign questions, as I think it provides the most flexible way to get started using properties and data mapping.
For this example, let's imagine that we are launching a vurvey to collect feedback on a new running shoe concept. While the feedback is valuable, we also want to collect information that might help us understand why certain concepts tested better with specific people. We may ask questions about their approach to running, shoes they typically wear, or even their 'Run Frequency" – i.e. how many times a week they go for a run.
Based on this approach, you can generate a question that asks about each topic and create a property custom to this information. Using the dropdown highlighted below, select "Create Property" to pop up a modal to enter the name you want to give this property.
For this example, I named the property "Run Frequency." Click save, and then make sure that it's selected in the same dropdown menu.
You have several choices based on how you want to collect the data. Let's take a look at both and how you might use each.
Append - collects the response, adds a time-stamp, and saves it to the record without deleting or overwriting the previous entries. This is helpful if you want to see if a specific creator's "Run Frequency" changed from 1x/week to Daily over time.
Set - collects the response and saves it to the record, overwriting the existing value. Rather than saving each response collected, the latest entry is the only one available. This is helpful if you want to save a value like a shoe size, which may not change very often.
Once you have the property created, selected in the dropdown menu, and chosen to Append or Set the entries, your campaign is ready to start gathering responses.
Once responses have come into the platform, you can see how data is mapped to each property. Under the Creators section, choose Property, and select the attribute you want to explore. In this case, the Run Frequency was collected as 2-3x/week. You can now select the creator and use the bulk actions menu to do things, like adding them to a specific list.
Common Use Cases
One of the most popular use cases for Properties is to easily organize common demographic or behavior data used for screening and/or customer segmentation. For example, using the property of "Run Frequency" above, we may collect shoe size, preferred environment to run, past footwear models, and even desired features. This could help provide better analysis and match new concepts that align with these attributes. Some additional use cases include:
- Qual or Quant screeners
- Shopper profiles and journey mapping
- Customer segmentation
- Traditional CRM organization
- Custom Distribution Lists
These are just a few ways that Properties can supercharge your workflow. If you have any questions, please drop us a line using the support chat icon.