Skip to main content
P
PyasSan
July 16, 2025
Solved

Qualtrics survey embedded data mapping in Adobe Analytics

  • July 16, 2025
  • 3 replies
  • 652 views

Hello,

 

We have the Qualtrics survey for our support website and we wanted to integrate the survey with AA. We have followed all the steps from the below link:

https://www.qualtrics.com/support/integrations/adobe-analytics-integration/

We now, are successfully receiving survey responses along with response IDs that are getting captured in a specified variable that we defined. However, we are not able to get the context data/dimension mapping done. For ex: we cannot break the survey by country. language, page, product, etc.

 

Qualtrics Engineering team confirmed that everything appeared to be correctly configured on their end. They advised that the next step would be to contact Adobe Support for further context

 

Please help to understand if we need processing rules that need to be implemented, if yes, how to do that? Also, if there are some other troubleshooting step that we can explore?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by pradnya_balvir

Hi @pyassan ,

 

You're on the right track by getting the response IDs into Adobe Analytics (AA). Now that you're receiving survey responses successfully, the next step: mapping embedded data like country, language, page, product typically requires processing rules or server-side contextData mappings.

 

Some Steps:

 

1. Understand How the Data is Sent

The Qualtrics → Adobe integration uses contextData to send data via the s.t() call to Adobe. This data needs to be mapped in Adobe either via:

  • Processing Rules (most common)

  • OR, Adobe AppMeasurement custom code (if working client-side)

  • OR, Launch/Tags (if using a tag manager)

You likely need processing rules in this case.

 

2. Validate Incoming Context Data

Use Adobe Debugger, Charles Proxy, or Experience Cloud Debugger to verify that the contextData keys (e.g., ctx.language, ctx.country, ctx.pageName) are arriving from Qualtrics in the image request.

Check for:

 

"contextData": {
"qualtrics.responseId": "12345",
"qualtrics.language": "en",
"qualtrics.country": "US",
"qualtrics.page": "support/home"
}

If you're not seeing those keys, the issue may be on the Qualtrics config side.

 

3. Set Up Processing Rules in Adobe Analytics

If the contextData is coming through, you must create processing rules to map them to eVars or props.

 

Example Processing Rule

Go to Report Suite Admin > Processing Rules > Add Rule:

Rule Name: Map Qualtrics Context Data

Condition:
If contextData key "qualtrics.language" exists

Actions:

Set eVar10 = "qualtrics.language"
Set eVar11 = "qualtrics.country"
Set eVar12 = "qualtrics.page"


... (assign each to appropriate variables)

You can also map to classification variables or props if needed for breakdowns.

 

4. Map Dimensions in Reporting

Once data starts flowing into the correct eVars/props, you should be able to:

  • Break survey responses by language, country, page

  • Use responseId as a join key with Qualtrics exports

  • Use Analysis Workspace or Reports to create breakdowns

Use Adobe debugger to verify.

 

5. Troubleshooting Checklist

Checkpoint Notes
Response ID captured Already working 
Context Data keys present Use Adobe Debugger to verify
Processing rules exist Needed to map contextData to eVars/props
Report suite permissions Ensure the correct suite has rules applied
eVars are enabled Check eVar allocation and expiration settings

 

Reach out to Adobe Support only if the contextData is being blocked, stripped, or if rules aren't applying.

 

Hope this information help you.

 

Thanks.

Pradnya

 

3 replies

pradnya_balvir
Community Advisor
pradnya_balvirCommunity AdvisorAccepted solution
Community Advisor
July 16, 2025

Hi @pyassan ,

 

You're on the right track by getting the response IDs into Adobe Analytics (AA). Now that you're receiving survey responses successfully, the next step: mapping embedded data like country, language, page, product typically requires processing rules or server-side contextData mappings.

 

Some Steps:

 

1. Understand How the Data is Sent

The Qualtrics → Adobe integration uses contextData to send data via the s.t() call to Adobe. This data needs to be mapped in Adobe either via:

  • Processing Rules (most common)

  • OR, Adobe AppMeasurement custom code (if working client-side)

  • OR, Launch/Tags (if using a tag manager)

You likely need processing rules in this case.

 

2. Validate Incoming Context Data

Use Adobe Debugger, Charles Proxy, or Experience Cloud Debugger to verify that the contextData keys (e.g., ctx.language, ctx.country, ctx.pageName) are arriving from Qualtrics in the image request.

Check for:

 

"contextData": {
"qualtrics.responseId": "12345",
"qualtrics.language": "en",
"qualtrics.country": "US",
"qualtrics.page": "support/home"
}

