Web Properties

A property is the working unit for the measurement team. Give it a name, an organization, an owner and a definition before collecting session facts. Its number and source record identity help the team distinguish a production site from a campaign destination with a similar name. The session date gives the work a time anchor. The consent basis explains why its observations may be used.

The lifecycle moves from Configured to Collecting, Validated, Analyzed and Published. Each status is a work decision. A property should not be marked Published just because a dashboard tile renders. The owner needs to know which collection run, review decision and observed values support that result.

• Property context. The organization, owner and definition identify the source and who is responsible for it.
• Measured outcome. Sessions, visitors, conversions, goal completions and variant exposure sit with the property for review.
• Revision trail. State history and operation runs make a change explainable after the status moves.

Decide how a property maps to a source system and how its source record identity is assigned. Agree which person owns each property and who independently reviews a source revision when approval is required. Define the consent basis before session collection. If a site and a campaign page require different ownership, keep them distinct rather than combining their readings into a name that nobody can reconcile.

Set a practical rule for the move into Validated and for the later Published status. The recorded decision needs to match the revision being released. A later source change deserves its own review context. This keeps the dashboard’s observed conversion trend tied to the source the team actually accepted.

Suppose the team measures a new product landing page. The Property Owner creates its record under the right organization, selects the experiment definition and records the consent basis. The Analyst collects consented facts and checks that they belong to this property. The Reviewer examines the relevant revision and evidence before approving it. The Analytics Lead then compares the session and conversion values with the run history. If an exception remains, an assigned follow-up action keeps it visible to its owner.

A status change without the linked run or decision is a reason to pause the handoff. Open the state history to see who acted and why. Check the run’s source revision before treating the displayed result as the accepted one.

• Property Lifecycle — Find measured properties by status, owner and organization.
• My Properties — Let an owner work through their assigned sources.
• Property Status Board — Review the handoff from configuration to publication.

Use property collection to trace the source into consented facts, then review and publish for the release decision.