Campaign History Without Shared Record History

Context

Staff need to review campaign moves and usage changes. Commerce has not adopted the common historical-record and change-event mechanism.

Decision

Campaign activity uses local attributed history, while other selling configuration retains only creation and latest-change metadata.

Alternatives Considered

Adopt the common historical-record mechanism immediately. The pinned implementation has no binding for that adoption; it remains a later change.

Keep no campaign action history. That would remove the existing record of launches, code changes and capacity releases.

Consequences

Older edits to policies, stores and audiences cannot be reconstructed from latest-change metadata. Adopting the common mechanism requires an explicit change across the affected record types.