[Feature] Reusable distribution lists as campaign recipient sources #4

New Issue

zemion · 2026-07-14T20:08:41+02:00

zemion commented

2026-07-14 20:08:41 +02:00

Problem / User Need

Distribution lists should act like reusable recipient lists for multiple campaigns. They need stable IDs to match entries in campaigns even when recipient data is copied, referenced, or enriched for a specific campaign.

Acceptance Criteria

A distribution list can serve as a recipient source for multiple campaigns.
Entries have stable IDs that can be matched from campaign data back to the source list.
The model supports deciding whether recipient data stays in the campaign snapshot or lives in the list.
Dependent/enriched lists are considered, for example one base list with different attached data for different purposes.
Campaign integration can detect changes, missing entries, and matching conflicts.

Notes / Decisions

Requires data-model decisions before implementation: snapshot vs live reference, dependent lists, and campaign-specific enrichment.

## Problem / User Need Distribution lists should act like reusable recipient lists for multiple campaigns. They need stable IDs to match entries in campaigns even when recipient data is copied, referenced, or enriched for a specific campaign. ## Acceptance Criteria - A distribution list can serve as a recipient source for multiple campaigns. - Entries have stable IDs that can be matched from campaign data back to the source list. - The model supports deciding whether recipient data stays in the campaign snapshot or lives in the list. - Dependent/enriched lists are considered, for example one base list with different attached data for different purposes. - Campaign integration can detect changes, missing entries, and matching conflicts. ## Notes / Decisions Requires data-model decisions before implementation: snapshot vs live reference, dependent lists, and campaign-specific enrichment.

zemion added the