Say you manage five brand websites and want to run a survey on multiple websites without building five separate projects. The questions are identical everywhere, but you still need to know which response came from which site.<\/p>\n\n\n\n
This is a common setup for companies that run several storefronts, regional pages, or product sites under one brand. The challenge is not the survey itself. It’s keeping the data organized once responses start coming in from different places.<\/p>\n\n\n\n
In this blog, we\u2019ll explore how link tagging, segmentation, and cross-site reporting work together, plus the mistakes that cause data to get mixed up.<\/p>\n\n\n\n\n\n
Running a survey on multiple websites means deploying one identical survey, whether as a popup or a plain link, across several domains while still being able to tell which site each response came from. The survey design stays fixed. Only the source changes.<\/p>\n\n\n\n
Most survey tools handle this by adding a small piece of tracking data to the survey link itself. In QuestionPro, this is done through a survey link<\/a> that can be posted on as many pages as needed, with a hidden variable attached to each version of the link.<\/p>\n\n\n\n Nielsen Norman Group notes<\/a> that intercept surveys, where a popup appears to visitors at specific points on a site, are one of the most common ways researchers gather feedback during an actual site visit. Running that same intercept survey on several domains just adds a tracking layer on top of a familiar method.<\/p>\n\n\n\n You track survey data by website so you can spot which specific site is driving good or bad feedback, not just what the average visitor across all sites thinks. Without a way to separate responses, a strong-performing site and a struggling one get blended into one misleading average.<\/p>\n\n\n\n This matters most when the sites serve different regions, products, or audiences. A 4.2 average satisfaction score sounds fine until you learn one site is scoring 4.8 and another is scoring 2.9.<\/p>\n\n\n\n Per-site tracking also lets you catch problems early. If one domain suddenly shows a drop in scores, you can investigate that site specifically instead of digging through combined data to find the source.<\/p>\n\n\n\n You tag survey links using custom variables by appending a variable and value to the end of the survey URL, so each version of the link carries a label identifying where it was posted. A custom variable is a small piece of data attached to the survey URL that gets saved alongside each response.<\/p>\n\n\n\n Every QuestionPro survey has a base URL that looks something like this:<\/p>\n\n\n https:\/\/www.questionpro.com\/akira\/TakeSurvey?id=xxx<\/p>\n<\/blockquote>\n\n\n To tag it by source, add a variable and value pair after the ID. Replace xxx with your own survey ID; these are examples only and are not live links:<\/p>\n\n\n https:\/\/www.questionpro.com\/akira\/TakeSurvey?id=xxx&custom1=flowers.com Both links open the exact same survey once xxx is replaced with a real ID. The only difference is the value stored in custom1, which tells you the response came from flowers.com or roses.com.<\/p>\n\n\n\n A skincare brand runs the same product feedback survey on its two storefronts. It creates two link variants:<\/p>\n\n\n\n Each visitor who completes the survey has their response tagged automatically, with no extra question needed to ask which site they came from. Full setup steps are covered in the QuestionPro custom variables<\/a> help documentation.<\/p>\n\n\n\n You segment survey results by website by creating a data group for each custom variable value, so the platform filters responses into per-site buckets automatically. This step happens after data collection, in the analysis section of the survey.<\/p>\n\n\n\n In QuestionPro, this is done through system variable grouping:<\/p>\n\n\n\n You can also combine values. If you run the survey across 40 domains and want to view 10 of them as one combined segment, list those 10 values separated by commas when building the group. This gives you a unit of analysis for that cluster without losing the option to break it down further later.<\/p>\n\n\n\n You compare all sites at once with banner table analysis by setting your custom variable as the pivot question, which generates a single report showing every site’s data side by side against the aggregate. A banner table, also called a pivot table, is a report format that shows response data broken out by one variable across every question in the survey.<\/p>\n\n\n\n To run this in QuestionPro:<\/p>\n\n\n\n The output is an Excel file with each site’s results in its own column next to the combined total, so you can scan differences without building separate reports for each domain. Setup details are in the pivot table setup<\/a> help guide.<\/p>\n\n\n\n A franchise group with 10 regional sites runs one customer satisfaction survey across all of them. Individually, each site gets too few responses per month to draw solid conclusions.<\/p>\n\n\n\n By grouping all 10 sites into a single combined segment while keeping each site’s raw data tagged separately, the team gets a reliable regional sample size for monthly reporting. When one location’s scores dip, they can isolate that single site’s data in seconds because the underlying tagging never changed, only the grouping applied on top of it.<\/p>\n\n\n\n This is the practical value of tagging every response at the source. You decide how to slice the data after the fact, without rebuilding anything.<\/p>\n\n\n\n The most common mistake is forgetting to change the custom variable value on each site’s link, which causes every response to get the same source tag regardless of where it was actually collected. Always double-check each link before publishing it.<\/p>\n\n\n\n A few other issues to watch for:<\/p>\n\n\n\n QuestionPro allows up to 255 custom variable<\/a> fields per survey, each storing up to 512 characters, so running dozens of tagged sites at once is rarely a limitation in practice.<\/p>\n\n\n\n One tagged survey across multiple websites is better when the questions are identical, and you want combined reporting alongside per-site views. Separate surveys per site make more sense when each location needs different questions, branching logic, or branding.<\/p>\n\n\n\n If your sites share the same customer journey and you mainly want to compare performance across them, tagging one survey is the simpler and more reliable route.<\/p>\n\n\n\n Custom variables and UTM parameters both attach tracking data to a URL, but they serve different systems. UTM parameters are read by web analytics platforms like Google Analytics to track marketing campaigns, while custom variables are read by the survey platform itself and stored with the response data.<\/p>\n\n\n\n You can technically use both on the same link. The UTM parameters would tell your analytics tool how someone arrived at the page, while the custom variable would tell your survey platform which site they took the survey on. They don’t conflict, but they also don’t share data automatically, so treat them as two separate tagging systems working in parallel.<\/p>\n\n\n\n The setup described here works the same whether you’re tracking two websites or two hundred. The only thing that changes is the number of tagged links you manage.<\/p>\n\n\n\n A simple naming convention for your custom variable values, matching each site’s domain name exactly, saves the most time as the list grows. It also makes handing off reporting to a teammate far easier, since the logic behind each segment is self-explanatory. For teams building this out on QuestionPro’s survey software<\/a>, the tagging and reporting tools described above are available on every plan that supports custom variables.<\/p>\n\n\n\n <\/p>\n\n\n\n\n\tWhy track survey data by website instead of combining it blindly<\/strong><\/h2>\n\n\n\n
How to tag survey links using custom variables<\/strong><\/h2>\n\n\n\n
\n
\n
https:\/\/www.questionpro.com\/akira\/TakeSurvey?id=xxx&custom1=roses.com<\/p>\n<\/blockquote>\n\n\nExample: Tagging links for two websites<\/h3>\n\n\n\n
\n
How to segment survey results by website<\/strong><\/h2>\n\n\n\n
\n
How to compare all sites at once with banner table analysis<\/strong><\/h2>\n\n\n\n
\n
Real-world example: Reading feedback from 10 websites at once<\/strong><\/h2>\n\n\n\n
Common mistakes to avoid when running one survey across websites<\/strong><\/h2>\n\n\n\n
\n
Survey on multiple websites vs. separate surveys per site: Which is better?<\/strong><\/h2>\n\n\n\n
\n \n
\n \n Factor<\/th>\n One survey, multiple sites<\/th>\n Separate survey per site<\/th>\n <\/tr>\n <\/thead>\n \n Setup time<\/td>\n Low, one build<\/td>\n High, one build per site<\/td>\n <\/tr>\n \n Question consistency<\/td>\n Guaranteed<\/td>\n Depends on manual upkeep<\/td>\n <\/tr>\n \n Combined reporting<\/td>\n Built in<\/td>\n Requires manual merging<\/td>\n <\/tr>\n \n Custom questions per site<\/td>\n Not supported<\/td>\n Fully supported<\/td>\n <\/tr>\n \n Best for<\/td>\n Identical feedback across sites<\/td>\n Sites with different needs<\/td>\n <\/tr>\n <\/tbody>\n<\/table>\n\n\n\n Custom variables vs. UTM parameters: What’s the difference?<\/strong><\/h2>\n\n\n\n
Keep the tagging simple as you scale to more sites<\/strong><\/h2>\n\n\n\n