Skip to content
Mather Media Solutions

Family entertainment centres, waterparks, amusement operators

Conversion tracking on CenterEdge

A CenterEdge implementation can depend on page markup, which means it can break silently when the checkout changes.

Paid, fixed scope · Within ten business days after complete access

Where the click dies

The drawing below separates two things that usually get treated as one: the event firing, and the money figure attached to it.

Where it dies

The journey does not die here. The value does. The order figure is read off a selector pointed at page markup, and a migration moves that markup out from under it. The reporting edge crosses the seam untouched and keeps firing, now carrying an empty value, which is a number nobody investigates.

What breaks

Diagnosed first-hand on a live account, not read off vendor documentation.

In the documented implementation, order value was scraped through a hardcoded CSS selector instead of read from a data layer. The confirmation trigger watched /cart/thankyoupage without a hostname filter, the same purchase sent different hardcoded flat values to GA4 and Meta, and no transaction ID was available.

Why nobody catches it

Migrations are exactly when nobody is looking at tag configuration. The venue is focused on the new platform working. The old triggers stay live, pointed at markup that no longer exists, and keep reporting.

The work

A list of every legacy trigger found, what it still fires on, and which ones were retired.

  1. 01Replace markup scraping with a real data layer value wherever the platform allows it
  2. 02Scope every legacy trigger to a hostname, not just a path
  3. 03Establish which platform is actually taking orders before assuming the legacy setup is dormant
  4. 04Reconcile a live transaction against the business record to prove the value is the real one

For agencies and operators

Bring a CenterEdge booking flow and we will read its setup before anything is signed.

Agencies keep the client relationship. Operators keep the account ownership. In either arrangement, definitions, configuration and test evidence stay with the people responsible for the work.

Agencies can bring the work in under their own name. Operators can engage directly. The implementation follows the account access and written scope.

Start the tracking audit

Paid, fixed scope · Within ten business days after complete access