HubSpot
CRM integration
A verdict on every contact, inside HubSpot.
FormGuard checks each submission as it arrives and writes a verdict, a score and the reasons into a FormGuard property group on the contact. Lifecycle stage, owner and every property your team uses stay yours; your workflows and lists do the rest.
NOTHING DELETED
Next
User
Daniel
Lena
Checking
Amira K.
Acme · Paid search
amira.k@example.com
Phone
555-0134
Source
Paid search
Company
Acme
Behaviour
Contact
Consistency
Record
About this contact
Amira K.
Acme
FormGuard
Verdict
Score
Reasons
Checked at
Reference
Lifecycle stage
Contact owner
not written by Tapper
five fields on the Contact, nothing else
Illustrative submissions with generic names, in the layout of the FormGuard intake view with the HubSpot contact record.
The verdict belongs where your team does its work.
Verdict, score and reasons land on the contact record your reps open anyway. Nobody checks a second dashboard, and nothing about how your team works in HubSpot changes.
01
The verdict beside the contact, not in another tool
Verdict, score and reasons sit in a FormGuard property group on the contact record your team opens anyway, beside lifecycle stage and owner. Nobody opens a second tool to learn which submissions were never a person.
02
Reasons you can filter and report on
The reasons are a fixed vocabulary in a multiple-checkbox property, never free text. Active lists collect on them, reports count them, and a rep can see at a glance why a contact was marked Suspicious.
03
Your rules, HubSpot tools
Workflows enrol on the verdict or on a score threshold you choose, active lists collect Suspicious contacts for review, and lead rotation reads the verdict before it assigns an owner. The routing is yours and it stays in HubSpot.
04
A fixed property set, written down before it is written
Five properties in one group on the contact, listed in the disclosure your admin reviews before anything is written. Nothing else on the contact is written, and lifecycle stage is never set by Tapper.
From the form to the Contact record, in three layers.
What leaves Tapper on this path is five fields going back into your own HubSpot.
Your form
on your site, unchanged
Tapper FormGuard
CHECKS
Behaviour · Contact · Consistency
passive, no challenge for the visitor
WRITES
verdict · score · reasons · checked at · reference
nothing else on the record
HubSpot
the Contact record
SCOPED OAUTH
Nothing typed into the form is stored in the clear. Five fields go back to your own HubSpot. Nothing else leaves.
Connect
01
Your admin authorises a scoped OAuth connection limited to contact records and the FormGuard property group. The scope is the disclosure, read before anything is written.
Check
02
Three layers on every submission: the session, read by the same monitoring script Block uses; the email and phone, normalised and hashed at ingest; and whether the two agree. No CAPTCHA, no extra step for the visitor.
Write
03
Verdict, score, reasons, checked at and a reference land in the FormGuard property group on the contact. Lifecycle stage, contact owner and every other property stay yours.
Route
04
Hold an Invalid submission before it reaches your team, or let every contact land flagged and let workflows, active lists, views and lead rotation act on the five properties.
A write, and a narrow one.
The connection is scoped to contact records and the FormGuard property group. FormGuard writes its own five properties and nothing else, and the scope is listed in the disclosure your admin reviews before anything is written.
A lead your team can trust before they dial it.
The point is not another dashboard. It is that the list your reps dial and the count your reports show are built from enquiries a person made.
Genuine enquiries reach a rep first
Lead rotation receives the contacts that passed all three layers, so the morning call list starts with enquiries a person made.
Suspicious contacts wait in a list, not in the rotation
A throwaway address or an implausible number lands in an active list for review with its reasons attached, and a person decides instead of a sequence.
Reports count what was real
Contact reports and dashboards filter on the verdict, so the count your team is measured against is the count of genuine enquiries, and junk stops inflating it.
Nothing is deleted, merged or archived
An Invalid contact is held or flagged, never removed. It stays in your portal with its five properties, reviewable at any time, and every record remains yours.
CONTACT ROUTING BY VERDICT
NOTHING DELETED
Workflow: hold
kept and reviewable, never deleted
Active list: review
lands with its five properties
Lead rotation
Amira K.
Genuineowner assigned by your rules
TOOLS
Illustrative: the intake submissions routed by verdict, with HubSpot's own tools.
Five fields written, a named set read, and written down.
Scope is a fixed list. The write is the one difference from a read-only connection and it is listed as such. Any CRM gets its own disclosure before it is connected.
PERMISSIONS AS THE DISCLOSURE LISTS THEM
Contacts (the properties it checks, hashed at ingest)
READ
Form submission context (which form, which page, the click id the form stored)
READ
Contacts (five properties)
WRITE
Deals
NEVER
Tickets
NEVER
Notes, emails and calls
NEVER
Custom objects
NEVER
Free text
NEVER
PII AT INGEST
j.doe@example.com
Scope is fixed in code and listed in your disclosure.
Scope, as the disclosure your admin reviews lists it
Objects read
Contacts: the properties FormGuard checks, hashed at ingest, and the submission context HubSpot keeps with them: which form, which page, and the click id your form stored. Never the free-text fields of the submission; no deals, tickets, notes, emails, calls or custom objects.
Fields written
Five properties in a FormGuard group on the contact: verdict, score, reasons, checked at and reference. No other property, no lifecycle stage, no owner, no other object.
Scope
A scoped OAuth connection limited to contact records and the FormGuard properties. Nothing else is requested, and disconnecting revokes the token.
PII handling
Email and phone are normalised and hashed with SHA-256 at ingest, and the raw values are never persisted: not in the database, warehouse, logs or queue messages.
Data out
Only the FormGuard properties, back to your own HubSpot portal. No email, phone, hash, name or record content goes to any third party.
Storage
Per-customer stores, never pooled across customers. Credentials are encrypted with AES-256-GCM at rest, and disconnecting revokes the token and deletes them.
Deletion
Never. Nothing in your HubSpot portal is deleted, merged or archived by Tapper.
A configuration step, not a project.
No code on your side, no change to how your team works in HubSpot. Your admin authorises the connection and we agree the field set in writing.
Agree the field set
01
We confirm the five properties in the FormGuard group on the contact and the values your active lists and reports will filter on. All of it is written into your disclosure.
Confirm click capture
02
HubSpot keeps the form and page of every submission. Where a hidden field also stores the ad click id, the verdict sits beside the click that produced it; the field is optional and no form change is required.
Authorise the connection
03
Your admin authorises a scoped OAuth connection limited to contacts and the FormGuard property group.
Review verdicts before any hold is switched on
04
Every submission lands flagged with its five properties while we read the verdicts with your team and settle the score threshold. Hold is switched on only when you decide.
Frequently asked questions
The questions security and CRM teams ask before connecting.
Five properties in a FormGuard group on the contact: verdict, score, reasons, checked at and a reference id. Nothing else on the contact is written.
The contact properties it checks, hashed at ingest, plus the submission’s context: which form, which page, and the click id your form stored.
Never the free-text fields of the submission, and no deals, tickets, notes, emails, calls or custom objects.
No. Lifecycle stage, owner and rotation stay yours. Workflows read the verdict and score and do what you tell them.
Enrol a workflow on the verdict or on a score threshold you choose, collect Suspicious contacts in an active list for review, and let the rep’s view carry the three fields.
Sequences and notifications are yours to wire.
No. HubSpot keeps the form and page of a submission on its own; a hidden click id field is the same convention as on Salesforce and is optional.
No. Per-customer stores, never pooled, and never used to train another customer’s models.
At any time. Disconnecting revokes the token and deletes the credentials. Properties written before you disconnect stay on your contacts.
Nothing new. No CAPTCHA and no extra step; the checks are passive.
Put a verdict on every contact in HubSpot.
We walk through the field set, the two modes and your routing rules with your CRM and security teams before anything is connected.
FormGuard for Salesforce
The same three layers and the same five fields, in Salesforce’s own vocabulary.
