Dedicated-IP warm-up for a B2B events organiser
A newly provisioned dedicated IP could not take an events organiser's established campaign volume without risking sender reputation. HubSpot Marketing Hub was configured for dedicated-IP sending, with segmented CSV imports used to introduce the most-engaged contacts first. The ramp began with 1-2% of that audience and doubled weekly only after send approval, suppression, and segmentation checks.
Executive Summary
Context
A B2B events and exhibitions organiser was moving marketing activity to HubSpot while preparing a dedicated IP for high-volume campaign sends. The implementation paired DNS authentication with staged imports and weekly performance reviews before larger audience segments entered the send schedule.
What We Built
We configured HubSpot Marketing Hub for dedicated-IP sending and built a staged CSV-import process that introduced Customer, Nurture, and Prospect segments under send-approval and suppression controls.
Tech Stack
- HubSpot Marketing Hub
- dedicated IP
- DNS
- SPF
- DKIM
- DMARC
- CSV imports
Not a fit if your sending volume is low or irregular enough that a dedicated IP adds cost without benefit, or if your contact database has little engagement history to segment on. A staged ramp only pays off for senders with sustained, high-volume campaigns and a consistent send cadence, and it depends on identifying your most-engaged contacts to introduce first. With a largely cold list or no reliable engagement or lifecycle data, the early ramp steps cannot build the positive reputation the later volume increases rely on.
The Challenge
Event campaigns required large email sends, but a new dedicated IP had no sending history to establish its reputation with mailbox providers. Sending the established campaign volume immediately could damage deliverability, so the team needed a controlled route from an engaged audience to broader campaign segments.
The existing root-domain DMARC record added a separate constraint. Strict alignment would block delivery through HubSpot's sending architecture, which meant the sending subdomain required scoped SPF and DKIM records with relaxed DMARC alignment before warm-up could begin. Each increase also needed an operating control, because suppressed contacts or an unapproved segment could undermine the ramp before the next weekly review.
Our Approach
The team first validated the DNS conditions for HubSpot sending. Strict root-domain DMARC alignment would have prevented delivery, so SPF and DKIM were configured for a new sending subdomain and DMARC alignment was relaxed for that route.
Rather than introduce the full event audience at once, the build separated Customer, Nurture, and Prospect pools for manual CSV imports. The first sends used 1-2% of the most-engaged contacts, then the planned volume doubled weekly across the ramp window. Before each increase, a send-approval checklist checked segmentation and suppression guardrails. Weekly performance reviews determined whether the next planned increase could proceed, trading faster audience activation for a controlled reputation-building schedule.
Impact
A controlled path to larger campaign sends
The ramp started with the most-engaged 1-2% of contacts and doubled planned volume weekly, so the dedicated IP could build sending history before broader campaign segments were introduced. The schedule made gradual audience activation possible without treating the new IP as ready for established campaign volume on its first sends.
An authenticated route for HubSpot delivery
SPF and DKIM were scoped to the new sending subdomain, while relaxed DMARC alignment prevented the root-domain policy from blocking HubSpot delivery. That configuration made the dedicated-IP warm-up technically viable under the organisation's existing DNS policy.
Audience segments checked before each increase
Customer, Nurture, and Prospect pools entered HubSpot through staged CSV imports, with suppression and segmentation guardrails checked before each ramp step. Those controls made the send population reviewable before a larger volume reached the dedicated IP.
Weekly review points before volume doubled
A send-approval checklist and weekly performance review governed each planned increase. The operating model gave the marketing team a defined decision point before moving to the next volume band.
HubSpot Marketing Hub was configured to send through a dedicated IP rather than a shared sending route. The IP supported the staged warm-up schedule for event-campaign audiences.
A new sending subdomain received SPF and DKIM records for HubSpot delivery. The root-domain DMARC policy required relaxed alignment because strict adkim and aspf settings would have blocked those sends.
Manual CSV imports introduced Customer, Nurture, and Prospect contact pools in stages. The first import used 1-2% of the most-engaged contacts, and planned volume doubled weekly after that starting point.
A send-approval checklist checked suppression and segmentation guardrails before each volume increase. Weekly performance reviews provided the gate for the next scheduled ramp step.
FAQ
The warm-up began with 1-2% of the most-engaged contacts, introduced through staged CSV imports into HubSpot Marketing Hub. Planned volume doubled weekly, with send approval, segmentation, and suppression checks before each increase.
The existing root-domain DMARC record used strict alignment, which would have blocked delivery through HubSpot's sending architecture. SPF and DKIM were configured on a new sending subdomain, and relaxed DMARC alignment allowed the authenticated route to operate.
