Measurement and eCommerce analytics

Google Analytics 4 for CMS Max

Measure the website journey and send supported purchase events from the server.

The CMS Max Google Analytics plugin supports a consent-aware GA4 script mode and an eCommerce mode that sends purchase events through Google’s Measurement Protocol using the configured Measurement ID and API secret.

  • GA4 setup
  • Consent-aware script
  • Purchase events
  • Item data
  • Property connection
Google Analyticson CMS Max
Product workflow
CMS Max dashboard for the website and eCommerce data measured with Google Analytics 4
CMS Max connects analytics configuration to the website and eCommerce environment where content, forms, catalog, customers, and orders are managed.
01Choose tracking mode
02Configure consent
03Validate reports

Design the operating workflow

The connection is only useful when the team can trust and maintain it.

Start with business outcomes, data ownership, consent and security, realistic test cases, monitoring, support, and a change process. Then configure the technology.

Start with a measurement plan

Define decisions, events, conversions, dimensions, owners, consent requirements, attribution limits, and data-quality checks before adding tags.

Use the right tracking mode

Paste a consent-gated GA4 script for general tracking, or configure the Measurement ID and API secret for supported server-side purchase events.

Validate end to end

Use Google’s debugging and reporting tools, compare CMS Max orders with GA4 events, and document expected differences and reconciliation.

CMS Max integration capabilities

What the current CMS Max implementation supports.

Availability depends on the plugin being active, required accounts and credentials, source data, consent, provider access, plan limits, and the specific tenant configuration.

01 / Script mode

Consent-aware GA4 script

Paste the full GA4 tracking snippet and CMS Max injects it into the website head unless the visitor has explicitly rejected optional cookies.

02 / eCommerce mode

Server-side purchase events

Configure a GA4 Measurement ID and Measurement Protocol API secret so supported placed orders can send purchase events from the server.

03 / Commerce detail

Transaction and item parameters

The purchase payload includes transaction ID, value, currency, tax, shipping, item IDs, item names, price, quantity, and a discount indicator when applicable.

04 / Google connection

Optional account and property discovery

Use the Google OAuth widget for account-level connection and asynchronous discovery of available Analytics properties.

05 / Consent

Cookie policy activation

Installing Google Analytics enables the tenant cookie banner. Review the public copy, privacy-page link, categories, and actual script behavior before launch.

06 / Quality

Reconciliation and governance

GA4 is an analytics system, not the order ledger. Compare event counts and values with CMS Max, document exclusions, and assign an owner for configuration changes.

End-to-end workflow

Make every handoff visible.

The system needs a clear start, protected configuration, representative validation, an observable result, and a named owner for improvement.

01

Plan

Define events, conversions, owners, and consent.

02

Configure

Choose script or server-side eCommerce mode.

03

Consent

Review cookie banner and privacy information.

04

Test

Validate tags, purchase payloads, and reports.

05

Reconcile

Compare analytics with CMS Max source records.

Implementation sequence

Move from account access to production confidence.

Do not publish the integration until the data, consent, errors, ownership, and rollback path have been reviewed.

01. Create the measurement plan

List the business questions, GA4 property, web stream, conversion events, campaign conventions, consent basis, and report owners.

02. Install Google Analytics

Activate the CMS Max plugin and review the automatically enabled cookie-policy banner.

03. Choose a mode

Use the GA4 script for browser tracking or enable eCommerce events and enter the Measurement ID and API secret.

04. Protect credentials

Treat the Measurement Protocol API secret as a secret and limit access to the CMS Max and Google administration owners.

05. Run test journeys

Visit pages under relevant consent states and place representative orders with tax, shipping, multiple items, discounts, and currencies.

06. Reconcile and monitor

Compare CMS Max orders to GA4 purchase events and values, record expected gaps, and review changes to consent or tracking configuration.

Governance and quality

Protect the customer, the data, and the operating team.

Provider policies and website requirements change. Keep credentials, consent, mappings, errors, and ownership under active review.

Consent is configuration
A banner alone is not a complete privacy program. Review disclosures, categories, default behavior, regional requirements, and connected tags with qualified advisors.
Server-side is not magic
Measurement Protocol can improve supported purchase delivery, but it does not make attribution complete or remove the need for consent, identity, debugging, and reconciliation.
Secrets stay private
Store the Measurement Protocol API secret only in the protected plugin setting. Do not place it in page content, scripts, screenshots, or shared documentation.
Analytics is not accounting
Use CMS Max and connected financial systems as operational records. Treat GA4 as a behavioral and marketing measurement system.

Documentation and related resources

Confirm the current provider requirements.

Use official provider documentation and the live CMS Max configuration during implementation. Features, interfaces, policies, and plans can change.

Integration FAQ

Questions to resolve before launch.

Use representative testing and written ownership to turn these answers into a reliable production workflow.

Does CMS Max support Google Analytics 4?

Yes. The Google Analytics plugin supports a GA4 script mode and an eCommerce mode that uses a Measurement ID and Measurement Protocol API secret for supported server-side purchase events.

What does server-side purchase tracking send?

The supported purchase event can include transaction ID, value, currency, tax, shipping, item IDs, item names, prices, quantities, and a discount indicator when applicable.

Does the GA4 script load after optional cookies are rejected?

No. The CMS Max frontend script is gated so it is not rendered after the visitor explicitly rejects optional cookies. Review the full consent configuration for the site.

Does installing the plugin add a cookie banner?

Installing the Google Analytics plugin automatically enables the tenant cookie-policy banner. The website owner should review its copy, privacy link, categories, and behavior.

Can CMS Max connect a Google account?

The plugin includes an optional Google OAuth widget used for account-level connection and property discovery. Access and property selection should be owned and documented.

Will GA4 match CMS Max order reports exactly?

Not always. Consent, identifiers, network delivery, filtering, time zones, attribution, refunds, test orders, and configuration can create differences. Reconcile regularly and use CMS Max as the operational source.

Connect with purpose

Build an integration the business can operate after launch.

Bring the account, use case, data, consent requirements, owners, test plan, error handling, and success metrics. CMS Max will help define the supported path.

Building Relationships with Web Developers and Marketing Agencies that want better results

The world's fastest and most SEO friendly website code.