When will we have comprehensive display logic for app intercepts? | XM Community
Skip to main content

I am working on an intercept survey for our mobile app and I cannot believe how limited the display logic criteria is for these projects. Basic criteria like time spent on page or how many times a page has been viewed has to be custom built on the backend and then referenced as 'custom property'. When I spoke with a support team member I was told that the feature is not designed to be used this way (e.g., with custom property workarounds), but I don't see how it is used any other way? Qualtrics' web intercepts allow so much customization when it comes to display logic and I don't understand why there isn't parity for App intercepts.
When can we expect to see expanded display logic for app intercepts?

emaenner ,
Having implemented a few app intercepts on a couple of different survey platforms, I can tell you that traditionally has been custom work. Using a companies SDK envelop is what usually has to happen with extensive work from an engineering team. This is a perfect example of what Qualtrics has done so well in the past. Take what usually requires dev time and turn it into something user friendly, turn-key simple. I would recommend you put this idea in the "Product Ideas" section of the XM Community. On the main page of the XM Community if you go to "Innovate" and then to "Website / App Feedback". You can then recommend this to Qualtrics there, and if you do, let me know and I'll Upvote it! I'd love to see more "in-app" survey options!


ThomasW_IronMountain - yes I have created a product idea for this here!
I appreciate your thoughts, it seems like the current in-app survey options on Qualtrics represent an in-between state: they have relieved some of the dev work required for these kinds of projects but not all. I am eager to relieve our engineers of additional work in order to get the targeting options I need for our research, but based on the conversations I've had with Qualtrics support I'm afraid it's not possible at the moment.
If you have any examples of targeting workarounds you've have used in your work I'd love to hear them!


Leave a Reply