Guide
Google Analytics on a Custom Domain
Developer-configured GA4 page views on a verified branded storefront domain, with current tracking and privacy boundaries.
SoundSync
Connect GA4
-
Prepare the property
Create the GA4 web stream in your own Analytics account and copy its G- measurement ID.
-
Verify the custom domain
Connect your apex domain or subdomain in Brand Manager and complete domain verification.
-
Save the measurement ID
Use Developer Settings > Google Analytics. Tracking readiness depends on the verified custom-domain connection, not just a correctly formatted ID.
-
Check the customer site
Review page views on the verified branded host and your own GA4 reports. Allow for Google reporting delays.
-
Review notice and consent requirements
Assess the requirements for your audience before enabling GA4. This integration runs automatically and does not provide visitor-consent controls. Where gating is required, do not enable it until suitable controls are available.
Where tracking runs
The storefront integration enables GA4 for the resolved, verified custom-domain host. It tracks supported public storefront pages, not private customer-library, account, or developer-dashboard pages. It is separate from SoundSync's own analytics workspace.
The page-view integration strips non-allowlisted query parameters and uses sanitized page/referrer information. That reduces unnecessary URL data; it is not a promise that no personal data can ever reach Google.
What it does not provide automatically
The current integration sends page views. Do not assume it imports Google reports into SoundSync, emits every ecommerce event, or supplies a complete cookie-consent manager. You remain responsible for your storefront's optional-analytics notice and applicable consent configuration.
Google Analytics on branded storefronts
When a developer configures GA4 for an eligible verified custom-domain storefront, this integration loads the Google tag and queues page views automatically on supported public pages. It does not wait for visitor opt-in, and a previously saved analytics decline does not disable this integration. Account, sign-in, developer and owner routes are excluded by its public-page rules.
The page URLs supplied by this integration omit query parameters except permitted catalog, product and bundle selectors; supplied referrers omit queries and fragments. This does not mean analytics is anonymous or cookie-free. Google processes information under its own terms and the configured property settings. Necessary account and checkout storage is separate.
This is not a consent-management system or a guarantee of legal compliance. The former soundsync:analytics-consent event is not a supported switch for this tracker. Developers must assess applicable notice and consent requirements before enabling analytics and arrange any required controls; a notice alone does not enforce a visitor choice.
SoundSync