Overview
This guide walks you through configuring survey tracking, or self-reported attribution, in your Sona Contact Journey settings. You will learn how to connect survey data sources, map fields, and set up custom attributes to track survey and self-reported attribution across your contact journey. These touchpoints are automatically added to the Profile 360 buyer journey, giving you a complete view of each customer's interactions.
When to use Survey tracking
Integrating survey responses into contact journey analytics.
Tracking survey completion rates and response data.
Connecting external survey platforms or reports to Sona.
Creating comprehensive contact engagement measurement including survey touchpoints.
Prerequisites:
Admin or workspace settings access in Sona.
Survey data available through connected platforms or reports.
Step 1: access Survey configuration
Navigate to Contact Journey settings: go to Workspace Settings in the left sidebar, then click the Contact Journey tab in the main area.
Select the Survey tab: click the Survey tab from the horizontal menu. You will see the survey configuration interface with touchpoint information.
Step 2: configure survey data source
Select data source type: in the Source section, click the dropdown and choose your preferred data source method for survey information.
Choose report type: click the "Select Report" dropdown to see available options.
Step 3: configure field mapping
In the Mapping section, configure how survey data connects to your analytics. Map survey fields to the appropriate columns in your data structure. This ensures survey responses appear correctly in your contact journey.
Step 4: configure Survey attributes
In the Attributes List section, click + Add to create new survey attributes. Configure the following for each attribute:
Field: the survey data field you want to track.
Filter: conditions for when this attribute applies.
Value/Transformation: how the data should be processed or displayed.
Name: a clear, descriptive name for the attribute.
Add all relevant survey attributes that align with your tracking goals. This step brings together all your survey data for comprehensive journey tracking.
Key concepts and best practices
Core concepts:
Survey Touchpoints: points in the contact journey where survey interactions occur, timestamped relative to other journey events.
Data Source Integration: the method by which survey responses flow into your Sona analytics.
Attribute Mapping: connecting specific survey questions or responses to trackable contact attributes.
Journey Context: how survey data fits into the broader contact experience timeline.
Best practices:
Touchpoint Timing: the system automatically adds survey touchpoints with proper timestamps, so ensure your survey timing aligns with your journey mapping goals.
Comprehensive Attribute Tracking: map all meaningful survey responses, not just completion status.
Data Source Selection: choose the data source that best matches your survey platform and workflow.
Clear Naming: use descriptive names for attributes that will be easily understood in reports.
FAQs
What does Survey tracking add to the Contact Journey?
What does Survey tracking add to the Contact Journey?
Survey tracking connects survey responses and self-reported attribution data to a contact's journey. Once configured, survey interactions appear automatically as touchpoints on the Profile 360 buyer journey timeline, timestamped alongside other journey events.
Why do I need to map survey fields?
Why do I need to map survey fields?
Field mapping connects your survey platform's data columns to Sona's Contact Journey structure, ensuring survey responses appear correctly against the right contact and touchpoint. Without accurate mapping, survey data may not populate correctly in the buyer journey.
Should I track every survey response as an attribute?
Should I track every survey response as an attribute?
Map all meaningful survey responses, not just completion status, so you capture the full context of what a contact reported. Use clear, descriptive attribute names so your team can easily understand each one when reviewing reports.