Map widget: can I display branch name/key instead of latitude/longitude as the point label? | Experience Community
Skip to main content

Map widget: can I display branch name/key instead of latitude/longitude as the point label?

  • April 8, 2026
  • 3 replies
  • 71 views

Hi everyone,

We are configuring the Map widget in Qualtrics and we have a question about the location label displayed for each point.

Right now, the widget asks us for a location field using the physical point coordinates (latitude/longitude). When we load the coordinates, the map places the points correctly, but the labels shown for those points are the coordinates themselves.

What we need is for the label to display the branch name or branch key/code instead of the coordinates.

Our challenge is scale: we have more than 1,000 physical locations, so using manual edit mapping is not a viable option.

Has anyone configured the Map widget so that:

  1. the point location is based on latitude/longitude, but
  2. the visible label shows another field, such as branch name or branch ID/key?

Is there a native way to do this in Qualtrics, or would it require a workaround such as embedded data transformation, custom mapping, or custom code?

Any guidance, examples, or best practices would be greatly appreciated.

Thanks in advance.

3 replies

Mishraji
Level 4 ●●●●
Forum|alt.badge.img+18
  • Level 4 ●●●●
  • April 9, 2026

nikamshubham73
Level 3 ●●●
Forum|alt.badge.img+4
  • Level 3 ●●●
  • April 13, 2026

Hi ​@Oski,

I have worked on a similar requirement where we mapped two regions - EMEA and APAC, on the CX Widget using different latitude and longitude values. We utilized Qualtrics Bucketing to assign them into 2 new variables. The only challenge I foresee here is that, since you mentioned 1,000 physical locations, bucketing them may be time-consuming. However, once completed, only the two regions will be displayed on the CX Widget. Hope this helps!


Forum|alt.badge.img+11
  • Level 4 ●●●●
  • July 29, 2026

Hi ​@Oski 

I agree with ​​nikamshubham73​ , whichever way you look at it you are going to have to type the 1000 locations in somewhere, unless you already have this in a file already or there is some logic that can refer to multiple inputs to help you narrow it down.  The data could either be loaded into the location table, imported data project or even a directory.

 

I’ve done something similar but on a smaller scale and used a lookup method in the survey flow using a webservice task for when a survey is run.  Based on the location it will look up information (extra details about the location) and record it with the response in question.  This is not dynamic though and so if you want this to be dynamic a data model approach is better but both options still need the data to be made available in the first place but if it is available publicly elsewhere, then you could use a webservice (effectively an API call) to retrieve it thus saving you having to create the 1000’s of fields.

 

Hope that gives you some food for thought