Mailchimp Grid Integration Block for React

A Mailchimp customer journey starts from a starting point you choose in Mailchimp, such as a contact signing up, a tag being added to a contact, or a date field. Wrenlist can cause the first two by writing a member and by adding a tag to it, so each card says which one it listens for ("Tag added: guide"). Building and turning on the journey itself stays in Mailchimp, where it belongs to you.

Edit JOURNEYS at the top of the file: each has an id, a name, one sentence (text), a trigger (signup, tag or date) with its title and detail, a wait and the email it sends. START_ON lists which switches start on. The tally and the drawn flows derive from those values.

No. A switch changes this page's state and the polite status line says so ("Birthday is on in this demo. Nothing was sent to Mailchimp."). The line is in the page from the first paint. In a real product, store which journeys are enabled with the connection and let your form handler add the matching tag.

Each switch is named by its journey ("Turn on the Welcome journey"), and the flow drawing is hidden from assistive technology because the card's text carries the same facts. The tally and the status line are one polite region, so a change is spoken once. The off state is shown by dashed nodes and links and by the switch itself, never by colour alone.

On a phone the cards stack in one column, with the flow strip and its switch on every card; two columns appear from md and three from lg. In a right-to-left layout the flow runs from the right and the cards flip, while the counts keep their reading order. The header fades up once on load and the nodes change tone with a short transition; reduced motion turns both off.