Integration guide

HubSpot and Gmail: What Gets Logged and What Gets Missed

The Gmail integration is two features with confusingly similar names — logging and tracking — plus a sidebar that quietly becomes the reason reps stop opening the CRM at all.

Connector
Native — HubSpot Sales Chrome extension plus an inbox connection in HubSpot settings
Sync direction
Two-way: outbound mail logs to the CRM, CRM context renders inside Gmail
Setup time
15 minutes per user
Availability
Logging, tracking and the sidebar are free; sequences and some template limits require Sales Hub Starter or above
What moves between HubSpot CRM and Gmail
What Direction Detail
Outbound email Gmail → HubSpot With Log ticked, the message body lands on the contact's timeline and the associated company and deal. Untick it and the email happens invisibly.
Open and click events Gmail → HubSpot Track is a separate checkbox that inserts a pixel and rewrites links. Notifications fire in the browser and optionally in Slack.
Inbound replies Gmail → HubSpot Replies to a logged thread attach to the same record automatically, provided the thread is unbroken and the reply comes from a known address.
Contact creation Gmail → HubSpot New recipients can auto-create contacts. Left on by default it fills the CRM with vendors, recruiters and your own colleagues.
CRM sidebar HubSpot → Gmail Company, deal stage, recent activity and open tasks render beside the thread, plus one-click task and meeting creation.
Templates and snippets HubSpot → Gmail Inserted straight into the compose window with personalisation tokens resolved from the contact record.
Meetings links HubSpot → Gmail The scheduling link inserts inline; bookings create a meeting on the contact timeline and on the connected Google Calendar.
Sequence enrolment Gmail → HubSpot Reps can enrol a contact into a sequence from the sidebar. Sales Hub Starter and above.

Setting it up

  1. Install the HubSpot Sales Chrome extension, then connect the personal inbox in HubSpot under Settings → General → Email. Both halves are required; installing only the extension is the most common half-setup.
  2. Set the account-wide default for Log and Track before rolling out to reps, and explain the difference once, clearly, because nobody reads the tooltip.
  3. Configure the never-log blocklist immediately — your own domain, recruiting domains, and any vendor domains — under the email logging settings.
  4. Connect Google Calendar in the same settings screen so meetings booked from Gmail write back to the contact timeline rather than sitting only in Calendar.
  5. Move any shared alias (support@, hello@, sales@) into the Conversations inbox instead, and connect it as a team email channel.
  6. Audit a week later: filter contacts created in the last seven days by source and see what the blocklist missed.

Where the integration stops

  • Log and Track are independent, and the defaults are per-user. A rep who unticks Log to send a personal note and forgets to re-tick it stops logging entirely, silently, for weeks.
  • Tracking breaks on plain-text and on some corporate mail gateways. Security scanners fetch images and rewrite links, which produces phantom opens seconds after send. Treat single opens as noise and repeat opens as signal.
  • Auto-create contacts needs a blocklist on day one. Without one, your contact count — and on paid tiers your marketing contact bill — grows from every recruiter who emails a rep.
  • Forwarded threads and altered subject lines lose their association. HubSpot matches on thread ID; break the thread and the reply lands nowhere.
  • A shared team alias is not a Gmail connection. support@ or sales@ belongs in the Conversations inbox as a shared channel. Connecting it as a personal inbox logs the whole team's mail under one user.

Why this integration matters more than it looks

Every CRM rollout has the same failure mode: reps live in the inbox and the CRM slowly becomes a place data goes to die. The Gmail integration is HubSpot's answer to that, and the thing that makes it work is not logging — it is the sidebar.

Logging is a compliance feature. It makes the manager's reporting real. The sidebar is what makes a rep prefer having the integration on, because deal stage, last touch, open tasks and templates are right there in the thread they were already reading.

The setting that decides your data quality

Auto-create contacts. It is on by default, it feels harmless, and six months later your database has three thousand contacts nobody ever intended to market to. On Marketing Hub, where pricing keys off marketing contacts, that becomes an invoice rather than an inconvenience.

Set the blocklist first, then turn logging on. In that order.

Where the tracking data actually helps

Not on individual opens — corporate security gateways generate too many false positives for a single open to mean anything. Where it earns its place is pattern: a proposal opened four times across two days, by a thread that then goes quiet, is a genuine signal that it is circulating internally. That is the moment a follow-up lands, and it is the one thing the integration tells you that the CRM alone cannot.

Frequently asked questions

What is the difference between Log and Track in the HubSpot Gmail extension?
Log writes a copy of the email onto the CRM record, so the history is visible to everyone on the team. Track adds an open-and-click pixel and notifies the sender when the recipient opens it. You can use either, both or neither, and the two checkboxes sit next to each other in the compose window — which is exactly why they get confused. If you only enable one across the team, make it Log; open data is interesting, but a CRM with no email history is a CRM nobody trusts.
Does HubSpot read my whole Gmail inbox?
Only what you log, plus replies on threads that are already logged. HubSpot requests Gmail scopes broad enough to send and read messages in order to associate replies, but it does not index and store your entire mailbox onto records by default. Teams with strict data policies usually restrict this further by turning off auto-create and by blocklisting internal domains.
Can two reps log the same thread?
Yes, and it deduplicates on the record — the email appears once on the timeline. Where it gets messy is ownership: the activity is attributed to whoever logged it, so shared prospecting threads can skew activity reporting. Teams that care about attribution usually assign a single owner per thread rather than relying on the integration to sort it out.