Location query parameter for center resolution
The Webstore accepts a location query parameter in its URL to identify which center to load when a guest arrives through a marketing or deep link. This is useful when you want to direct guests to a specific center without embedding the center identifier in the URL path itself.
Audience: Marketing teams, administrators, and developers who create links to the Webstore for campaigns, social media, email, or other promotional channels.
On this page
Before you begin
- You must know the center identifier (center ID) for the center you want to target. You can find this in Configuration > Online booking > Online booking settings > Webstore V2 when viewing center-specific settings, or by asking your Zenoti administrator.
- The Webstore must already be configured and accessible. Center resolution using the
locationparameter works only when the Webstore is live. - The
locationparameter is evaluated after path-based and domain-mapping resolution. If the URL already resolves a center through its path structure or a mapped custom domain, thelocationparameter is not required and will not override the primary resolution result.
Note: Changes to Webstore configuration may take up to 30 minutes to propagate due to cache invalidation. If you have recently made configuration changes, allow this window before testing your links.
Steps
Construct a Webstore URL with the location parameter
Start with the base URL of your organization's Webstore (for example,
https://booking.example.com).Append
?location=followed by the center ID for the center you want to load:https://booking.example.com?location=<centerId>Replace
<centerId>with the actual center identifier provided by your Zenoti administrator.Verify the URL by opening it in a browser. The Webstore should initialize in the context of the specified center, displaying that center's services, availability, and pricing.
Use the constructed URL in your marketing materials, email campaigns, social media posts, or deep links.
Worked example: Your organization has two centers. The downtown center has the ID
a1b2c3d4-e5f6-7890-abcd-ef1234567890. To send guests directly to that center's booking flow, your link would be:
https://booking.example.com?location=a1b2c3d4-e5f6-7890-abcd-ef1234567890A guest who arrives via this link sees the downtown center's service catalog, provider availability, and time slots — not the organization's default center selection screen.
Combine with other query parameters
The location parameter can be combined with other Webstore query parameters in a single URL. Use & to append additional parameters after the first:
https://booking.example.com?location=<centerId>&<otherParam>=<value>
For guidance on other query parameters that control what guests see when they arrive (such as pre-selecting a service), see Configure Webstore deep links for marketing campaigns.
Tips
- Use center IDs, not center names. Center names may change over time, but the center ID is a stable identifier. Always use the ID in deep links to avoid broken experiences after a center is renamed.
- Test links before campaign launch. Open the complete URL in an incognito or private browser window to confirm the correct center loads without any cached session data affecting the result.
- Coordinate with your campaign tracking. If you are using UTM parameters to track campaign performance, append them alongside the
locationparameter. For example:?location=<centerId>&utm_source=email&utm_campaign=summer. For details on UTM setup, see Configure Webstore utm tracking. - Confirm the parameter after cache propagation. If you update center settings around the same time as distributing new links, allow up to 30 minutes before testing, as changes are not reflected immediately.
- Review your domain setup if links behave unexpectedly. When a custom domain is mapped to a center, that mapping takes precedence over the
locationparameter. If guests arrive at a custom-domain URL with alocationparameter, the domain mapping governs which center loads. See Configure a custom domain for the Webstore for more information.
Troubleshooting
| Problem | Likely cause | Resolution |
|---|---|---|
| Webstore loads but shows the wrong center | The center ID in the URL is incorrect or belongs to a different organization | Confirm the center ID with your Zenoti administrator and re-test with the corrected value |
| Webstore loads the default center selection screen instead of a specific center | The location parameter value is missing, malformed, or the center is inactive |
Check that the URL contains ?location=<centerId> with a valid, active center ID and no extra spaces or characters |
A custom domain URL ignores the location parameter |
The custom domain is already mapped to a specific center, which takes priority | If you need the parameter to control center resolution, use the organization's generic Webstore URL rather than the center-mapped custom domain |