Loading...
  • Customer Experience
    Customer Experience
  • Employee Experience
    Employee Experience
  • Brand Experience
    Brand Experience
  • Product Experience
    Product Experience
  • Core XM
    Core XM

Step 2: Creating a Website Feedback Project

What's on This Page:


Was this helpful?


This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

The feedback you submit here is used only to help improve this page.

That’s great! Thank you for your feedback!

Thank you for your feedback!


Once you have built your survey, the next step is to create a new Website Feedback Project in your account. Every Website Feedback project can consist of multiple Creatives and Intercepts.
Creating a Website Feedback project from the Projects page

One vs. Multiple Website Feedback Projects

Every time you create a project, you need to implement that new project’s deployment code separately on your website. Since one project can contain many interconnected Creatives and Intercepts, using just one project to house them all is a great way to reduce the number of times you update your site code. In using just one or very few projects, you ensure that every time you activate or publish changes, these go straight to your website without additional action, since you added the code when you first created the project.

Generally, it’s best to create multiple Website Feedback projects when you plan to implement Intercepts across different websites. For example, you may want to keep feedback and redirects meant for your Support site separate from your Marketing site.

Qtip: It’s also good to separate any content you don’t want to get mixed up. If both your Marketing department and HR team are going to be using the Website Feedback platform, it would be a good idea to create a “Marketing” project and a separate “HR” project. This way, you can easily separate your Creatives and Intercepts.

Adding Project Deployment Code to Your Website

Once you’ve created your Website Feedback project, it’s time to retrieve the Project Deployment Code so you can put it on your website.

The Deployment section. Beneath the navigation bars are Intercept Versions to select from, then Sampling options, then a large field with Javascript code inside

Implementing your code will require that you have access to your website’s HTML code. If you do not have access, then a member of your IT team will have to implement the code for you. You will want to send them the entire snippet of code starting with <!–BEGIN QUALTRICS WEBSITE FEEDBACK SNIPPET–> and ending with <!–END WEBSITE FEEDBACK SNIPPET–>.

We recommend that the Project Deployment Code is placed within the global header or global footer of your site. If you have Intercepts that are only supposed to appear on certain pages, use Current URL conditions on the appropriate Action Sets.

Qtip: If you are unsure whether your IT Team has placed the code on your page, you can right-click on your site and choose “View Page Source.” If they have placed the code within the header or footer, you’ll see it within the Page Source HTML. Implementing your code through a Tag Manager may impact whether you can use this method to see if the code is on your page. Check out our Using Tag Managers page for more information.

Do I ever have to replace my Project Deployment Code?

You will only have to add Project Deployment Code to your website once. After that, you will not have to edit the code, even if you are planning on adding or removing elements. The only exception would if you decide you want to add Sampling to your Deployment Code.

Once Project Deployment Code is on your site, changes published within the project will instantly appear on your site. For example, you can deactivate Intercepts you are no longer using to instantly remove them from your site without changing the code.

If you have created multiple projects, you will want to find and implement Project Deployment Code for each project on your site.

Important Considerations

Here are some questions you should ask yourself before placing code. For each scenario, we explain the best way to proceed.

Do you use a Tag Manager?

Code can be added through a Tag Manager, rather than directly to your website. Rather than copying and sending the code to your IT Team, you can paste it into a Tag Manager instead. For more information, see the Tag Managers FAQ and Using Tag Managers page.

Are you integrating with any other platforms?

Typically, your IT teams know the best ways to integrate with Adobe Analytics and other data platforms, or how to capture other data from Javascript or cookies directly from the webpage. Get their recommendations on best ways to use data from the website. You can then enhance your data set using Embedded Data to capture these values.

How long does it take to get code added to the website?

Each company has a different code release cycle. Because the Project Deployment Code is necessary for any Website App Feedback Project to work on your website, the sooner you can add the code the better. Typically, we recommend communicating with your IT teams to add the code while you work on building out the content. You don’t need to wait for code to be added to your website to start designing Creatives or Intercepts, because Website Feedback projects won’t go live until the Intercepts you create are activated. If code gets added before the content is built, it’ll just run in the background and not show anything until content is activated within Qualtrics. This gives you time to wait for your IT team’s code release cycle, if need be.