topic Same question across different surveys in Customer Feedback Tool

Same question across different surveys

NKieran_Hyve — Wed, 24 Jan 2024 16:56:32 GMT

We're about to create around 50 surveys with questions that are repeated across the surveys, these will be used annually or bi-annually, so repeated again the next year. We need to create a property per question per survey.

As the questions are the same, there's a change they'll be mixed up. I've created a group for the properties but when building surveys they don't show the groups in the same way that forms do.

Has anyone found a way round this?

Re: Same question across different surveys

BérangèreL — Thu, 25 Jan 2024 09:35:25 GMT

Hi @NKieran_Hyve,

Great question, that's exactly why the Community is here for!

I'd like to invite a couple of subject matter experts to this conversation: Hi @danmoyle, @beeginman and @OPerek-Clark can you think of a workaround to help @NKieran_Hyve, please?

If anybody else has anything to add and/or share, please feel free to join in the conversation 🙂

Thanks a lot 🌟 and have a lovely day!

Best,
Bérangère

Re: Same question across different surveys

OPerek-Clark — Thu, 25 Jan 2024 15:34:01 GMT

Thanks for tagging me @BérangèreL!

Hi @NKieran_Hyve, I'd recommend editing the Label for the Feedback Submission Properties to have a unique identifier so that allows you to choose the correct one.

Then you should be able to edit the question, placeholder text and/or help text to be the standard question you ask across forms.

I hope this helps!

Re: Same question across different surveys

RubenBurdin — Fri, 05 Sep 2025 04:16:53 GMT

@NKieran_Hyve this is one of those things where HubSpot’s survey tools haven’t really caught up with the property management flexibility you see in forms.

In 2025, the cleaner approach is still to give each recurring survey question its own uniquely labeled property, even if the text of the question repeats. Adding a suffix like “_2025_Q1” or “_Annual” to the internal name helps you avoid collisions, while the end-user only sees the clean question label in the survey. Groups unfortunately don’t surface in the survey builder the way they do in forms, so organization really comes down to consistent naming and a master property spreadsheet on your side.

Another option in 2025 is leaning on custom-coded surveys via the Feedback API, where you can centralize repeated questions against a single property and pass context about which survey instance it came from. That way, the property remains consistent but you still preserve the history of which survey it was tied to.

So while there’s no perfect “reuse” button yet, thinking ahead with naming conventions or using API-based custom feedback collection keeps you safe from mix-ups. Hope that clarifies the landscape in 2025.