Customer.io Actions is a connector plugin. It stores its action map and API credentials in wp_options under a prefixed key, keeps a recent-deliveries log either as a custom table or as an option blob, and writes a per-user Customer.io id to wp_usermeta so each WP user maps to a Customer.io profile. The schema is small but operationally important.

The default plugin admin shows whether the workspace is connected and which actions are configured. It does not surface a row-level view of which identify calls landed, which track events failed, and what the payload contained. When a campaign trigger silently misses a user, the only path to root-cause is opening the Customer.io dashboard and reverse-engineering the timeline. Bulk-replay of failed actions isn't a default capability.

SleekView reads the deliveries log directly, joins it to the WP user row through the customerio_id meta key, and exposes the option-stored action map as a navigable view. Failed actions become a saved filter, raw payloads become inspectable cells, and bulk retries route through the plugin's send action so rate limits and registered hooks stay intact.

Customer.io is a behaviour-driven messaging platform, which means every campaign starts with an event that has to land at the right moment with the right attributes. The connector plugin handles the forwarding, but the operational question (did the event actually arrive?) lives in two places at once: the WordPress deliveries log and the Customer.io dashboard. Reconciling them takes time and rarely happens proactively.

The default plugin admin tells you that the workspace is connected but not which actions landed. A single missing identify call can quietly desynchronise an onboarding cohort for weeks before anyone notices. SleekView turns the deliveries log into a workspace where failures are a filter, payloads are an inline cell, and bulk replay is a single action.

For teams running Customer.io as their primary lifecycle layer on top of WordPress, that audit view is the difference between trusting the integration and rebuilding it from scratch every time a campaign feels off.