ZenotiHelp

Configure Webstore deep links for marketing campaigns

ZTZenoti Docs Team Updated October 19, 2026 8 min readHow-to

Send guests directly to a specific service, category, package, membership, fitness class, or provider on your Webstore by using deep-link URLs in your marketing campaigns. Deep links reduce navigation friction between an ad click and the booking β€” every removed click typically improves conversion.

Audience: Marketing administrators and Webstore administrators who build campaign URLs for email, paid search, and social media promotions.


On this page


Before you begin

Note: For conceptual background on the Webstore, see Webstore Overview.

  • Identify the entity (service, category, day package, series package, membership, fitness class, or provider) you want to promote.
  • Have your center ID ready. The center ID appears in the URL of center-specific admin pages in the Zenoti admin portal.
  • For series packages and memberships, you must obtain the Version ID of the entity β€” not the Package ID or Membership ID. See the critical note below.
  • For provider deep links, you must obtain the provider identifier by contacting Zenoti Support β€” provider identifiers are not visible in the admin interface.
  • For category deep links, you need the category identifier. Categories are managed at the organization level. If you have only center-level access, ask an administrator with organization-level access for it.
  • Confirm that the services, packages, memberships, or classes you plan to link to are marked Available Online in the Zenoti admin. Entities not marked Available Online will not display correctly when a guest follows the deep link.

URL formats

The following table lists the supported deep-link URL formats. Append these paths to your Webstore's base URL (for example, https://booking.yourbrand.com). The Example column shows each format as a complete, working-shape URL built from that sample base URL and the sample center identifier 12345. The identifier values in the examples are illustrative β€” replace the base URL, the center identifier, and the entity identifier with your own values.

Important: Service and category deep links must include the center identifier segment in the URL path. A link that omits the center identifier segment silently lands the guest on the generic booking page rather than the intended service or category.

Entity URL format Example Notes
Service /services/<centerId>?serviceid=<service_id> https://booking.yourbrand.com/services/12345?serviceid=7021 Drops the guest into the booking flow with the service preselected. The center identifier segment is required β€” omitting it silently lands the guest on the generic booking page.
Service category /services/<centerId>?CategoryId=<category_id> https://booking.yourbrand.com/services/12345?CategoryId=3304 Lands on the category browse view. Category identifiers are organization-scoped β€” the same category ID applies across all centers in your organization. The center identifier segment is required.
Day package /services/<centerId>?daypackageid=<package_id> https://booking.yourbrand.com/services/12345?daypackageid=4410 Used for day packages within the services booking flow. The center identifier segment is required β€” omitting it silently lands the guest on the generic booking page.
Series package /sales/seriespackage/<centerId>?seriespackageid=<version_id> https://booking.yourbrand.com/sales/seriespackage/12345?seriespackageid=5042 Use Version ID β€” not Package ID. See the critical note below.
Membership /sales/membership/<centerId>?membershipid=<version_id> https://booking.yourbrand.com/sales/membership/12345?membershipid=6118 Use Version ID β€” not Membership ID. See the critical note below.
Fitness class /fitness/classes/<centerId>?classes=<class_identifier>&duration=<duration> https://booking.yourbrand.com/fitness/classes/12345?classes=2207&duration=60 Pre-selects the class on the fitness booking flow.
Provider /services/<centerId>?therapistid=<provider_id> https://booking.yourbrand.com/services/12345?therapistid=9153 Provider deep links are supported, but provider identifiers are not discoverable through the admin interface. To obtain a provider identifier, contact Zenoti Support.

Note: Category identifiers are organization-scoped. The same CategoryId value applies across all centers in your organization β€” you do not need a separate category ID per center.

Note: Service categories are managed at the organization level. At center level, the Category field on an existing service is read-only, so you cannot select a category there to look up its identifier. If you have only center-level access, ask an administrator with organization-level access for the category identifier, or contact Zenoti Support.

Critical: Version ID vs. Package ID for series packages and memberships

Important: Series packages and memberships have two distinct identifiers: the Package/Membership ID and the Version ID. Deep links must use the Version ID. Using the Package ID produces a broken link that fails silently β€” guests click and land on an error page or a blank state.

The Webstore reads the deep-link query parameter as the Version ID and matches it against the entity's version-specific record. The Package ID and Membership ID are separate fields and are not interchangeable with the Version ID.

To find the Version ID:

  1. Sign in to the Zenoti admin portal.
  2. Navigate to the series package or membership entity you want to promote.
  3. Open the entity's detail page and locate the version-specific record β€” typically listed under a Versions tab or section.
  4. Copy the Version ID shown next to the version's effective dates.

Tip: Test every series package and membership deep link in a private browsing window before including it in a campaign. Broken Version IDs are the most common failure mode for these link types.

Worked example: Your organization runs a "Summer Glow" series package. The package has Package ID 1001 and a current active version with Version ID 5042. The correct deep link for center 12345 is:

https://booking.yourbrand.com/sales/seriespackage/12345?seriespackageid=5042

Using ?seriespackageid=1001 (the Package ID) produces a broken link. Always use 5042 (the Version ID).

URL parameters are case-sensitive

?serviceid=... and ?serviceId=... are not interchangeable β€” query parameter names are case-sensitive. Use the exact casing shown in the URL formats table above.

