Day-Grouped Timeline Mailchimp Integration Block for React

No. Retry sync turns the row's button to Writing for about 900 ms, then to Written, and the status line says so: "Nothing was sent to Mailchimp". To make it real, call your own endpoint from retry in the block, and set the row's phase from the result. The timer is cleared if the block unmounts, so a late timeout never updates a page that has gone.

The words follow what Mailchimp reports. A double opt-in signup waits as pending until the person clicks the confirmation link, an unsubscribe is the person's own choice and only they can resubscribe, and Mailchimp cleans an address after a hard bounce. Because a cleaned address can't be written again, only the timed-out write has a retry. Edit START to list the events your product records.

It dims rows rather than removing them. A row that doesn't match gets a solid five-percent tint and softer text, so every row keeps its height and the list never reflows. Needs attention counts the bounced and not-written rows, and the count follows the rows: it drops by one when the retry finishes.

Each heading is a fixed ISO day spelled by one Intl.DateTimeFormat in UTC, so "Wednesday, Oct 14" reads the same on the server and in every browser. Nothing is computed from today. Times are fixed UTC strings in a time element.

The block names Mailchimp in text and ships no logo, colour or wordmark. Its tile is a neutral lettermark, Mc in a muted square, in an icon slot that a code comment marks: drop in the official mark only if you have the rights to use it under the owner's brand guidelines, and never redraw it.

On a phone each row stacks: the glyph, the event and address, then the form and time on a second line, with Retry sync at the row's end. In a right-to-left layout the columns flip while addresses, form names and times keep their own direction. The entrance is a CSS transition that is dropped under reduced motion.