How do I make Qualtrics to work via Tealium iQ?

Hey there! For anyone looking to scale Qualtrics via Tealium without getting bogged down in manual template edits, the best move is to ditch hardcoding the base_url. Instead, try using a dynamic mapping approach. You can set up a lookup table within Tealium as a data layer variable or extension that maps your specific URL patterns to the right Qualtrics survey IDs and intercept servers.

Using an extension over a standard tag is usually the way to go here because it gives you that extra JavaScript flexibility to handle conditional logic before the tag even fires. This lets you maintain one clean Qualtrics tag that just pulls in whatever embedded data the lookup table spits out. It’s much easier to manage in the long run and keeps your CSP settings a bit more predictable.

If you run into any weird behavior with how the scripts are loading or need someone to take a look at your specific account configuration, it’s worth checking in with the experts. You can get in touch with a specialist by logging into the Customer Success Hub here: https://support-portal.qualtrics.com/. They can dig into the backend if the dynamic mapping isn't firing as expected! 🚀

Thanks ​@Lpena - I managed to get it working via Qualtrics site intercept tag along with a lookup table. I also created a JS extension to add a div element before the lookup table executes. Both before load rule logic. This logic works on one of the smaller Tealium profiles. But does not fetch the qualtrics survey id properly when I run on the bigger profile (probably because of the timing issue).

I will try how you recommended to use JS Extension instead of the tag, if I am not able to achieve it.

​@Lpena - how do i make sure I send the correct survey id? I tried using tealium JS extension, but it is triggering all 3 survey i have in the project. 

It sounds like you're running into a snag with the Tealium JS extension where multiple surveys are firing off at once instead of just the one you need. Usually, this happens when the embedded data or conditions aren't specific enough to tell the surveys apart.

To get this sorted, I’d suggest using a dynamic mapping approach—like a lookup table in Tealium—to map your URL patterns or visitor data directly to specific Qualtrics survey IDs and intercept servers. Instead of hardcoding anything, you can set a unique variable (like "InvokeSurveyID") in your data layer. Then, just configure your Qualtrics intercept to only trigger when it sees a match for that specific ID. Since you're using a JS extension, you've got the flexibility to run that logic before the tag even fires, which helps prevent that "everyone-invited-to-the-party" situation with your surveys. Just double-check that your lookup tables are fully populated before the extension runs so the timing stays synced.

If things still aren't behaving or if you suspect there's a deeper bug in how the extension is interacting with your profile, it’s probably worth having a specialist take a closer look at your specific setup.

Thanks ​@Lpena - The problem was because I was sending survey ID, instead of Intercept ID :’(
Maybe I will raise a support request as this is something specific and might need more support. Thanks again.
But I like the idea of creating a new variable… btw i have a specific migration case, not simple implementation, thus it's a bit more complex than I imagined. Also, it was firing on other pages as well, with using just 1 extension to implement this.