EDD ConvertKit adds customers to ConvertKit (Kit) when they purchase and applies tags or sequence subscriptions based on the product bought. The integration stores the subscriber id, applied tags, and last sync timestamp in edd_customermeta under keys such as _edd_convertkit_subscriber_id, _edd_convertkit_tags, and _edd_convertkit_synced_at. The default EDD Customers screen shows none of this, so tag membership and sequence state stay invisible at the row level.

SleekView reads edd_customers with edd_customermeta and joins to edd_orders so subscriber id, tags, last sync, and lifetime value become first-class columns. Marketing builds a saved view of customers in a specific tag with LTV above a threshold, support sees subscriber state inline when answering a sequence-related question, and ops triages customers whose sync failed before the next broadcast.

Inline edits to tag state route through EDD ConvertKit's hooks where supported so the API call is made through the integration's existing chain. Direct meta writes are guarded by conflict detection so a stale row never overwrites a ConvertKit webhook update.

ConvertKit (now Kit) is built around tags and sequences rather than rigid lists, and EDD ConvertKit translates that flexibility into post-purchase automations: buy a course, get tagged, drop into a sequence. The model works for marketers, but the operational data is split. Tags and subscriber ids sit in edd_customermeta, EDD's default Customers screen ignores them, and the ConvertKit UI knows nothing about LTV or product slugs.

The result is the familiar "export both, vlookup in a spreadsheet" workflow every time someone needs a segment. SleekView turns the join into a saved view: subscribers and customers in one row, tags as columns, purchase history visible, LTV computed. Marketing builds the segment once, rebuilds it weekly with two clicks, and ConvertKit stays the source of truth for sends.

Same database, same integration, dramatically less spreadsheet handoff.