Transactional vs Embedded Data in Contact Import Automations

AxelSAxelS ArgentinaCommunity Member Guru ✭✭

Transactional vs Embedded Data in Contact Import Automations

Is there any advantage to setting a field as Embedded Data instead of as Transactional in the "Data Field Mapping" part? As far as I saw, from the Survey Flow you can add Transactional Data as if it were Embedded Data fields, so it doesn't make a difference in that aspect.

Tagged:

Answers

  • MattBroffman_OrlandoMattBroffman_Orlando OrlandoCommunity Member Guru ✭✭

    The advantage to transactional data is how it's tied to the contact. Each transaction can add more and more data to the contact. For example

    Transaction 1:

    • Date: 1/1/19
    • Service: Purchase
    • Store: 123

    Transaction 2:

    • Date: 1/15/19
    • Service: Return
    • Store: 456

    Both of those transactions will be on the contact record. It's not easy to retrieve transaction data as it is embedded data but it's there. If you do embedded data all you will have is:

    • Date: 1/15/19
    • Service: Return
    • Store: 456

    I assume there will be more features using the transaction data in the future. It would be nice for example on the Return survey to be able to pull in the original store it was purchased at.

    We're currently adding transaction data as embedded data because it's not available to add in the Actions tab.

    However, I think a good way to think about it is that transaction data should be tied to an interaction you have with a contact whereas embedded data is tied to the contact themselves and if it changes there is little value in the old data (e.g. customer ID, Favorite Store, Number of Transactions, etc.)

    That's how we've been trying to think about it.

  • AxelSAxelS ArgentinaCommunity Member Guru ✭✭
    edited January 15

    The advantage to transactional data is how it's tied to the contact. Each transaction can add more and more data to the contact. For example

    Transaction 1:

    • Date: 1/1/19
    • Service: Purchase
    • Store: 123

    Transaction 2:

    • Date: 1/15/19
    • Service: Return
    • Store: 456

    Both of those transactions will be on the contact record. It's not easy to retrieve transaction data as it is embedded data but it's there. If you do embedded data all you will have is:

    • Date: 1/15/19
    • Service: Return
    • Store: 456

    I assume there will be more features using the transaction data in the future. It would be nice for example on the Return survey to be able to pull in the original store it was purchased at.

    But does it have any advantage the other way around? I mean setting them as embedded data instead of transactional.

    We're currently adding transaction data as embedded data because it's not available to add in the Actions tab.

    But if you add it in the survey flow, then you can add it in Actions, right? Although you would have only the last transaction.

  • MattBroffman_OrlandoMattBroffman_Orlando OrlandoCommunity Member Guru ✭✭

    Embedded data has been around in qualtrics longer as is available in more features.


    Yes you can set in the survey. In our case we have a web service (think user fills out a form not in qualtrics) that is what triggers that action and then sends out a survey. Right now there is no way to add the data in the from as a transaction so we have to add as embedded data.


    Another example I could think of is if you used an authenticator, you could then add contact embedded data but not transaction data.

Sign In to Comment