Missing shared context: engineering solution

Send each approved shared property from every source and event that needs it. Data Assistant and tracking-plan configuration can't populate a value the application, server, or pipeline doesn't send. Start from the property contract and affected-source list in the audit.

Use a user property when the value describes the person and should persist across future activity. Use an event property when the value describes one action at the time it happens.

Update the implementation

1. Start from the property contract and affected-source list in the audit.
2. Map the property to a trusted application or backend value.
3. For a user property, set or update it before the next event that needs the new value. Don't resend an unchanged custom user property on every event unless your integration requires it.
4. For an event property, add it to every relevant event payload at the point where the source knows the value.
5. Keep names, types, and allowed values consistent across web, mobile, backend, and customer data platform mappings.
6. Avoid deriving sensitive values or sending data that violates your organization's privacy policy.

Validate the fix

1. Trigger representative events from every changed source.
2. Inspect the raw payloads in Event Explorer or the user's event timeline.
3. Confirm that Observe reports the required property with full expected coverage for the test window.
4. Build a chart grouped by the property and check for unexpected (none) values.

If existing raw properties already contain the needed value, a derived property may support analysis without new instrumentation. Derived properties calculate at query time and don't change the source payload or fill the original property's coverage gap.