Predictions get stranded
Most platforms generate scores and leave them in their own UI. Moving them into the CRM is a separate engineering project.
Wave · HubSpot Enrichment
Seven smart fields on every contact, native in HubSpot.
Wave provisions seven contact properties in HubSpot and keeps them current automatically. Your workflows, lists, and reps get smarter the moment Wave runs, with no pipeline to build.
Quick answer
Wave automatically populates seven native HubSpot contact properties on every scoring cycle: predicted inbound channel and promotional channel, preferred content format, buying-group role, the next content theme, the preferred send window, and the target cadence interval. There is no data warehouse, Zapier, or webhook work; the moment Wave runs, every HubSpot workflow and rep view is already smarter.
Key capabilities
- Seven native HubSpot contact properties
- Auto-provisioned on setup
- Updates on every scoring cycle
- Read-before-write dedupe, no wasted API calls
- Full writeback audit with one-step rollback
- Per-tenant, per-field kill switches
- Configurable property name mapping
Last updated June 2026
The problem
Great insight that never reaches the CRM is just a dashboard.
The missing link in most intelligence deployments is activation. You buy a smart platform, then spend months trying to pipe its output into the tools where reps and automation actually live.
The middleware tax
Teams wire up Zapier, webhooks, or a warehouse sync just to get insight onto the contact record. It breaks and needs babysitting.
Reps never see it
If a prediction is not on the record the rep opens, it might as well not exist.
How Wave does it
Seven fields, provisioned and kept current.
Wave writes its predictions straight onto the HubSpot contact record as standard properties, governed and auditable.
- 01
Provision the fields
Wave sets up the seven contact properties in your portal on setup. There is no manual field creation.
- 02
Write on every cycle
Each scoring run updates the fields. Wave reads the current value first and skips the write when nothing changed.
- 03
Govern every write
Every write is logged with the previous and new value. Per-tenant kill switches let you pause any field without touching the others.
- 04
Activate in HubSpot
Filter lists, enroll sequences, route workflows, and brief reps using fields that fill themselves.
Where it fits
Built to write back, not just predict.
Wave was designed from day one to make HubSpot the activation surface. Each property maps cleanly to the product that produces it.
Wave
HubSpot
Your campaigns
For the technical reader, the seven fields are tw_predicted_inbound_channel and tw_predicted_promo_channel from Channel Affinity, tw_predicted_engagement_channel (the preferred content format) from Engagement Channel, tw_buying_group_role and tw_next_theme from Buying Groups, and tw_predicted_send_window and tw_predicted_cadence_days from Cadence Affinity. You can rename any of them to match fields you already use. Writeback is HubSpot today, with Marketo next.
Works alongside Channel Affinity, Buying Groups, Cadence Affinity.
Why Wave is different
Activation is a product behavior, not a services project.
Ask any competing platform how many HubSpot fields it populates, how fast, and with what audit trail. For most, moving predictions into the CRM is a custom build.
Most tools
Wave
Predictions live in the vendor's dashboard; you build the CRM sync.
Wave ships the writeback as a built-in behavior, with no middleware.
Writes overwrite silently, with no history.
Every write is logged with before and after values, and rolls back in one step.
All-or-nothing enrichment.
Per-tenant, per-field kill switches let you enable products one at a time.
Unchanged values still burn API calls.
Wave reads first and skips the write when nothing changed.
FAQ
Questions buyers ask about Wave's HubSpot enrichment.
What does Wave write to HubSpot?
Seven native contact properties: predicted inbound channel and promotional channel, preferred content format, buying-group role, the next content theme, the preferred send window, and the target cadence interval. They update automatically on each scoring cycle.
Do I have to create the fields myself?
No. Wave provisions the properties in your portal on setup, so there is no manual field creation. You can rename them to match fields you already use.
Does this need a data warehouse or Zapier?
No. Wave writes directly to HubSpot through the official app connection. There is no warehouse, no Zapier, and no webhook engineering required.
Can I see and undo what Wave wrote?
Yes. Every write is recorded with the previous value, the new value, and the model version that produced it. You can roll any write back in one step.
Can I turn individual products off?
Yes. Per-tenant, per-field kill switches let you enable Channel Affinity writeback first, add Buying Groups later, and control Cadence Affinity separately. There is no all-or-nothing dependency.
Will Wave spam the HubSpot API?
No. Wave reads the current property value before writing and skips the call when the value has not changed, so only real changes produce a write.
Does Wave write to Marketo or Salesforce?
Writeback is HubSpot today, with Marketo next. Wave reads from HubSpot, Snowflake, and secure file upload now, with Marketo and Salesforce in progress.
How do I see this on my portal?
Book a 20-minute walkthrough. We will show the seven properties Wave would populate and how your existing workflows would use them.
See it on your data
See seven smart fields in your portal.
Book a 20-minute walkthrough. We will show the contact properties Wave would populate and how your sequences and reps would use them.
Request a demo Download the one-pager (PDF)