SalesFusion for WP is a SaaS connector. It stores API credentials and form-to-campaign mappings in wp_options, keeps a recent-events log either as a custom table or as an option blob, and writes per-user SalesFusion contact ids to wp_usermeta. The footprint is intentionally compact because SalesFusion (now part of SugarMarket) is the platform of record.

The default plugin admin shows whether the connection is healthy and which forms route to which campaigns. It does not give a row-level view of which lead pushes landed, which failed, and what the payload contained. Per-form audit ("how many demo-request submissions actually reached the SDR queue this week") requires reading log entries one at a time or switching to the SalesFusion dashboard.

SleekView reads the sync log directly, joins it to WP users through the SalesFusion id meta key, and pivots option-stored campaign mappings into a navigable view. Failed pushes become a filterable cohort, payloads become inspectable cells, and bulk-resync routes through the plugin's push action so registered hooks fire as expected.

SalesFusion (now SugarMarket) is a B2B marketing automation platform, which means every lead it receives is the start of a multi-touch nurture sequence. The WordPress connector pushes those leads, but the operational question (did this lead actually reach the right campaign with the right attributes) lives in two places at once. The default connector admin tells you the API is connected; it does not tell you whether last week's webinar form actually populated the post-webinar nurture campaign.

The data needed to answer that question already exists in WordPress (in the sync log, in wp_usermeta, in the option-stored mappings) but the default UI doesn't surface it at row level. SleekView turns those rows into a workspace. Failed pushes become a filter, mappings become a maintained view, and bulk resync routes through the plugin's existing push action.

For B2B marketing teams running SalesFusion campaigns on top of WordPress, that audit layer is the difference between trusting the pipeline and reconciling it after every campaign.