HubSpot Marketing Hub

Marketing Hub runs lead capture, segmentation, campaign reporting and automated followup on HubSpot's shared CRM. Breeze adds writing, research and personalization to that operating model. The Nurture Agent beta can rewrite subject lines, preview text, calls to action and email bodies for selected recipients using CRM context and web research. It consumes credits and applies to published automated marketing emails. Forms, contact properties, workflow branches and ordinary email programs remain useful without it, so AI extends the marketing system rather than constituting the entire product.

Workflow publishing requires the relevant permission, and users can turn workflows off individually, in bulk or on a schedule. Turning one off blocks new enrollment and skips actions for existing records rather than freezing every contact at its current step; delays and branch evaluation continue, and skipped actions do not replay. Enterprise adds email approvals, so a marketing email can require sign off before it sends.

Nurture Agent, in beta on Professional, has its own controls through recipient percentages, credit limits and an off switch. These govern future execution without reversing messages or record changes already completed.

Breeze uses HubSpot models alongside models from OpenAI, Anthropic and Google for generation and related AI functions. Nurture Agent draws on CRM data and web research to personalize an existing automated email, while model controls address data retention and external training. The AI settings distinguish CRM records, customer conversations and files as separate input sources. Which model rewrites a given recipient's email is not disclosed. The input controls distinguish what an assistant can access from which model processes a particular request.

Reed reports more than 13,000 website leads in one year after adopting HubSpot, along with faster routing to the appropriate recruitment consultant. Its implementation combined Marketing Hub, Sales Hub, Service Hub and a custom connection to an internal CRM. Content downloads and webinar interest triggered relevant followup, while channel reporting guided advertising and search investment. The result has a named customer, a lead count and a time window, but does not isolate Marketing Hub's contribution from the wider platform rollout, integration work or changes in marketing strategy.

Marketing forms can collect consent, and contact records carry subscription and suppression information into campaign selection. The messaging policy requires verifiable permission, accurate sender identity and a simple unsubscribe route, with requests processed within 24 hours. It also separates purely transactional communication from marketing content. The account rules govern delivery and enforcement, while the sender remains responsible for permission collected before an import. A customer's lawful basis, tracking notices and consent records still have to match the audience and channels used in each program.

The DPA separates customer directed processing from uses where HubSpot acts as a controller, including parts of enrichment. Customers can retrieve, correct, restrict and delete personal data, with additional assistance available when the product controls are insufficient. Transfer terms include the Data Privacy Framework and current EU standard contractual clauses. The supplier roster identifies services, providers and processing locations, including AWS, Google, Snowflake and OpenAI.

Enrichment outputs still require a lawful basis, and regional hosting does not prevent every support or supplier transfer outside that region. Enterprise Sensitive Data properties add application layer encryption and restricted access. Their values cannot be used in personalization tokens, sandboxes, chatbots or playbooks.

Campaign audiences can combine CRM records, form submissions, website activity and enrichment. Those inputs have different origins: a submitted form is a direct interaction, while enrichment adds information under separate product terms. HubSpot treats parts of its enrichment service as controller processing and requires deletion of enrichment outputs when the customer lacks an independent lawful basis. Turning off model training does not turn off enrichment, because the settings govern different data uses. No provenance record or indemnity is offered field by field for enrichment or imported lists.

Marketing Hub connects advertising accounts and CRM systems through supported integrations, an app marketplace and APIs. Advertising audiences still need the right account access and must follow each network's conditions. The Salesforce connector synchronizes records by mappings and inclusion rules instead of automating a seller's browser session.

Third party applications carry their own permissions, processing and service limits, so the integration surface is a conventional connection model without a blanket conformance guarantee for every installed app. Ad management is included from Starter, so paid audience sync does not require a higher edition.

Third party AI providers cannot use customer data for model training, with zero retention applied wherever possible. HubSpot's own model training has a separate account setting that is on by default. Super Admins can opt out without losing AI features; the change applies prospectively and does not remove data already used in a trained model. Accounts using Sensitive Data are excluded from training and cannot opt in. Separate toggles control access to CRM, conversation and file inputs, making training permission distinct from access during an AI task.

