How to Log Emails in HubSpot CRM: BCC, Forwarding and Server-Side Auto-Logging

If your CRM only holds half the emails your team sends and receives, the contact timeline lies. Reps re-introduce themselves to people colleagues spoke to last week, reporting undercounts real activity, and handovers leave the next person guessing. Logging emails in HubSpot is not housekeeping. It is how you keep the system of record accurate enough to trust.

There are three reliable ways to get email activity into HubSpot: log individual messages with the BCC address, capture inbound mail with the forwarding address, and remove the manual step entirely with server-side auto-logging. This guide covers all three, the distinction that trips most teams up, and how to make logging consistent across a whole organisation rather than one diligent rep.

Find your BCC and forwarding addresses first

Every HubSpot account has two unique, portal-specific email addresses for capturing mail. You will need both.

In HubSpot, go to Settings, then Integrations, then Email Integrations, and open the Log and Track tab. You will see:

• A BCC address in the format yourportalid@bcc.hubspot.com, used to log emails you send.
• A forwarding address in the format yourportalid@forward.hubspot.com, used to log emails you have received.

These addresses are specific to your portal, so copy them rather than relying on a generic example. If you want logged emails to associate with the right contacts and create activity on the timeline, this is where everything starts.

Method 1: Log emails you send with the BCC address

When you compose an email from your own client, whether Gmail, Outlook, or anything else, add the HubSpot BCC address to the BCC field before you send. HubSpot receives a copy, matches the recipient to an existing contact by email address, and logs the message on that contact's timeline.

A few things to know:

• If the recipient does not already exist as a contact, HubSpot can create one, depending on your settings. That is useful for capture, but it is also how duplicate and low-quality records creep in, so decide deliberately whether you want that behaviour switched on.
• BCC only logs that single outgoing message. The reply that comes back is not captured unless the other party is also BCC'd, which in practice they will not be.
• Logging by hand on every send is fine for a handful of important emails. As a standing process for a busy team, it fails quietly the moment someone is rushed.

Method 2: Log emails you receive with the forwarding address

To capture an inbound email, forward it to your HubSpot forwarding address. HubSpot reads the original sender, matches them to a contact, and logs the message.

This is where the single most common mistake happens, and it is worth stating plainly.

Forwarding is not the same as redirecting

HubSpot needs to see the original sender's address in the message in order to associate it with the correct contact. A standard forward preserves those original headers, so logging works. A redirect rewrites the message so it appears to come from you, which strips the original sender and breaks the match. If forwarded emails are landing against the wrong contact, or not logging at all, a redirect rule is almost always the cause.

Method 3: Auto-log at the server level (the scalable option)

Manual BCC and forwarding work, but they depend on people remembering. The version that survives contact with a real sales or service team is server-side logging, where the mail server itself adds the BCC and forwards inbound mail automatically.

If you run Google Workspace, Microsoft 365, Exchange, or another managed mail environment, an administrator can configure routing rules so that:

• Outbound mail from chosen users or aliases is automatically BCC'd to the HubSpot logging address.
• Inbound mail is automatically forwarded, not redirected, so it logs against the right contact.

Two practical notes. First, HubSpot only logs mail for addresses it recognises, so any send-from aliases your team uses need to be registered in HubSpot to be eligible. Second, server-side rules apply to everyone in scope by default, which is powerful but also a fast way to flood the CRM with internal or irrelevant mail if the rules are too broad. Set them with intent.

Logging emails is a data-architecture decision, not a settings toggle

Choosing where the BCC sits is the easy part. The hard part, and the reason email logging quietly degrades in most mid-market CRMs, is everything around it:

• Matching and deduplication. Logged emails are only useful if they land on the correct, single contact record. Weak matching rules and uncontrolled auto-creation produce duplicates that fragment the timeline.
• Scope and noise. Logging absolutely everything buries the signal. Internal threads, automated notifications, and personal mail rarely belong in the CRM.
• Privacy and consent. Auto-logging inbound mail means personal data lands in HubSpot. Under UK GDPR you need to be deliberate about what you capture, retain, and expose to whom.
• Consistency. A process that relies on individuals BCC'ing by hand will never be complete. Server-side rules make logging a property of the system, not the person.

Get these right and your HubSpot CRM implementation produces activity data you can actually report on and automate against. Get them wrong and you build dashboards on a timeline full of gaps and duplicates.

Where email logging fits in a clean CRM

Email is one data stream among several. The same discipline applies to calls, meetings, form submissions, and data flowing in from the rest of your stack. If the picture of a customer is spread across tools, connecting those systems so activity lands in one place is the job, which is what our HubSpot integrations work is built around. For the full picture of what can be connected and how, the guide to connecting anything with HubSpot integrations is the place to start. And if your records are already messy before logging is even switched on, that is usually a data migration and cleanup problem to solve first.

Make HubSpot a system of record you can trust

BCC for one-off sends, forwarding for inbound, and server-side rules when you need email capture to be complete and consistent across the team. The mechanics take minutes. Designing the matching, scope, and governance so the logged data stays clean is the part worth doing properly.

If you want email activity, and the rest of your CRM data, set up so it is accurate enough to run the business on, that is the work we do.

Talk to us about CRM implementation