As your subscribers opt-in, you can use this opportunity to collect preferences about messaging, collect personal information and ask any questions that’ll help you segment your audience for future campaigns.
Tags vs. Custom Properties: Collecting Customer Data
Both tags and custom properties are powerful tools for collecting data about your customers. Understanding the ideal use case for each will help you implement them effectively.
When to Use Tags
If your primary goal is to segment an audience, tags are the recommended tool. Tags make it significantly easier and quicker to create and manage customer segments for targeted campaigns and communication.
When to Use Custom Properties
Custom properties are ideal for saving unique, specific data points about a customer. Use them when you need to generate detailed reports or sync information with external systems, such as a CRM.
Using Tags and Custom Properties Together
For the most robust data strategy, we recommend using both tags and custom properties in your workflows. This combined approach allows you to leverage the easy segmentation of tags while capturing the detailed, unique information that custom properties provide, leading to more powerful and efficient customer management.
Collecting Customer Data
Via tags
To store responses to quick reply buttons or lists:
Create a flow and add a Send message node
Add quick reply buttons or a list
Add a Manage tags node off each response
Now a tag will be applied to the contact’s profile once they answer.
Via custom properties
Watch
In our March Product Release webinar, Grace showed us how to store custom properties in Journeys.
To store free-text responses (i.e. what your customer messages you back) like email;
Create a flow and add a Send message node
Click the node to Edit
Go to ⚙️ → Customer response settings ****and toggle ON Store customer response
Select Store in charles contact property and make sure Email is selected
Now the customer’s response will be store as a Custom properties
Note: The first response from your customer is stored (no matter the value) and the flow will only continue once your customer has responded.