EDD Mailchimp adds customers to Mailchimp lists when they purchase, optionally tagging them with product purchases and storing the sync state in edd_customermeta or edd_ordermeta under keys like _edd_mailchimp_subscribed and _edd_mailchimp_list_id. The default EDD admin doesn't surface any of this on the Customers or Orders screen, so opt-in status and list membership stay invisible at the row level.

SleekView reads edd_customers together with edd_customermeta and joins to edd_orders so opt-in status, list id, last sync timestamp, and lifetime value become first-class columns. Marketing builds a saved view of subscribers acquired in the last quarter, support sees opt-in state inline when responding to GDPR requests, and ops triages customers whose sync failed before the next campaign sends.

Inline edits to subscription state route through EDD's CRUD layer where supported so EDD Mailchimp's subscribe and unsubscribe hooks fire. Direct meta writes are guarded by conflict detection so a stale admin row never overwrites a Mailchimp webhook update.

EDD Mailchimp is one of the most common ways a digital store keeps its marketing list in sync with its customer list. The integration works cleanly on the happy path: a customer buys, gets added to a Mailchimp list, optionally gets tagged with the product. Where it falls down is making the result usable inside WordPress.

The default EDD admin treats opt-in state as invisible meta. The default Mailchimp UI knows nothing about LTV or which EDD product a subscriber bought first. Operators end up exporting CSVs both directions to build a segment that's really just "customers who bought X, opted in to list Y, ordered more than once".

SleekView turns that into a saved view inside WordPress: subscribers and customers joined, opt-in state visible, product purchases joined through edd_order_items. Marketing builds the segment once and rebuilds it monthly with two clicks. Same database, same Mailchimp integration, dramatically less CSV juggling.