Context
We want to distribute different notice wording or designs while knowing exactly which client received which version. This also likely will be a more generalized solution to PR #80, where any element of a templates and its config can be notice variant-specific. It will support not only custom information, but also A/B testing workflows.
Scope
- Support explicit per-client assignment.
- Assignment functionality out of scope
- Decide whether assignments come from:
- the main input file; or
- a separate assignment file.
- Ensure one client receives one notice per run.
- Proper reflection in metadata/manifests
Context
We want to distribute different notice wording or designs while knowing exactly which client received which version. This also likely will be a more generalized solution to PR #80, where any element of a templates and its config can be notice variant-specific. It will support not only custom information, but also A/B testing workflows.
Scope