G2

Cameron B.

Senior Revenue Operations Manager

Computer Software

Mid-Market (51-1000 emp.)

10/21/2026

Business partner of the seller or seller's competitor, not included in G2 scores.

"GetResponse’s Consolidated Settings Sidebar Makes Compliance and Governance Easy"

4.5/5

What do you like best about GetResponse?

What I like best about GetResponse is its consolidated account details sidebar, where consent fields, login history, landing page domain management and security settings live in one view. As Senior Revenue Operations Manager for our Austin B2B software firm, I manage our outbound nurture workflows alongside HubSpot Sales Hub, and this organized settings panel cuts roughly three hours each week from my privacy validation and contact-list audit work. We run dozens of sales sequences for free-trial prospects, demo no-shows and churn-risk accounts, so clean opt-in tracking is non-negotiable under CAN-SPAM and CCPA, and GetResponse makes that governance far less manual.

I rely most heavily on the Consent Fields and Login History modules in this menu. The consent builder lets me create custom, required fields to log exactly why a prospect is receiving our messages. For example, we separate opt-ins for our technical webinar series, product update newsletters, and direct sales follow-up sequences. Every form capture stamps the contact with that consent source, timestamp and landing page domain. When a prospect submits a privacy request, I can pull a full consent trail directly inside GetResponse instead of stitching records together across form submissions, HubSpot activity logs and calendar scheduler notes. The Login History feed also helps me track which RevOps team members adjusted campaign settings, which is critical when multiple admins manage our sales automations.

The two-factor authentication toggle built here is another big win for our team security policy. I roll out MFA for every admin seat, and the layout makes onboarding new RevOps contractors simple. The core account details panel locks our sending identity, business address and currency settings, preventing junior sales ops staff from accidentally modifying our sender information or physical address required in every commercial email by CAN-SPAM. Before launching GetResponse, I spent time every week checking every active sequence to confirm our mailing address was correctly placed in footers; now the account-level business details feed automatically into templates.

One unexpected benefit I’ve found is the Predefined Text tool. I store our approved unsubscribe language, CCPA disclosure copy and webinar disclaimer text here. Any sales rep building a quick nurture email sequence pulls from these locked snippets, so there’s no variation in our compliance wording. Before this, sales team members would draft unsubscribe language on their own, creating inconsistent disclosures and opening us up to compliance risk. The landing page domain management on this same sidebar also speeds up our campaign rollouts. When we spin up a gated whitepaper or benchmark report capture page, I can confirm the branded domain is active and validated without jumping to a separate tool.

Suggestions: My top request is deeper native sync with HubSpot Sales Hub, so consent status, email engagement and unsubscribe events push bidirectionally to our CRM contact records automatically. I also want more granular audit logs for consent edits, contact exports and setting changes, with webhook support to feed events into our BI reporting. Finally, role-based permission controls would let junior team members build email sequences without giving them access to modify core account identity, MFA or global consent rules. Review collected by and hosted on G2.com.

What do you dislike about GetResponse?

What I dislike most about GetResponse is its rigid, coarse-grained team permission model, paired with incomplete bidirectional sync with HubSpot Sales Hub and shallow audit logging for consent changes. As Senior Revenue Operations Manager for our Austin B2B software company, I manage nurture sequences, free-trial follow-ups and churn outreach while upholding CCPA and CAN-SPAM rules, and these gaps force me to build clunky manual checkpoints every week to avoid privacy missteps and bad CRM data.

The role permissions are my biggest pain point. The built-in user access tiers don’t give me granular scoping; there is no clean way to let a junior RevOps analyst build email sequences and review campaign reports without granting them the ability to edit core consent fields, modify sender identity settings or alter landing page domain configurations. Our team has contractors who help draft webinar nurture emails, but I cannot isolate their access. If I give them campaign builder rights, they can touch the compliance rules that live in the account details sidebar. If I lock those critical settings down, they can’t edit sequences at all. This forces me to either over-provision access, which creates privacy exposure risk, or absorb all sequence edits myself, adding hours to my weekly workload. Last month, a contractor accidentally edited our global consent field label, which would have broken our opt-in audit trail if I hadn’t caught it during my end-of-week compliance review.

