Field Mapping Issues
Overview
Ensuring your custom recorder questions accurately map to your analysis fields is crucial for getting meaningful insights from your customer feedback. When these fields don't align, your data can become messy, making it difficult to analyze trends or identify areas for improvement.
This guide helps you quickly identify and fix common mapping problems, so you can trust the data you see in your reports and make informed decisions with confidence.
How It Works
When you set up your custom recorder, you ask questions to gather specific information from your users. Each question needs to be linked to a corresponding field in your analysis system. If this link is broken or incorrect, the data from that question won't appear in the right place, or at all.
Step-By-Step Fixes
Follow these steps to resolve common field mapping issues:
Check Field Types: Make sure the type of data you're asking for matches the type of field it's being sent to. For example, a question asking for a date should be mapped to a 'Date' field, not a 'Text' field.
Unique Names: Avoid using the exact same name for multiple questions. This can confuse the system when trying to map responses.
Field IDs: Open your Recorder settings and carefully check the
fieldIdfor each question. This ID must exactly match the corresponding field in your internal database or CRM.Hidden Fields: If you're using hidden fields, ensure there aren't duplicates that might be overriding the visible fields you intend to use.
Pro Tips
To make mapping easier and ensure data consistency:
Use 'Radio Buttons' or 'Dropdowns' for questions instead of 'Text' inputs. This helps standardize the answers, making them easier to map correctly.
Troubleshooting
If you notice data is missing from your analysis:
Data Missing: Double-check if the user actually filled out the optional field in the recorder.
Next Steps
Ready to ensure your data is mapping correctly?
Login to your account and navigate to your Custom Recorder settings.
Review your questions and their corresponding field IDs, paying close attention to data types.
Test your recorder with a few submissions to confirm data is appearing as expected in your analysis.
Need further assistance? Contact our support team or explore our other help articles.