If you're not seeing those keys, the issue may be on the Qualtrics config side.

 

3. Set Up Processing Rules in Adobe Analytics

If the contextData is coming through, you must create processing rules to map them to eVars or props.

 

Example Processing Rule

Go to Report Suite Admin > Processing Rules > Add Rule:

Rule Name: Map Qualtrics Context Data

Condition:
If contextData key "qualtrics.language" exists

Actions:

Set eVar10 = "qualtrics.language"
Set eVar11 = "qualtrics.country"
Set eVar12 = "qualtrics.page"


... (assign each to appropriate variables)

You can also map to classification variables or props if needed for breakdowns.

 

4. Map Dimensions in Reporting

Once data starts flowing into the correct eVars/props, you should be able to:

  • Break survey responses by language, country, page

  • Use responseId as a join key with Qualtrics exports

  • Use Analysis Workspace or Reports to create breakdowns

Use Adobe debugger to verify.

 

5. Troubleshooting Checklist

Checkpoint Notes
Response ID captured Already working 
Context Data keys present Use Adobe Debugger to verify
Processing rules exist Needed to map contextData to eVars/props
Report suite permissions Ensure the correct suite has rules applied
eVars are enabled Check eVar allocation and expiration settings

 

Reach out to Adobe Support only if the contextData is being blocked, stripped, or if rules aren't applying.

 

Hope this information help you.

 

Thanks.

Pradnya

 

Vinay_Chauhan
Community Advisor and Adobe Champion
Vinay_ChauhanCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
July 16, 2025

Hi @pyassan 

You're almost there, if you’re already getting the response ID into Adobe Analytics, that means the Qualtrics integration is working at a basic level. What’s likely missing is mapping the additional embedded fields (like country, language, page, etc.) into reportable variables within Adobe.

You can fix it using following steps -

Step 1: Confirm Context Data is Being Sent

Use the Adobe Experience Platform Debugger (or Charles/Fiddler) to check if Qualtrics is actually sending the additional fields you need.

Look for something like this in the network request -

"contextData": {
"qualtrics.responseId": "abc123",
"qualtrics.country": "US",
"qualtrics.language": "en",
"qualtrics.page": "support-home"
}

If you don’t see the keys (e.g. qualtrics.country, qualtrics.language), the issue may still be on the Qualtrics config side.


Step 2: Create Processing Rules in Adobe Analytics

Assuming the context data is coming through, the next step is mapping it to your report suite variables (eVars or props).

Go to:
Admin > Report Suites > [Your Suite] > Processing Rules

Set up a rule like this:

  • Condition: If contextData key qualtrics.country exists

  • Actions:

    • Set eVar10 =  qualtrics.country

    • Set eVar11 =  qualtrics.language

    • Set eVar12 = qualtrics.page

Use any eVars/props that are free in your setup.

Make sure the eVars you're mapping to -

  • Are enabled in the report suite settings

  • Have the correct allocation (e.g., "Most Recent") and expiration (e.g., "Visit") settings

 

Step 3: Validate and Use in Reports

Once the rules are active -

  • Give it a few hours for data to populate

  • Then check Analysis Workspace to break down your survey responses by country, page, language, etc.

  • You can also use the responseID to join the survey results offline (if needed)

 

hope this works for you!








N
nitesh__anwani
Level 3
July 20, 2025

Hi @pyassan ,

I don't have much expertise with Qualtrics, but I reviewed the integration documentation you shared to better understand how the data is sent from Qualtrics to Adobe Analytics.

From what I understand, the data is sent from the Qualtrics server to the Adobe Analytics tracking server—not directly from the user’s device completing the survey. So, this is essentially a server-to-server integration.

According to the documentation, the data payload sent from Qualtrics to the Adobe tracking server includes only the Response ID and the list variable containing the survey responses.

The dimensions you're referring to—such as country, language, page, product, etc.—are not included in the payload. These values are also not persisted, because the response data is sent from the Qualtrics server rather than the user’s browser/device, so Visitor Id based eVar persistence does not apply in this scenario.

I noticed that the documentation briefly mentions options for adding Embedded Data to surveys, which could potentially be sent to Adobe. However, the details provided are limited. You might want to check with Qualtrics Support on how Embedded Data can be configured in your workflow. If it's possible to send this data as context variables to Adobe, you could then map those context variables to Adobe variables using processing rules.

Aside from Embedded Data, the payload from Qualtrics to Adobe is quite limited—essentially just the Response ID and the response list variable. So without leveraging Embedded Data, it's unlikely you'll be able to capture all the other required variables.

 

Thanks,

Nitesh

Terms & ConditionsAccessibility statement

Loading footer...