[MGNLPN-1] As a marketing manager, I create a localized campaign page variant for every major market area, then specify manually for every variant to which visitors it should only show. Created: 11/Feb/14  Updated: 28/Feb/14  Resolved: 28/Feb/14

Status: Closed
Project: Magnolia Personalization
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Story Priority: Neutral
Reporter: Philip Mundt Assignee: Philip Mundt
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Attachments: PDF File PDF prototype.pdf    
Issue Links:
Relates
relates to MGNLPN-2 As a visitor coming from a particular... Closed
relation
is related to MGNLPN-16 As a marketing manager, I create a lo... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLPN-5 Create basic module structure Sub-task Closed Philip Mundt  
MGNLPN-6 Create first version of VariantManager Sub-task Closed Jaroslav Simak  
MGNLPN-10 Create and add "CreateVariantAction" ... Sub-task Closed Philip Mundt  
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Epic Link: Personalisation
Sprint: 5.3 Preparation 2

 Description   

As a marketing manager, I'm planning a new campaign for the relaunch of our main product line. Since we have adapted a product to work in several regions of the planet, I create a localized campaign page variant for every major market area, then specify manually (in the JCR config) for every variant to which visitors it should only show.

This story was part of an initial spike to show the feasibility of th concept.

The follow-up story which entails targeting a page by selecting a country from a dialog is: MGNLPN-16


Generated at Mon Feb 12 06:33:20 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.