Hello all. We are thinking of leveraging Marketo to generate NPS surveys, but we would like to retain the scoring over time, so we could analyse its progression. We did some tests and built a program for that, but it only retains the latest score. Has anyone been able to achieve the same thing? Any advice would be appreciated. Thank you!
Solved! Go to Solution.
I think you can do this with 2 fields.
- NPS Score (Score field)
- NPS Score Appended (or something similar) (Text Field)
NPS Score would collect the latest score
"NPS Score Appended" would be a text field that would add the latest score and the date to the text file
See how to append data to a field here
https://experienceleague.adobe.com/docs/marketo/using/product-docs/core-marketo-concepts/smart-campa...
Expanding on @derelict_wombat’s correct answer, you can make the history field useful to your data team by using partial JSON format.
When you append to the field, add a comma and then a JSON object in curly brackets {}:
{{lead.History Field}}, { "{{system.DateTime}}" : {{lead.NPS Score}} }
This is a “partial” JSON array because it lacks enclosing square brackets [], but since the format is otherwise good JSON, your team can add those and then parse the value as a true sequential list.
I think you can do this with 2 fields.
- NPS Score (Score field)
- NPS Score Appended (or something similar) (Text Field)
NPS Score would collect the latest score
"NPS Score Appended" would be a text field that would add the latest score and the date to the text file
See how to append data to a field here
https://experienceleague.adobe.com/docs/marketo/using/product-docs/core-marketo-concepts/smart-campa...
Thank you for the suggestion. Will give it a try.
Expanding on @derelict_wombat’s correct answer, you can make the history field useful to your data team by using partial JSON format.
When you append to the field, add a comma and then a JSON object in curly brackets {}:
{{lead.History Field}}, { "{{system.DateTime}}" : {{lead.NPS Score}} }
This is a “partial” JSON array because it lacks enclosing square brackets [], but since the format is otherwise good JSON, your team can add those and then parse the value as a true sequential list.
Thank you for this. Will try implement it.