Transaction data and Automations | XM Community
Skip to main content

Hi all, 

I have a setup issue involving transaction data, automations and “holding of contacts” and am a bit out of ideas how to solve it. 

So to give context the following setup: 

  • we have a survey that goes out to all customers who ordered a so called “sample” of a product
  • to ensure that the survey only goes out once the sample is received we want to send out the survey 5 weeks after the transaction “ordered sample” has happened
  • we are currently already creating transactions via the transaction API to store the product ID and product name of the specific interaction that a survey should refer to 

Main issue: 
It seems like there is no way to use transaction data in any automated mails and surveys? So even if we send out the survey through an automation now 5 weeks later, it will pull the recent embedded data into the invite mail and survey introduction and not the data in the transaction. Sending the surveys out via the normal “distribution” is simply not feasible due to the number of surveys to be sent out daily, we really need an automation on this. 

 

Is there any way to improve this? We really need the invite to refer to the correct product as it could happen that within the 5 weeks waiting period customer asks for another product sample and then they would get an invite (worst case) for a sample that they have not even received yet. 

 

I would really appreciate the hive mind ideas on this 🙂 Maybe somebody has run into a similar restriction. 

Best regards, 

@ManuF You can make transactional data available in a distribution and within your survey. They key to achieve this is the so-called transaction batch. You need to generate a transaction batch, add the transaction to it and generate the distribution with the transaction batch added. Some examplary API flow is this: 

Here is the documentation of how to work with transaction batch.

Best
Christian


@chackbusch Thank you so much for the reply!
Would this then also work with our “delay” of 5 weeks - so example: 

We upload transaction batch today with all the info 

We only want to send the distribution to this specific batch 5 weeks later

 

-- does it then still have the correct value in the mail and such? 

Best regards


@ManuF Yes. It will have the details of the transaction available which was added back then. When you add the transaction to the batch, you provide the ID of the transaction. Transactions processed afterwards will not be taken into consideration.

I think you need to check if this works for your automation but if you want to use data of a specific transaction for some distribution, this is the usual way to go.


Leave a Reply