I previously used Dynamics 365 Outbound Marketing to send Customer Voice Surveys via Customer Journeys, attaching surveys directly in the email element. This allowed me to view respondents' names (contacts) in the survey reports.
However, after transitioning to Customer Insights - Real-time Journeys, I can no longer find a way to replicate this process. Surveys are now sent, but respondents are only identified as "Marketing respondents" in the reports, without their contact names.
Could the professionals please guide me on how to track respondents' names in Customer Insights - Real-time Journeys, as I was able to do in Outbound Marketing?
Hi CU05091629-0, Yes, this can be accomplished by combining a Power Automate flow, a custom trigger, and a Real-time Journey with an email.
First create a custom trigger with some attributes you consider important. Consider the invitation link as one attribute. Then create a Power Automate flow. Consider thinking about how that flow will be triggered, this should make sense with your overall process. Use the “Create an invitation” action that you can find under Customer Voice, select the correct project and survey, and make sure to fill in the contact information in the attributes. At the end of the flow, use the “Perform an unbound action” step under Dataverse to fire your custom trigger in Real-time Marketing. In this step, you’ll need to pass the right values, with the most important ones being the profileId and the invitation link generated from the previous action. That invitation link is what you’ll embed in your marketing email. Finally, create your email and journey in Real-time Marketing, using the custom trigger as the entry point. This way, your contacts receive personalized Customer Voice invitations through Real-time Journeys, and the survey responses are tied back to the actual contacts rather than showing as generic “Marketing respondents.”
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.