Contact Form 7 Conditional Fields layers show/hide logic onto standard CF7 forms. The form definition stays in the wpcf7_contact_form custom post type, and submissions persist through Flamingo as flamingo_inbound posts. Each submission records the field values that were visible at the time of submit, while hidden-branch fields are skipped. The default Flamingo screen lists messages with a fixed column set and no view of which branch each respondent took.

SleekView Charts reads the Flamingo inbound feed and pivots the submission payload into queryable columns. A KPI counts submissions in the last seven days. A horizontal bar groups submissions by the value of the controlling field (the branch trigger). A donut splits respondents by which conditional group they actually filled in. An area chart tracks daily volume across the date range so a stalled branch shows up as a flat line on the dashboard.

Form admins finally see the shape of conditional traffic: how many respondents took the support branch versus the sales branch, how many abandoned after a conditional reveal, which question paths complete and which dead-end. The data is already in flamingo_inbound postmeta; SleekView Charts just makes it legible.

Conditional logic exists to make one form serve many audiences. A single contact form routes sales, support, partnerships, and careers down separate questions without splitting the form into four pages. That works on the capture side: respondents only see the questions that apply to them.

It falls apart on the analytics side because the default CF7 plus Flamingo admin shows each submission as a flat row with no view of which branch the respondent followed. Form admins guess at branch usage from anecdotal scanning. Marketing has no way to confirm that a campaign pointed at the partnership branch is converting to partnership submissions rather than the sales branch.

SleekView Charts reads the Flamingo inbound feed and treats the controlling field as a first-class dimension. A bar of branch usage answers "which path did people take", a donut of completion answers "which questions did they finish", a volume area answers "is the form still healthy". The data is captured by CF7 Conditional Fields the moment it is submitted; SleekView Charts just turns the captured data into the dashboard the people running the form already wish they had.