Mailchimp Detail Integration Block for React

Yes. status takes pending (Mailchimp sends the double opt-in confirmation email) or subscribed; merge_fields holds merge tags such as FNAME and LNAME, the default fields a new audience starts with; tags, ip_signup, timestamp_signup and marketing_permissions are fields of a list member; and double_optin is a setting on the audience. Subscribers are written to /lists/{list_id}/members/{subscriber_hash}, where the hash is the MD5 of the lowercase email address. Edit GROUPS at the top of the file to match exactly what your integration calls.

Mailchimp's OAuth 2 sign-in doesn't ask for scopes the way some services do. What an app can do follows the role of the person who connects it, and Mailchimp answers an action that role doesn't permit with a 403. So the Never tab can't be a list of scopes the app didn't request: it is your own promise about what the integration does, and the note says so.

Both buttons are links (href="#"). Point Connect Mailchimp at your Mailchimp OAuth authorize address and View docs at your setup guide. Nothing connects, signs in or sends anything from the block itself. Connect Mailchimp is a Shine Button, the block's one primary action; View docs is an outline button. Both buttons render the link they're given with render, with nativeButton={false}.

The block names Mailchimp in text, the way any integration page says what it works with, and ships no Mailchimp 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 logo only if you have the rights to use it, under the owner's brand guidelines, and never redraw it. The pair is hidden from assistive technology because the heading already names both.

The tabs are real tabs with panels: arrow keys move between Reads, Writes and Never, and each panel is a list. The tab names carry their counts. The timeline is an ordered list and the mark pair is hidden because the heading names both products.

Below lg the divider gives way to a rule and the parts stack: header, timeline, mark pair and buttons, then the tabs. Fields and API names keep their left-to-right order in a right-to-left layout while the rows flip. The header and buttons fade up once on load; with reduced motion they simply appear.