HTS-only Salesforce sync with event automation
The strategy we mapped
We started by narrowing the Salesforce integration to HTS records only, since the default sync was pulling in unwanted data that skewed HubSpot metrics. The team needed to filter companies and deals on inbound fields–HTS Sales Region or HTS Account Industry for companies, and HTS Category for deals–while protecting the Marketing Contacts quota by ensuring Salesforce-synced contacts arrived as non-marketing by default. Contacts presented a separate challenge: most were not tracked consistently in Salesforce, so we synced only those tagged as HTS and built a workflow to propagate deal stage changes up to the associated company lifecycle, then down to all related contacts. Once the Salesforce connection and filters were stable, we turned to the event platforms: we built Zapier flows to automatically capture registrations and attendance from Crowdcast webinars, and we initially scoped a Swapcard connection for new attendee connections until the team determined individual account structures made that flow unsuitable.
The solutions we executed
The Salesforce integration syncs companies, deals, and contacts from Salesforce to HubSpot using filters to ensure only HTS-relevant records arrive. Companies and deals are tagged with HTS identifiers–either HTS Sales Region or HTS Account Industry for companies, with deal filtering by HTS Category–and the team created segments to review any non-HTS records for safe bulk deletion. Contacts from Salesforce sync only if they carry HTS markers and arrive as non-marketing by default to protect quota limits. A workflow automatically propagates company lifecycle stage (based on the highest-stage deal) to all associated contacts and keeps HubSpot and Salesforce in sync.
The Crowdcast integration automatically captures five separate webinar events: registration, live attendance, missed attendance, replay views, and CTA button clicks. Each trigger flows into HubSpot so the team can update existing contact records or create new ones, with all webinar activity tracked in the engagement feed for downstream nurture and reporting. We built the Zapier flows to match the data shape coming from Crowdcast so field mapping stays consistent as the team tracks which prospects engage with which content.
The Salesforce integration also includes a one-way sync where Salesforce is the authoritative source for contact names and other mapped fields, ensuring both platforms stay aligned without manual rework. The team identified specific contact names that were pulling in with formatting issues–all caps or nicknames–and the integration was configured so corrections made in Salesforce reflect back into HubSpot automatically, with a provision for two-way sync on names only if needed down the road.
What changed after the engagement.
The Salesforce integration now syncs only HTS-relevant companies, deals, and contacts to HubSpot using filters on sales region, account industry, and deal category, eliminating unwanted data that previously skewed metrics. Contacts from Salesforce arrive as non-marketing by default to protect quota limits, and a workflow automatically propagates company lifecycle stages to associated contacts, keeping both platforms synchronized. The Crowdcast integration captures five distinct webinar actions–registration, live attendance, missed attendance, replay views, and CTA clicks–flowing each into HubSpot so the team updates existing records or creates new ones, with all activity tracked in the engagement feed for downstream nurture and reporting. Contact name corrections made in Salesforce now sync back to HubSpot automatically, allowing the team to fix formatting issues without manual rework.
Want results like these?
Tell us where your revenue engine is stuck — we'll map the fix in one call.