Nurture Agent can alter the wording of an automated email for a selected share of recipients while preserving the campaign's sender identity. Personalization tokens and smart content continue to operate, although the agent can rewrite surrounding text. HubSpot's messaging rules prohibit misleading people about whether they are interacting with a human or an automated system and require AI disclosure where the law requires it. HubSpot adds no automatic label for recipients and has not described its Article 50 approach. The policy obligation is separate from a default product label on every generated message.

Salesforce integration covers contacts, companies, deals and tickets through the corresponding Lead or Contact, Account, Opportunity and Case objects. Engagements can become Salesforce tasks, and custom objects have their own synchronization options. Inclusion segments and field mappings determine which records and values move. The CRM APIs provide current and historical properties, associations, batch operations and paginated retrieval, with separate calls for some association data. This gives an operations team both packaged synchronization and programmable access, while requiring it to manage connector permissions and data mappings deliberately.

HubSpot hosts accounts on AWS in the United States, Germany, Canada and Australia, with backup replication inside the selected regional hosting location. Paid accounts can change data centers; free accounts need an upgrade for that move. The region covers the core account's storage and processing, not every connected activity. Support, analytics, enrichment, apps and some suppliers can process data elsewhere. These boundaries matter when a marketing team chooses a region for its contact database. There is no customer operated or dedicated tenant edition on offer.

The platform holds SOC 2 Type II and SOC 3 assurance, backed by annual penetration testing, incident response and a vulnerability reporting program, and Marketing Hub sits inside that scope rather than borrowing an infrastructure provider's certificate. The trust program offers current reports and questionnaires for a security review through its access process. HubSpot itself is not ISO 27001 certified, although AWS is.

Coverage of newly released and beta features is left open, which matters because Content Agent, Nurture Agent and Marketing studio are still in beta on Professional. Enterprise adds controls that limit access to content and data by team.

Starter lists at $20 per seat a month with 1,000 marketing contacts and 500 HubSpot Credits, and new customers can currently start from $7 a seat on annual billing. Professional costs $890 a month on an annual commitment paid monthly, or $800 paid annually, with three Core Seats, 2,000 marketing contacts and 3,000 credits; extra seats start at $45. Enterprise starts at $3,600 with five seats, 10,000 contacts and 5,000 credits.

Required onboarding costs $3,000 for Professional and $7,000 for Enterprise. Contact tier increases apply immediately and cannot be reversed midterm by shrinking the audience, and extra AI credits cost one cent each.

Exports cover CRM records, form submissions, campaign data, email results and unsubscribes. Workflow exports provide a spreadsheet inventory or an image of a flow; they exclude workflow history and performance data and are not a portable executable campaign. Professional and Enterprise customers can request data retrieval within 30 days after termination, with possible reactivation or assistance fees. The DPA separately addresses deletion and protected backup copies. A migration therefore needs several exports and replacement of embedded assets, rather than relying on a single complete account archive.

Marketing Hub supports domain authentication and changes the From address to a HubSpot managed domain when the sending domain is not connected. Enterprise adds a rolling frequency safeguard for regular, automated and blog emails. Transactional messages, individual emails, surveys and inbox conversations fall outside that cap, and a marketer can exempt a particular send. Account monitoring adds throttling and enforcement when sending patterns indicate abuse. These controls support audience discipline, but the frequency setting is neither universal across editions nor a single ceiling for all customer communication.

Marketing Hub serves small teams through enterprise marketing operations, with editions spanning basic email and forms through broader workflow and campaign management. Reed's recruitment implementation shows B2B lead routing across a large organization while preserving a proprietary CRM. The same platform can support marketing, sales and service teams, but those hubs have separate subscriptions and access requirements. Buyers can use the shared CRM or integrate another sales system. Regional hosting and a partner ecosystem broaden deployment choices, while local services and every channel's availability still depend on the account arrangement.