Since realizing engagements (surveys included) within PX can be launched by Query Parameters (<url>?key=value&key2=value2), i’ve found this as an effective way to drop in hyperlinks and custom buttons to launch between engagements (such as chaining engagements back-to-back in a series). That said, I’d like to see the ability for PX surveys to capture additional query parameters (preferably by defining the extra/valid parameters when creating the survey).
I’d like to use this functionality specifically in the following way:
- Feedback mechanism for In-App Guides (many-to-1): Include a link or custom button to launch the boolean survey (?guide=survey1) but be able to extend this by adding an additional hidden field to the survey (such as ?guide=survey1&previous=cookiesguide1) which tells me which guide triggered the survey. This way I don’t need feedback surveys 1:1 for our 100+ guides.
- Capturing consistent feedback in-app unrelated to guides (say CES or Boolean), but allow developers to sprinkle the feedback hyperlink/button in the UI where they want to capture it without the need to create new CES.
That said, I would still like to be able to do some filtering on the feedback based on that extra/hidden defined query parameter.
Alternatively, If a single survey is tied to multiple feature/modules by audience rules, could we capture the feature/module that triggered the survey as a filterable parameter in the survey results? Then I could *hopefully* view the score calculated based on all the responses, or just the responses tied to specific features (or multiple features rolled up to a module view).