The native HubSpot integration is another major limitation. The sync only pushes basic contact names and email addresses one way in many scenarios; consent status, unsubscribe events and email engagement metrics do not reliably flow back into HubSpot contact records. We rely on HubSpot for pipeline reporting, call recording logs and CPQ quote tracking, so our sales reps rely on CRM contact timelines to judge prospect engagement. When a prospect unsubscribes in GetResponse, that status often fails to populate HubSpot automatically, leaving reps unaware and at risk of sending follow-up messages that violate CAN-SPAM. I have to run weekly CSV exports from GetResponse, clean the files, then manually import them into HubSpot, a repetitive process that eats into my pipeline hygiene time.

The login history and consent change audit trails are far too limited for our regulatory needs. The platform logs basic sign-ins, but it does not capture discrete actions like consent field edits, contact list exports, unsubscribe events or changes to predefined compliance text. When a prospect submits a CCPA data access request, I cannot pull a single timestamped report showing every modification made to their opt-in record. I have to cross-reference campaign timestamps, export logs and my own change notes, piecing together an audit trail that regulators might view as incomplete. This adds significant overhead during quarterly privacy audits.

The final frustration is inconsistent webhook reliability. Unsubscribe and consent-update webhooks occasionally time out without alerting me, so downstream workflows in our BI dashboards miss critical privacy events. There is no built-in retry dashboard to surface failed events, which means I discover broken syncs only when I manually validate reports.

Suggestions: First, introduce modular permission roles, so I can separate sequence building, reporting access and consent/account setting controls. Second, rebuild the HubSpot integration for true bidirectional sync of consent, unsubscribe and engagement data. Third, expand audit logging to capture every consent edit, export and setting change with exportable, timestamped records. Finally, add a webhook failure queue with alerts so broken privacy event syncs don’t slip unnoticed. Review collected by and hosted on G2.com.

What problems is GetResponse solving and how is that benefiting you?

Before adopting GetResponse, our prospect nurture emails were split across disjointed tools and ad-hoc HubSpot workflows. We struggled with scattered consent records, inconsistent CAN-SPAM footer language, and no single place to log and validate opt-in intent, but now we can build segmented nurture sequences and centralize all consent documentation in one platform, which has resulted in roughly four hours saved every week on CCPA and CAN-SPAM compliance checks and contact data cleanup.

Back then, our RevOps team relied solely on native HubSpot email workflows for post-demo follow-ups, free trial nurture and churn-risk outreach. We had no dedicated space to define separate consent categories. Prospects who opted in for webinars were mixed together with people who only agreed to receive product newsletters. Our sales reps would sometimes send the wrong messaging to contacts, and we had no reliable way to prove exactly what each prospect consented to receive. Every quarter when we ran our privacy audit, I had to pull records from HubSpot form logs, meeting scheduler entries and manual spreadsheet notes to reconstruct opt-in histories. It was slow, error-prone, and created risk that we would fail to demonstrate compliant contact handling for regulators.

We struggled to keep unsubscribe language and required mailing address consistent across dozens of active sequences, but now we can lock approved compliance text in the Predefined Text panel, which has resulted in far fewer accidental non-compliant email sends. Before GetResponse, anyone building a sequence typed footer copy from scratch. Minor variations in wording or missing physical addresses put us at risk of CAN-SPAM violations. Now all our email templates pull from these saved, approved snippets, so every outbound message automatically includes our required disclosure and unsubscribe link. This also reduces the time I spend auditing every new sequence before it goes live.

We struggled to track who was modifying campaign and consent settings, with no clear login and activity trail for our multi-admin RevOps team, but now we can review Login History from the account settings sidebar, which has resulted in better accountability when we troubleshoot unexpected changes to our nurture campaigns. When we onboard contract support staff to help build webinar sequences, I can check the log to confirm who accessed the system and when. While the logs don’t capture every granular edit, it gives us a baseline layer of visibility we did not have before.

We struggled to manage gated content landing pages separately from our email nurture stack, but now landing page domain management lives alongside consent and account details, which has resulted in faster campaign rollouts for our whitepapers and technical benchmark reports. Instead of juggling a separate landing page tool and manually importing leads into HubSpot, the leads captured on GetResponse pages flow into contact lists for nurturing. Even though the HubSpot sync has limitations, it still cuts down on manual CSV imports that we used to run multiple times per week.

Suggestions: I still need a fully bidirectional HubSpot Sales Hub sync for consent and unsubscribe events. More granular, exportable audit trails for consent edits and contact exports would strengthen our CCPA audit packets. Role-based permissions would let junior team members build sequences without access to critical compliance settings. A webhook retry queue with alerts would also help us catch failed data syncs before bad contact data lands in our CRM pipeline. Review collected by and hosted on G2.com.