Campaigns prepared in parallel, released on their date

Deliver brand messaging and product information with approval and scheduled publishing, ship hot fixes when you need to, and roll back to a last known good state.

Holiday campaignRelease
Source branch
holiday-campaign
Scheduled
Black Friday · 09:00 UTC
Changesets
42:e9a03f61, 43:7c21d0a4
Conflicts
1 resolved in promo.regions
Status
Approved
On go-live
Merge to master, publish to CDN, notify Slack
Example release, locked to its date. Illustrative data.

What retail teams need

Black Friday, the holiday season and product launches decide the year, and each needs its own products, pages and experiences ready on a fixed date.

Fixed dates
Every product, page and experience has to be ready on a date that won’t move.
Parallel teams
Brand, product and regional teams prepare campaigns at once, and their changes collide.
Preview and approval
Editors need to see changes as they will look live, and managers need to approve each batch.
A way back
When a launch goes wrong, the site has to return to a known good state quickly.
Under Armour Cricket Wireless

How Gitana gets every campaign out on its date

Branches, merges and scheduled releases let retail teams prepare many launches at once and ship each on time.

  • Scheduled releases and hot fixes

    Releases go live on their date, and hot fixes can ship ahead of the schedule.

  • A branch for each campaign

    Teams work on a branch and merge it to master when it is approved. When two campaigns change the same field, rules resolve it automatically or an editor chooses which change to keep.

  • Preview and approval

    Preview a release, approve it through workflow, and promote it from staging to live.

  • Rollback

    Every change is versioned, so you can roll back to a last known good state.

Merge holiday-campaign into master 1 conflict
master holiday-campaign

masterholiday-campaign

promo.regions changed on both branches. The differences are marked.
master

["US", "CA"]

Drops EU
holiday-campaign

["US", "EU"]

Drops CA
combined

["US", "CA", "EU"]

Keeps both

Next changeset: 44Choose a version to create the merge changeset on master.

Two branches changed the regions of one promotion. Example merge, modeled on Gitana’s conflict resolution view. Choose a version to resolve it.

See how Gitana fits your content

In a demo, a solutions engineer walks you through Gitana around your use case. The same call covers architecture, security, deployment and procurement questions. In a guided evaluation, you work on your own content with one of our engineers on Gitana Cloud.