Appearance
Hosting Analytics
WebUse ZynoHosting > Analytics to create shared analytics properties, attach hosted sites, and review the available reports. Analytics separates the reporting dataset and policies your sites share from the choices each individual site makes when it participates.
The useful mental model is:
Property: “What analytics dataset and rules do these sites share?”
Site configuration: “How does this individual site participate in that dataset?”
Access required
Your organization can grant analytics access separately from site-management access. Ask an administrator if Analytics is unavailable or you cannot change a property or site setting.
Analytics properties
An analytics property is the shared reporting container. Sites attached to the same property report into the same dataset and share policies that need to stay consistent, such as reporting timezone, retention, cross-site policy, and individual-journey availability.
For example, shop.example.com and www.example.com can share an Example Commerce property. Their reports are grouped together, and they can optionally use cross-site tracking. The shop can use enhanced collection while the marketing site uses a more restrictive setting.
Property settings
| Setting | What it controls |
|---|---|
| Name | A recognizable label for the shared analytics property. |
| Reporting timezone | The IANA timezone used to group reports, such as America/New_York. |
| Default collection mode | The collection mode sites use unless they choose their own override. |
| Raw-data retention | How long detailed analytics data is retained: 1–395 days. |
| Rollup retention | How long aggregated reporting data is retained: at least the raw-data period and up to 3,650 days. |
| Cross-site mode | Whether sites in this property can use cross-site tracking: off, linker, or hybrid. |
| Individual journeys | Whether authorized users can view person-level journey data. |
| Status | Whether the property is active or disabled. |
Collection modes
| Mode | What it means |
|---|---|
server_only | No analytics JavaScript is added to the site. |
cookieless | Collects allowed browser facts without creating a persistent visitor ID. |
consent_required | Browser collection happens only when the site's consent or legal-basis condition is satisfied. |
enhanced | May use persistent first-party visitor and session cookies after that condition is satisfied. |
Global Privacy Control and your configured consent requirements still apply. Choosing enhanced does not bypass them or guarantee that every visit receives a persistent identifier.
Query-string collection
ZynoHosting currently does not collect query strings for analytics. The underlying model reserves future none, utm_allowlist, and allowlist settings, but the current service accepts only none with an empty allowlist. You will not see query-string collection controls in the portal.
Configure a site's participation
A site's analytics configuration is its attachment to a property plus settings that apply only to that site.
| Setting | What it controls |
|---|---|
| Property membership | Which shared analytics property the site reports into. A site may belong to only one active property at a time. |
| Collection-mode override | A mode specifically for this site. Leave it unset to use the property's default. |
| Cross-site enabled | Whether this site participates in the property's cross-site behavior. |
| Membership status | Whether this site's attachment is active or disabled. |
| Analytics feature | A separate on/off setting for delivering and collecting analytics on the site. It can be enabled only after the site has active property membership. |
The analytics feature has its own deployment status. An active membership tells ZynoHosting where the site should report; the feature status tells you whether collection has been successfully applied to the hosting site. If it is pending, degraded, or has an error, review that status before expecting new data.
Cross-site tracking
Cross-site tracking is possible only when all of these are true:
- The participating sites are attached to the same active analytics property.
- The property uses
linkerorhybridcross-site mode. - Cross-site collection is enabled for every participating site.
- The sites are on the same hosting cluster under the current implementation.
off disables cross-site linkage. linker links sites through URL or link decoration. hybrid also supports the enhanced shared approach where it applies. Sharing a property gives unified reporting, but it does not automatically enable cross-site identity or journeys for every site.
Set up analytics
- Create or select the property that should own the shared dataset and policies.
- Set its timezone, default collection mode, retention, journey setting, and cross-site policy.
- Attach each site to the property. Leave collection mode unset when the property default is appropriate, or choose a more restrictive site-specific mode.
- Enable cross-site collection only for sites that should participate and meet all the requirements above.
- Enable the site's analytics feature and wait for its deployment status to become active.
- Review the site's reports using the date range and views available to your role.
Property, membership, and feature changes can apply in the background. Check their reported status before assuming collection is live. You can disable a property, a site membership, or the site feature when you need to stop collection; existing reports remain subject to the property's retention settings.
Individual journeys and privacy
Individual journeys are more sensitive than aggregate reports. They require both the property's individual-journey setting and dedicated authorized access. Use them only when they are appropriate for your organization's privacy policy and the visitor context.
ZynoHosting supplies trusted site context to the analytics service. A visitor's browser cannot use a page setting to send data into another organization's property.