Marketing Automation Software Resources

Say marketing works in HubSpot Marketing Hub and sales lives in Salesforce: I'm writing a piece on which campaign data needs reconciling by hand between the two. Contact records and activity are the side that lines up, with emails and calls logged against the right contact. Campaign metrics split by campaign and user are what teams reconcile by hand or report on from the Salesforce side, and where the sync runs one way from Salesforce, contact management moves into manual updates too.

Going by reviews, the connection earns its place through closed-loop reporting that ties revenue back to the campaign. In marketing automation, the deciding factor seems to be where a team keeps its source of truth for revenue. Teams that report campaign revenue in HubSpot get the most from a two-way setup, while teams that live in Salesforce reporting tend to treat some reconciliation as part of the arrangement rather than a gap in it.

Questions for anyone running both:

• Which campaign metrics do you still pull together manually?
• Do you report campaign revenue in HubSpot or in Salesforce?
• Did you start one-way and move to two-way, or the reverse?

What would you set up differently if you were connecting them again?

A question I keep coming back to is what HubSpot Marketing Hub teams do when the workflow logic they need goes beyond the standard filters. The visual builder handles if/then branches that route contacts down different email paths without code, and when a case falls outside the filter options, the workaround that comes up on G2 is a contact property used as a flag: one workflow sets it, and other workflows filter on it. That covers cases like stopping someone from answering the same survey twice.

Across marketing automation setups, the situations seem to split three ways:

1. A single campaign with clear branches. The standard filters cover it, and the builder is quick to work in.
2. Logic that depends on something that happened earlier, like a survey answer. A property flag carries that state between workflows.
3. Several people building on the same account. Controlling who can build or change which workflows becomes the setup question, along with keeping duplicate contacts and companies out of enrolment.

Builders tend to lean either towards visual simplicity or towards open-ended scripting, and HubSpot sits on the visual side, which suits teams where marketers rather than developers own the workflows. The flag pattern is how those teams extend it without leaving that model.

For anyone running property flags, how do you keep track of what each one means? And who on your team owns that naming?

I've been trying to work out how marketers handle segmentation in HubSpot Marketing Hub without rebuilding lists every few months, and most of it comes down to the active or static choice made when a segment is created. HubSpot now calls lists segments: an active segment keeps adding and removing contacts as they meet its filters, a static one is a one-time snapshot, and a static segment built with filters can be converted to active later instead of being rebuilt.

Reading recent G2 reviews, rebuilding tends to happen in two situations: putting together a quick segment with several criteria on the fly, and cleaning up after a year of sends when it isn't clear which older lists still feed a workflow. The filter depth behind that is also what people value most here, splitting contacts on several criteria for a targeted email, suppressing a specific list from a send, and using AI-assisted audience building to find high-intent groups. For marketing automation teams, that depth is exactly why segment counts grow.

What I'd like to compare notes on:

• Do you default to active segments and keep static ones for one-off sends?
• How do you name or folder segments so they're still findable a year later?
• How do you check which workflows depend on a segment before deleting it?

And has anyone converted a static segment to active instead of starting over?