Migration › Knowledge Base › Governance & ownership
Governance & ownership
The project ends; the system lives on. After any move, someone has to water the plants, and the Web SDK spreads ownership across more surfaces than AppMeasurement ever did.
Where one team used to own "the Analytics tag," responsibility now spans several places, each of which rots if unowned:
| Schema | Data architect, field changes ripple to CJA/AEP; the Profile lock is irreversible |
| Datastream | Analytics eng / admin, RSID routing and services; a wrong RSID is a silent disaster |
| Tags | Analytics implementation, rules, data elements, publishing |
| Data layer | Front-end / product, the menu the waiter reads; drift breaks everything |
| Consent | Analytics + Privacy/Legal, defaultConsent, CMP cookie categorisation |
| Identity | Data architect, cross-domain, CRM IDs, ECID continuity |
For your migration: assign a named owner to each surface and put a change-control step on the irreversible ones (schema, datastream). The handover from "project" to "operated system" is where many otherwise-clean migrations slowly decay.
Assign a named owner to each surface, schema, datastream, tags, data layer, consent, identity, before the project closes, and put change-control on the irreversible ones.
The project ends; the system lives on
AppMeasurement concentrated ownership in "the Analytics tag." The Web SDK spreads it across several surfaces, and any surface without a clear owner quietly decays. The handover from project to operated system is where many technically clean migrations slowly fall apart.
Who owns what
| Schema | Data architect, field changes ripple to CJA/AEP; the Profile lock is irreversible |
| Datastream | Analytics eng / admin, RSID routing and services; a wrong RSID is a silent disaster |
| Tags | Analytics implementation, rules, data elements, publishing |
| Data layer | Front-end / product, the source every mapping reads; drift breaks everything |
| Consent | Analytics + Privacy/Legal, defaultConsent posture, CMP cookie categorisation |
| Identity | Data architect, cross-domain, CRM namespaces, ECID continuity |
| Report suites | Analytics admin, processing rules, classifications, marketing channels |
Operating cadence
Put a change-control step on the irreversible surfaces (schema and datastream edits especially). Maintain a documented, versioned data-layer spec with an owner. Reuse the validation checklist as a release gate. And run a periodic audit that the mapping matrix still reflects reality, variables drift, and an out-of-date matrix is how silent breakage creeps back in.