The following table shows the most common casing errors:

Wrong Right
?serviceId= ?serviceid=
?CategoryID= or ?categoryId= ?CategoryId=
?seriesPackageId= or ?SeriesPackageId= ?seriespackageid=
?membershipID= or ?MembershipId= ?membershipid=

If a deep link does not pre-select the entity as expected, check parameter casing first before investigating other causes.

Building campaign URLs

Combine the deep link with UTM parameters for marketing attribution:

https://booking.yourbrand.com/sales/seriespackage/12345?seriespackageid=98765&utm_source=google&utm_medium=cpc&utm_campaign=spring_packages

The Webstore captures all six standard UTM parameters (utm_source, utm_medium, utm_campaign, utm_id, utm_term, utm_content) automatically and persists them through the booking flow. The booking confirmation event sent to your analytics platform includes the original UTM parameters from the entry URL.

For full UTM configuration details, see Configure Webstore UTM tracking.

Common use cases

  • Google Ads campaign for a specific service: Use ?serviceid= so clicks land on the service's booking flow rather than the Webstore homepage. Include the center identifier segment in the URL path.
  • Email campaign promoting a series package: Use the /sales/seriespackage/<centerId>?seriespackageid=<version_id> pattern. Test the link before sending β€” broken Version IDs are the most common failure mode.
  • Social media post linking to a fitness class: Use the /fitness/classes/<centerId>?classes=<class_identifier>&duration=<duration> pattern.
  • Multi-center campaign: Generate one deep link per center using each center's center ID. Each center's catalog, pricing, and availability are independent.
  • Category-level campaign: Use ?CategoryId= when promoting a broad service category (for example, "Facials" or "Massages") rather than a single service. Because category identifiers are organization-scoped, the same CategoryId value works across all centers β€” only the center identifier segment in the URL path changes per center.
  • Provider-specific campaign: Contact Zenoti Support to obtain the provider identifier before building the URL. Provider identifiers are not available in the admin interface.

Before launching a campaign, verify each deep link:

  1. Open the campaign URL in a private browsing window.
  2. Confirm that the Webstore lands on the expected entity β€” service preselected, category open, or package or membership displayed.
  3. Complete a test booking through the flow and confirm the entity carries through to checkout.
  4. If you have GA4 connected, check GA4 DebugView and confirm UTM parameters are captured on the booking confirmation event.

Note: Webstore configuration changes can take up to 30 minutes to propagate due to cache invalidation. If a newly created entity does not appear after following a deep link, wait 30 minutes and test again.

Tips

  • Bookmark your center ID. The center ID is required for service, series package, membership, and fitness class deep links. Keep it in a shared document so your marketing team can build links without contacting an administrator each time.
  • Use a URL shortener for social media. Deep-link URLs with UTM parameters can be long. Use a URL shortener (such as your organization's branded short-link service) for social posts, but always verify the destination URL resolves correctly before publishing.
  • Coordinate with campaign scheduling. If a service or package is not yet Available Online at the time a campaign launches, guests who follow the deep link will not see the expected entity. Enable the entity in the Zenoti admin before the campaign goes live β€” and allow up to 30 minutes for the change to propagate.
  • Test across devices. The Webstore is a responsive web application. Test deep links on both desktop and mobile browsers to confirm the landing experience is correct on all screen sizes.
  • Keep a link registry. Maintain a spreadsheet of all active deep links, their entity names, Version IDs (where applicable), and the campaigns they are used in. This makes it easier to update or retire links when entities change.

Troubleshooting

The deep link lands on the Webstore homepage instead of the expected entity.

  • Check that the URL parameter name uses the exact casing shown in the URL formats table. Parameter names are case-sensitive β€” ?serviceid= and ?serviceId= are different.
  • For service and category links, confirm the URL includes the center identifier segment. A URL missing the center identifier segment silently lands the guest on the generic booking page.
  • Confirm the entity ID in the URL is correct. Copy the ID directly from the Zenoti admin rather than typing it manually.
  • Verify the entity is marked Available Online in the Zenoti admin.

A series package or membership deep link shows an error page or blank state.

  • You are most likely using the Package ID or Membership ID instead of the Version ID. Open the entity in the Zenoti admin, navigate to the version-specific record, and copy the Version ID. Replace the ID in your URL and test again.
  • Confirm the version is currently active. An inactive or expired version will not display on the Webstore even with a correct Version ID.

UTM parameters are not appearing in GA4 or your analytics platform.

  • Confirm that UTM tracking is configured for your Webstore. See Configure Webstore UTM tracking.
  • Check that the UTM parameters are appended after the deep-link parameters in the URL, separated by &. For example: ?seriespackageid=98765&utm_source=google.
  • Verify that no URL shortener or redirect is stripping query parameters before the guest reaches the Webstore.

The fitness class deep link does not pre-select the class.

  • Confirm the classes and duration parameter values match the class identifier and duration configured in the Zenoti admin.
  • Check parameter casing β€” both classes and duration are lowercase.

A provider deep link is not working or I cannot find the provider identifier.

  • Provider identifiers are not visible in the Zenoti admin interface. Contact Zenoti Support to obtain the correct identifier for the provider you want to promote.
Was this article helpful?
Your feedback helps us improve our documentation.