after a bit of testing, just typing in the litteral name of the transactional data field, so it is ${e://Field/TransactionFieldTest}, does apparently seem to work.
Also on the survey flow, just typing in the litteral name of the field, seems to do the trick.
I had hoped to be able to select these fields via a dropdown like we can often do with the Embedded Data. Or a function on the Survey Flow like the "add from contacts" but then "add from transaction batch". Just to avoid typing the fields, as that leads ever-so-often to typing errors.
Hi JoycaV !
Thank you for sharing. So, does transaccional data work similar to Embedded data?
I am trying to setup on the survey flow but it does not work.
Could you help me please? thanks
JoycaV
First of all millions of thanks for your time and this valuable information. I'll check what I did wrong.
I´ve followed all the step but in my case it doesn´t work...
https://community.qualtrics.com/XMcommunity/discussion/comment/44591#Comment_44591Then I suggest you contact Qualtrics support, they can look into your system to find out what's going wrong.
JoycaV
Can you explain how did you do the distribution to the Transaction Batch that you made? I think I have a problem there, because normally I go to the survey and I select the contact and for that reason it doesn´t work. Thanks in advance!
JoycaV I have found my error. When you go to distributions and you have to select your group of people to whom you want to send, you must select all the transactional groups and not the list of contacts that was created. And that's why it didn't work for me.
Hi @JoycaV,
great thread, it helped us a lot already. Nonetheless, I still have a question about your solution:
Did you import your transactional data as [Transaction information] or as [Embedded data] in the respective UI? (Did you use the UI? There’s also an API endpoint for this...)
We can (manually) pipe transactional data into distribution e-mails or surveys only if we choose [Embedded data]. Since we cannot rule out many and frequent transactions for certain contacts, this is potentially problematic (for two reasons: contact-level ED might be overwritten in the meantime so that the text piped in migth change from the invite e-mail to the survey session; further, there is a limit of 100 ED fields per contact).
To state it explicity: When we save the field “TransactionDescription” as [Transaction information], we can’t (at the moment) pipe it in anywhere, not even with the manual process you described.
Hi @cpschroeder
I mapped my data as transactional data. (I used the UI, not the API)
It doesn’t matter if the field is embedded data or transactional data. They can all be used as piped texts within emails, surveys, etc.
What is important though, that in order for the “match” to work, is that your distribution is sent to the transaction group, like Alea explained before. Otherwise the survey cannot know from which transaction it needs to fetch the value for that field.
Hi @cpschroeder
I mapped my data as transactional data. (I used the UI, not the API)
It doesn’t matter if the field is embedded data or transactional data. They can all be used as piped texts within emails, surveys, etc.
What is important though, that in order for the “match” to work, is that your distribution is sent to the transaction group, like Alea explained before. Otherwise the survey cannot know from which transaction it needs to fetch the value for that field.
Ahh, thanks a lot. I looked at that again really closely and only then realized that distributing directly out of the directory seems to be the only way to do this at the moment (whereas distributing out of the survey, which we are usually doing, does not allow choosing a transaction group).
