Connecti Gong & Hubspot Email Preference Centers

Hello!

One of the email preference centers we have in Hubspot is for one-to-one comms, however these are handled by Sales via Gong Engage.
I’d love for the two email preference centers to “speak” to one another, so that if someone (un)subscribes to one they also do that with the other.

Right now, the main way I have found of doing this is to create an extra field in each platform, which would trigger a workflow.
Is there a better solution?

For extra context: Currently HS and Gong aren’t integrated directly, they are both connected to Salesforce instead.

Hi @NikkoK,

Thanks for posting here!

Keeping two systems in sync like this can get tricky, especially with Salesforce sitting in the middle.

While we wait for some pure input, it could be worth checking out these articles that I’ve included below:

Tagging in some folks from the community for you!

Hey @danmoyle, @val_kouba, @EugeneAtKiwi – do you have any ideas for @NikkoK on how they could improve their flow?

Thanks!!

Sam, Community Manager

Thanks for tagging @stassey .

Hey @NikkoK , I’d say your current solution is possibly the best one in the current setup. If you connect HubSpot and Gong directly, the integration can sync opt-out status (though I’m not sure if that’s passed for a particular subscription type or as an opt-out from all communication).

With Salesforce it seems like the recommended setup passes a custom property and requires an automation in Salesforce to handle the real opt-out, so essentially it looks like your current setup.

Hi @NikkoK. This is an interesting question because we’re using multiple tools and trying to decide where the center of truth lies. I agree with @EugeneAtKiwi that your set up seems sensible and could probably work for the most part.

I also think there may be another option. Bear with me as I try to write out what I’m thinking.

Note to self: You might still need a HubSpot workflow to translate the relevant subscription status, but you shouldn’t need to recreate that automation in Gong. I believe Gong supports two-way opt-out synchronization with mapped CRM fields.

For the specific HubSpot subscription type covering one-to-one sales communications, I’d aim for: HubSpot subscription status ↔ mapped Salesforce field ↔ Gong email opt-out

The implementation I’m thinking about would look like this:

Configure Gong’s native opt-out sync. I found this path in Gong’s documentation: In Gong, go to Admin center → Engage → Compliance settings → Opt-out controls. You should be able to map an email-specific opt-out field for Salesforce Leads and Contacts, rather than using a global “Do not contact” flag that also affects calls. Gong documents this mapping as two-way.

Next, use that Salesforce field as the shared suppression flag. On the HubSpot side, your proposed mapped-property/workflow approach can translate between this flag and the relevant HubSpot subscription type. HubSpot’s “Manage communication subscriptions” workflow action can unsubscribe contacts from a specific subscription type. That keeps the custom automation concentrated on the HubSpot side rather than duplicating it in both systems.

Then, Check Gong’s enforcement settings, not just the mapping. Gong can be configured to allow one-off emails even when someone is opted out. If the intention is to stop all Gong sales emails, select the restriction that prevents sending emails and skips email flow steps.

I’d keep this scoped to the sales-communications subscription rather than treating a sales opt-out as an automatic unsubscribe from every HubSpot marketing subscription, unless that is explicitly what your preference language promises.

This makes sense in my head, hopefully it’s logical. I’d keep in mind a little semantic situation though, too: subscribing isn’t simply the reverse of unsubscribing. So I wouldn’t build this as “whenever either checkbox changes, make the other match.”

HubSpot’s subscription workflow action cannot resubscribe someone who previously opted themselves out. It can resubscribe contacts whose unsubscribe was set through certain account-side actions, including a workflow, but a self-unsubscribe requires the appropriate resubscription process.

So I’d separate the rules:

  • Opt-out: propagate suppression between systems.
  • Opt-in/resubscription: require an explicit preference change or other appropriate consent evidence—not simply a Salesforce checkbox being cleared.

That avoids a sales-side edit inadvertently being treated as permission to resume communications.

Hopefully that gives you another option for what you’re working on.

Hey Dan!

This is quite helpful, thank you for putting together.
I am currently experiencing some issue with my Gong access (not sufficient permissions, even though I have been given the correct access) so I can’t validate any course of action until that is fixed, but I will come back once I have the answer of how we have decided to proceed!