What This Update Actually Is
HubSpot has expanded its AI-powered gibberish detection to cover all text fields in a form submission. Before this update, the detection was limited in scope. Now the AI scans every text input, catches random strings and meaningless sequences, and moves flagged submissions to the Spam Submissions tool automatically.
One important caveat: sensitive data fields are not included in gibberish detection right now. HubSpot hasn't shipped that piece yet, so keep that boundary in mind when you're evaluating coverage.
Flagged entries sit in the Spam Submissions tool for up to 90 days. During that window, you can review, release, or delete them. After 90 days, HubSpot deletes them automatically.
Why HubSpot Shipped This
Spam form submissions are one of the quietest CRM killers we see. Humans spend real time chasing contacts that were never real. Workflows fire. Sequences trigger. Lead scores inflate. And by the time someone realizes the name field says "asdfghjkl," the damage to data quality is already done.
The internal frustration is real too. Marketing ops leaders don't want to babysit form submissions. They want to trust the data coming in. That trust erodes fast when a handful of junk records slip through every week and clutter the pipeline view.
HubSpot's answer is to move the filter upstream, before the record exists in the CRM. That's the right design choice. Clean data at the source beats a cleanup workflow every time.
How to Use It Step by Step
- Go to Settings > Tools > Marketing > Forms > Submission Settings in your portal.
- Toggle ON the "Gibberish detection" switch. This enables detection at the portal level for all forms.
- Review any properties where you intentionally collect alphanumeric strings, like order numbers, access codes, or license keys. Go to the Rules section for each of those properties and exclude them from gibberish detection so valid submissions aren't flagged.
- Check your Forms list view. You'll now see a "Spam Submissions" count column. This gives you a quick read on which forms are attracting the most junk traffic.
- Click the spam count for any form to open the Spam Submissions side panel. Each entry is labeled with Spam Type: "Gibberish" so you know exactly why it was flagged.
- Decide what to do with each entry: delete it immediately or release it into the CRM if you determine it's legitimate. If you take no action, the entry is auto-deleted after 90 days.
What It Touches in Your HubSpot Strategy
This update is technically a forms setting. But the ripple effect runs much deeper than that.
Key Takeaway
Every workflow, sequence, or nurture campaign triggered by a form submission is only as good as the data entering it. Stopping gibberish at the gate means your automations fire on real signals, not noise.
CRM Data Quality
Fewer junk contacts entering the CRM means cleaner contact lists, more accurate lead scores, and list segmentation you can actually trust. If you're running any form of predictive lead scoring or lifecycle stage automation, this directly improves the signal quality those tools depend on.
Email Deliverability
This one surprises teams when we first bring it up. Spam form submissions often produce fake or malformed email addresses. Sending to those addresses hurts your sender reputation and inbox placement rates over time.
We've written about how a bloated or dirty contact list actively hurts your email deliverability. If you haven't read why your B2B email list might be killing your inbox placement, this update is a good reason to revisit that conversation.
Workflows and Automation
Any workflow that enrolls contacts from a form submission will benefit here. The trigger condition "contact submitted form X" now carries more weight because the contacts entering that workflow have cleared the gibberish filter first.
Reporting and Attribution
Form submission counts in your reports will better reflect genuine interest. If your team reports on leads generated by form, those numbers were previously inflated by junk. Cleaner submissions mean your attribution data gets closer to reality.
Key Takeaway
If you have forms collecting alphanumeric codes, serial numbers, or short ID strings, exclude those properties from gibberish detection immediately. Valid submissions for fields like coupon codes or product keys could otherwise land in spam and never reach your CRM.
A Note on Duplicate Management
Gibberish contacts that do slip through often create near-duplicate records with scrambled data. If you're using HubSpot's Duplicate Similarity Score to manage CRM record matching, catching gibberish at the form level reduces the noise that tool has to sort through downstream.
Who Should Care Most
This update matters most to the following groups.
- Turn it on immediately if you're a marketing ops leader or HubSpot admin who owns form and list hygiene. This is a direct quality-of-life improvement for your week.
- Review your property-level settings first if you're a demand generation manager running high-volume lead capture. Any field that collects alphanumeric codes needs an exclusion rule before you flip the portal toggle.
- Audit your form count in the Spam Submissions column if you're a revenue operations leader who depends on form-to-pipeline reporting. You may find the volume of flagged entries tells a story about which landing pages are being targeted by bots.
- Pay attention if you're a business owner who was told lead volume was growing. Some of that growth may have been junk. This update will give you a clearer picture of actual lead quality going forward.
This feature requires Marketing Hub Pro/Enterprise or Content Hub Pro/Enterprise. If you're on Starter, this isn't available yet.
George's Take
We've done portal audits where a team thought they were generating 400 leads a month and were genuinely shocked when we showed them that 60 of those contacts had names and messages that looked like someone fell asleep on a keyboard. The humans working those lists were wasting hours. The automations were wasting sends. And the reporting was giving leadership a false sense of momentum. This update doesn't solve every spam problem, but it closes a gap that has been costing real teams real time for years. Turn it on. Check your alphanumeric exclusions. Then go look at your spam count and let the number tell you what your forms have actually been dealing with.
“Your CRM is only as trustworthy as the data entering it. Catching gibberish at the gate isn't a nice-to-have. It's the foundation that makes every report, workflow, and conversation with a prospect mean something.”
This update shipped alongside a wave of AI-focused changes. If you want the full picture of what HubSpot released this week, our May 2026 HubSpot updates roundup breaks down all 28 releases and what they mean for your portal strategy.
If you want a second set of eyes on your form setup, spam patterns, or overall data quality, Sidekick Strategies offers portal audit sessions built for exactly this kind of conversation. Book a strategy call and let's look at what your forms are actually capturing.
Frequently Asked Questions
What does HubSpot's gibberish detection actually do?
HubSpot's AI-powered gibberish detection scans all text fields in a form submission and flags entries that contain meaningless or random character strings. Flagged submissions are moved to the Spam Submissions tool instead of creating records in the CRM. You can review, release, or delete them within 90 days.
How do I turn on gibberish detection in HubSpot?
Go to Settings > Tools > Marketing > Forms > Submission Settings and toggle on "Gibberish detection." This enables it at the portal level. You can also go to individual properties and exclude them from detection under the Rules section if they collect alphanumeric strings like codes or IDs.
What happens to submissions flagged as gibberish?
Flagged submissions are routed to the Spam Submissions tool and labeled with Spam Type: "Gibberish." They don't enter your CRM. You can review the side panel, release legitimate entries, or delete spam manually. If no action is taken, HubSpot automatically deletes them after 90 days.
Which HubSpot plans include gibberish detection for forms?
Gibberish detection is available on Marketing Hub Professional, Marketing Hub Enterprise, Content Hub Professional, and Content Hub Enterprise. It's not included in Free or Starter plans as of this release.
Will gibberish detection flag valid fields like product codes or license keys?
It can, if those fields contain short alphanumeric strings the AI interprets as nonsense. To prevent this, go to the Rules section for any property that collects codes, IDs, or similar structured data and exclude it from gibberish detection before enabling the portal-level toggle.
Does gibberish detection cover sensitive data fields?
No. HubSpot has explicitly stated that sensitive data fields are not included in this update. Detection for those field types hasn't been shipped yet. Keep that boundary in mind when assessing your full spam coverage across complex forms.
