Connect Kickbox to a Digioh campaign to check email addresses the moment someone submits a form. This guide walks you through installing the Kickbox Integration extension, connecting your Kickbox account, and choosing how strict validation should be.
What you'll learn
- How to install the Kickbox Integration extension
- How to connect a Kickbox integration to your account
- How to tell Kickbox which form field to validate
- How to control which risk levels are allowed to submit
- What happens when validation succeeds, fails, or can't run
1. Install the Kickbox Integration extension
- Go to the menu under your account name in the top right of the page and select Extensions.

Under the Data Validation section, find Kickbox Integration and click Install.

- Click Publish > Publish to Your Site.

2. Connect your Kickbox integration
- Go to Integrations > Integrations in your account navigation bar.

Click + New Integration and search for Kickbox and click on it.

Name your integration and click Create Integration
![Add New Integration form with Friendly Name set to "Kickbox (8-14-2026)," Integration dropdown set to Kickbox, Campaign (optional) dropdown set to [None], and Create Integration and Cancel buttons.](//dyzz9obi78pm5.cloudfront.net/app/image/id/6a7f7a474ba879ced507d564/n/1786739271611.png)
On the next screen, you'll need to add your Kickbox API Key and domain. To find your API Key, reference Kickbox's documentation. Once entered, click Save.

Go back to the Integrations page, locate the integration you created, and take note of the 5-digit integration ID.

Note: Copy this integration ID. You'll need it in the next step.
3. Add your Kickbox integration ID as account metadata
- Go to the menu under your account name in the top right of the page and select Account Metadata.

Add a metadata key of kickbox_proxy_integration_id and set the value to your Kickbox integration ID.

Click Save
Tip: If you run multiple sites from one Digioh account (for example, a production site and a sandbox), you can point each site to a different Kickbox integration. Add a separate metadata key for each site, using the format kickbox_proxy_integration_id:yoursite.com, replacing yoursite.com with the site's domain. When a site-specific key exists, it takes priority over the default kickbox_proxy_integration_id key for that site.

4. Tell Kickbox which field to validate
- Open the campaign you're setting up for Kickbox and go to Settings > Campaign Settings and scroll down to Campaign Metadata
- Add the campaign metadata key email_field and set its value to email to validate the default Email field, or custom_X (for example, custom_1) to validate a custom field, where X is the field number.

Important: If email_field is missing or points to a field that isn't enabled on the campaign, Kickbox validation is skipped entirely. The form submits normally, and the only record of the problem is a notice in your account's app notifications; the visitor never sees an error. If submissions seem to be going through without validation, check this value first.
5. Choose which risk levels to allow (optional)
Kickbox rates every email as deliverable, undeliverable, risky, or unknown. Deliverable addresses always pass, and undeliverable addresses always fail. By default, risky and unknown addresses are blocked too, but you can choose to allow them.
- To allow risky addresses, add the campaign metadata key kickbox_allow_risky with the value true or risky.
- To allow unknown addresses, add the campaign metadata key kickbox_allow_unknown with the value true or unknown.
Both values are case-insensitive, so TRUE, True, and true all work the same way.
Summary of metadata keys
Metadata Key | Level | Value | Description |
kickbox_proxy_integration_id | Account | ID | Kickbox proxy integration ID. |
kickbox_proxy_integration_id:domain.com | Account | ID | Site-specific variant. Takes priority over the default key when present. |
email_field | Campaign | email / custom_X | Form field containing the email to validate. |
kickbox_allow_risky | Campaign | risky or true | Allow risky addresses to submit. |
kickbox_allow_unknown | Campaign | unknown or true | Allow unknown addresses to submit. |
How submission behavior works
Understanding when a submission is blocked and when it's let through helps you troubleshoot form issues:
- Valid or allowed email: the form submits as normal.
- Blocked email: if Kickbox rates the address as undeliverable (or as risky or unknown and you haven't allowed that rating), the form is blocked, and the visitor sees a generic invalid email error.
- Kickbox can't be reached: if the validation request itself fails because of a network issue, the form is blocked with the same generic error, even if the email address is actually valid.
- Missing configuration: if your account is missing the kickbox_proxy_integration_id metadata, or email_field isn't set correctly, validation is skipped, and the form submits without checking the email at all.
Important: These last two behaviors are opposites: a configuration problem quietly lets submissions through unchecked, while a temporary connection problem blocks every submission. If you notice unusually high bounce rates on your list, check your Kickbox metadata configuration first. If submissions drop to zero, check whether Kickbox is reachable.
Note: Once an email address passes or fails validation, Digioh won't re-check that same address again for the rest of the visitor's session.
That's it, your Kickbox validation is ready to go. Need a hand? Reach out to support@digioh.com.
Want to get more from Digioh?
Get the playbooks leading brands use to convert more visitors into revenue.
Browse the Playbooks ?Platform Tour
See what else you can do with Digioh in our self-guided platform tour.
Take the Tour ?




![Add New Integration form with Friendly Name set to "Kickbox (8-14-2026)," Integration dropdown set to Kickbox, Campaign (optional) dropdown set to [None], and Create Integration and Cancel buttons.](http://dyzz9obi78pm5.cloudfront.net/app/image/id/6a7f7a474ba879ced507d564/n/1786739271611.png)




