Daisy Fashion: Right message. Right audience. Right store.

A shared campaign calendar can save time across a group of fashion stores. It also creates a practical challenge: keeping each store’s audience, signup journey and product links correct. Daisy Fashion shows the less visible work behind getting those details right.

Selected delivery records: August 2021–April 2023. ActiveCampaign email production · audience selection · customer-journey planning.

A shared template still needs a store-specific journey.

Daisy Fashion was part of Eli Zeta’s portfolio and appeared in the team’s production records as UW. Several sister stores shared fashion campaign themes, while their websites, products and audiences remained separate. The work needed to support a repeatable production process without treating every store as interchangeable.

The early records show why that distinction mattered. In August 2021, a team member reported replacing another store’s signup triggers with the popup available for Daisy. The accompanying discussion connected popup work to the welcome journey. This was a practical configuration issue: the entry point had to belong to the store receiving the subscriber.

The challenge continued after signup. Campaigns needed appropriate product selection, correct links and a defined recipient group. A January 2022 production discussion raised the difficulty of finding Daisy’s products and bestsellers. Good execution depended on the available catalogue and brief, as well as the email layout.

How do you reuse a campaign process while keeping the customer’s journey specific to the store?

Check the entry point before scaling the template.

The August 2021 discussion records a store-specific trigger adjustment and further popup work. The broader September lifecycle plan included welcome, abandonment, customer thank-you, winback and sunset journeys for Daisy and the sister stores. Those records establish the intended journey and configuration work; they do not establish that every planned automation went live.

Make audience selection part of the review.

In December 2021, Trayan recorded updating the fashion-store campaign segments, including Daisy, to 90 days. He also removed an extra line from the second email and centred the top link section before marking the campaign ready to send. This review combined audience selection with copy and layout checks, rather than treating scheduling as the only production task.

Adapt the calendar to the audience.

January 2022 instructions separated Australia Day activity from the general sale-reminder schedule and explicitly included Daisy’s Australian audience. October’s Halloween brief also specified Daisy’s offer alongside the other stores’ offers. These were instructions for brand and audience adaptation, not a reason to send one undifferentiated campaign to every list.

Keep platform plans separate from delivered work.

The August 2022 scope record described Daisy’s work as production in ActiveCampaign. In March 2023, moving Daisy to Klaviyo was a discussion item. An April 2023 production message still listed Daisy among the stores built in ActiveCampaign. The case study therefore documents the verified platform work without presenting that migration proposal as a completed launch.

The detail that makes a shared programme usable.

The documented delivery includes signup-trigger checks, campaign audience updates and copy-and-layout review within a recurring production programme. The December campaign reached a recorded ready-to-send state after those changes, and ActiveCampaign production for Daisy remained explicitly documented in April 2023.

The practical change was in the operating process: a reusable campaign still received store-specific configuration and review. That is useful work for a multi-brand team because a correct-looking design can carry the wrong signup trigger, audience or destination.

The selected records do not support a standalone revenue-growth or conversion-lift figure for Daisy. This is an implementation case study about how the work was handled, with a defined historical scope. It does not borrow the commercial results of the larger Eli Zeta stores.

What to apply

Build a separate checklist for the parts that must vary by store: signup source, recipient segment, product destination, offer and local calendar. Reusing the structure should reduce repetitive work while making those differences easier to check.

Put the recipient group in the campaign brief before approving the artwork. The documented 90-day update is a concrete example of audience selection being part of production. It is not a universal sending rule for every account; choose and review the window against your own engagement data.

Track configuration, approval and launch as separate milestones. A welcome-flow plan or a migration discussion should not be counted as a live customer journey until the destination account and activation are verified.

Scope and evidence

What did Thrivelia do for Daisy Fashion?

The selected records document ActiveCampaign email production, signup-trigger checks, audience selection and campaign copy-and-layout review within Eli Zeta’s multi-brand programme.

Was Daisy’s Klaviyo migration verified?

No. A March 2023 record proposed moving Daisy to Klaviyo, while an April 2023 message still confirmed ActiveCampaign production. This case study does not claim that the proposed migration was completed.