{"id":40,"date":"2026-07-13T11:04:31","date_gmt":"2026-07-13T05:34:31","guid":{"rendered":"https:\/\/jnkplugins.com\/blog\/docs\/entryvault\/"},"modified":"2026-07-13T11:05:50","modified_gmt":"2026-07-13T05:35:50","slug":"entryvault","status":"publish","type":"page","link":"https:\/\/jnkplugins.com\/blog\/docs\/entryvault\/","title":{"rendered":"EntryVault"},"content":{"rendered":"

EntryVault<\/a> captures form submissions from many builders and stores them in its own tables, then presents them as one searchable, taggable Kanban board. This page explains how that works so you can reason about \u2014 and extend \u2014 it.<\/p>\n

How capture works<\/h2>\n

EntryVault ships one adapter<\/em> per supported form builder. On each request it detects which form plugins are active and registers only the matching adapters \u2014 so there’s no overhead for plugins you don’t use. When a form is submitted, the adapter reads the submission through that builder’s own hooks, normalises it into a common shape, and hands it to EntryVault’s sync engine.<\/p>\n

Supported builders (all in the free tier): Contact Form 7, WPForms, Gravity Forms, Fluent Forms, Forminator, SureForms, Ninja Forms, Formidable Forms, WS Form, Everest Forms, and Trinity Forms<\/a>.<\/p>\n

The normalised submission<\/h2>\n

Every adapter converts a builder-specific payload into the same normalised structure before storage: a list of fields (label, key, value, type), a best-guess email<\/strong> and title<\/strong> for the card, and a dedupe identity. EntryVault copies this into its own tables ({$wpdb->prefix}ev_submissions<\/code> and ev_submission_data<\/code>) \u2014 it never modifies your source plugin’s data, so deleting the original form leaves your EntryVault records intact.<\/p>\n

De-duplication<\/h2>\n

A submission’s identity is the triple (source plugin, source form id, source entry id)<\/strong>. Ingest is idempotent on that triple, so re-processing the same submission won’t create a duplicate card. Adapters for builders that store nothing of their own (Contact Form 7 is the classic case) synthesise a unique entry id per submission, so distinct submissions never collapse into one record.<\/p>\n

Capture timing (why you don’t lose leads)<\/h2>\n

Where a builder offers a pre-send hook, the adapter captures there rather than on “mail sent”. For Contact Form 7 that means capturing on wpcf7_before_send_mail<\/code> \u2014 the same hook Flamingo uses \u2014 so a submission is recorded even if the notification email fails to send<\/em>.<\/p>\n

Working with submissions<\/h2>\n