Every submission from Contact Form, Trip Builder, or Cart Abandonment Recovery is saved to one Entries screen automatically, with a delivery log showing whether it actually reached you and a one-click resend if it did not.
What it does #
A guest inquiry, a saved trip, an abandoned-cart lead: any of these can fail to reach you. An email bounces, a webhook receiver is briefly down, a connection times out. Without a record of the original submission, that guest is simply gone. Form Entries fixes that by saving every submission the moment it happens, before anything is emailed or forwarded anywhere.
Three Conversion Kit tools feed Entries, each in its own way:
- Contact Form. Every “Have a Question?” inquiry is saved as it comes in, whether or not the notification email or webhook forward it successfully.
- Trip Builder. A saved trip is recorded only when the guest gave an email. Anonymous saves carry no personal information, so they are never recorded.
- Cart Abandonment Recovery. An abandoned cart is recorded only once the guest is identified, meaning they have a known email. This is passive capture: it logs that the abandonment happened, nothing more.
Each saved entry shows:
- What the guest submitted, and when.
- Which property (if any) it relates to.
- A delivery log for every place the submission was supposed to go, an email inbox or a connected webhook, each marked sent, pending, or failed.
- A resend button on any delivery that can be retried.
If you also run HomeRunner Toolkit on this site, its forms share this same Entries screen and dataset, so you have one place to check instead of two.
Example. A guest taps “Have a Question?” on your Sunset Bungalow listing, fills in their dates, and sends the message. HomeRunner saves that inquiry immediately, then emails your team. If the notification email bounces, the entry’s delivery log shows the email channel marked failed, with the actual error underneath. You resend it from that screen with one click, no need to ask the guest to submit again.
How to turn it on #
Form Entries does not have its own on/off switch in Conversion Kit. The screen appears in your admin menu automatically, and it fills in as soon as one of the three tools above is doing its normal job.
1. Turn on a tool that feeds Entries #
Set up Contact Form, Trip Builder, or Cart Abandonment Recovery as you normally would. See Contact Form, Trip Builder, and Cart Abandonment Recovery for each tool’s own setup steps. You do not need all three, entries start appearing as soon as any one of them captures its first submission.
2. Find the Entries screen #
Look for Entries in your admin menu, under HomeRunner if you run the main HomeRunner plugin, or under Settings if you do not.
3. Review the retention and privacy settings #
Open Entries → Settings to set how long entries are kept, whether IP addresses are captured, and the failed-delivery alarm threshold (see Settings below). All three have sensible defaults, so this step is optional, but worth a quick look if you have a specific privacy policy to match.
Settings #
| Setting | What it controls |
|---|---|
| Retention (days) | How long entries are kept before a daily cleanup job permanently deletes them, delivery log included. Default 365 days. Set to 0 to keep entries forever. |
| Capture IP / user agent | Whether the guest’s IP address and browser information are stored with each entry. Default on. |
| Failed-delivery alarm | Shows a dismissible notice on every admin page when a form’s notification emails fail this many times in a row, linking to that form’s entries. Clears automatically on the next successful send. Default 3. Set to 0 to disable the alarm. |
| Delete all entries on uninstall | Whether uninstalling Conversion Kit drops the shared entries data. Default off, entries survive uninstall. Because the dataset is shared with HomeRunner Toolkit, data is only actually dropped when this box is checked and the Toolkit plugin is no longer installed on the site. While either plugin remains, your entries stay put. |
Tips #
- Guest receipts are not the same across all three forms. Contact Form has its own Guest Receipt toggle (off by default, in Contact Form’s settings) that emails the guest an automatic copy of their inquiry. Trip Builder has no separate toggle: whenever a guest provides an email, the trip-link email it already sends doubles as that entry’s receipt automatically. Cart Abandonment Recovery does not send a receipt at all, since it only logs an identified abandonment passively.
- The failed-delivery alarm watches notification emails specifically. A run of failed webhook deliveries will not trigger it on its own, check the entry’s delivery log directly if you rely on a connected webhook.
- Export to CSV or JSON from the Entries list, filtered by form, property, or date range. Exports are capped at 10,000 rows per request, narrow your filters for larger sets. Every export is logged on the Settings screen with who ran it and when.
- A failed delivery can be resent straight from the entry’s delivery log, when the tool that submitted it supports resending that channel. A resent webhook carries the exact original payload, so a receiver that de-duplicates on it may drop the redelivery.
- Entries hold guest personal data, so set retention and IP capture to match your privacy policy. Entries also respond automatically to WordPress’s built-in personal data export and erase tools, no extra setup needed.
- Running HomeRunner Toolkit alongside Conversion Kit? Its forms show up in this same shared screen. See Toolkit: Form Entries.