@Pavel Do I need to setup the distributionId in embedded data before export the response even If I using and API export? Or there's a way to bring that directly using the API call? The Get Distribution API call would need to know the destributionId, and the only way to get in the response export output it is to set it in survey flow :(What @Nam Nguyen suggested would also work, but we need a more real-time way to update responses with their respective distribution metadata, and the only way to do it is either through workflows with multiple web service tasks, or externally, albeit with a minor delay.In our use case, we do it with a Python script that runs on a Cron schedule every X minutes, extracts new responses with continuation token, gets their respective distribution metadata, and then updates them again with update response API.
We set distributionId in embedded data, and then after exporting responses, run Get Distribution requests for each responseId value on each distributionId.
If you use SSO, why not map whatever AD group (or some other attribute) that grants Qualtrics access to a desired UT? That way, the first time they login, their default UT will be automatically changed to the desired one.See Mapping Options in SSO settings, and related documentation.
Rod_Pestell actually this was solved a while back. Not quite sure when, but I've had a number of JSON event-based actions setup with XMD tasks which add transactions, totalling a few thousand distributions per day, and it's been working flawlessly.Well, the transaction part has been working flawlessly, but JSON events themselves are still a pain to work with, and I hate having to create 2 separate XMD tasks in each action only to be able to update both transactional data and attributes.
The Response Export Automation feature is excellent! A few questions/comments about it:How does it determine the date parameter for export - End Date or Recorded date?I see that it can only handle new responses - what about responses that have been changed/updated? Right now the only way to reliably export them is either manually or via API. Are there any plans to expand the Response Export Automations or Actions (Survey Response event - Response Type - Updated) functionality to also cover updated responses?The automations cannot be triggered more than once per day - are there any plans to increase the frequency?Scheduling always shows AM/PM times, regardless of one's language setting. Please add support for 24H times.Export Options UI displays two sets of scroll barsAs a separate note, I'm a little surprised that a feature like this was just released without first going through at least one round of Qualtrics Preview program...
> @KatharineS said: > @Pavel @MsIreen I apologize for the confusion here - sounds like you have some pretty specific setups in this case. I’d recommend getting in touch with our support team here so they can better dig into your specific case with you. I've had several discussions about our use case with EPS, and the conclusion was that there is no solution. There is a complex workaround involving Automations, but it's not really relevant for us since we have hundreds of thousands of distributions every month via API. While not quite the same, I think @MsIreen and I have somewhat similar use cases, and I wouldn't go as far as calling them "pretty specific", because any large-volume transactional contact/call center CX programme will face the same issues. The simple truth is, Research Core and XMD were just not designed to handle the demands of large enterprises. That's why I initially started to question the new transactions functionality in the XM Directory task - I just can'
OK, so consider the following scenario: 1. John calls Qualtrics at 12:00 and Speaks with Jane in Sales. 2. An XMD task is triggered through a JSON event which adds the call's metadata (including Jane's name) to John's contact in XMD as a transaction, and a survey is distributed. 3. John calls Qualtrics again at 13:00, and speaks with Susan in Support. 4. Another XMD task is triggered through a JSON event which adds the 2nd call's metadata to John's contact in XMD as a transaction, but no new survey is distributed due to contact frequency settings. 5. John finally clicks on the survey link at 13:15, and completes the survey. If call metadata is set in the ED block in the Survey Flow, which transaction data will end up in the response as embedded data - the 1st call with Jane or the 2nd call with Susan? Unless Survey Flow and XMD functionality has fundamentally changed recently, it will be Susan's data, even through the survey was originally distributed for a call with Jane.
> @KatharineS said: > @Pavel & @MsIreen The XM Directory task can be used to add transactional data to a contact. Even if you choose to distribute a survey, you can add a contact and update transactional data. (Apologies if I'm misunderstanding the question!) Yes, you misunderstand. A survey is distributed to a contact as a whole, not the transaction that was added with the XMD task. Between when the survey is distributed and when the respondent clicks on the survey link, the contact's attributes can be overwritten with new data many times, and survey flow will always set ED from contact at the time the link is clicked, by which time the original data which triggered a distribution and contact creation is already outdated. The only solution would be to be able to distribute a survey to a transaction, and/or set ED from a particular transaction, rather than the contact. The current implementation makes Transaction functionality in the XMD task effectively useless, since it just
Correct me if I'm wrong, but it's still not possible to distribute a survey to a particular transaction? The risk with the way XMD and ED currently works is that attributes on a contact in XMD can change after a survey has been distributed, but before the respondent actually clicks the survey link. This is especially important for high-volume call center transactional CX programs, where attributes on contacts in XMD can be overwritten many times throughout one day, but contact frequency settings prevent multiple surveys from being distributed.
Happening to my users as well. SSO makes dealing with this easier, but it's still annoying for me as brand admin to have to reopen dashboards I've been monitoring before getting logged out for the umpteenth time during the day...
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
