_hsmi
Email marketing · HubSpot · introduced ~2011
What is _hsmi?
Why _hsmi exists separately
HubSpot's tracking pipeline distinguishes “which campaign” (close to utm_campaign in risk profile) from “which contact” (per-person, identity-bound). _hsmi covers the campaign side; _hsenc covers the per-contact side. The two-token design mirrors Mailchimp's mc_cid / mc_eid split.
_hsmi alone tells HubSpot's analytics how a specific email send is performing. It rarely appears without _hsenc — but the two are conceptually distinct.
How LinkClean removes it
Default-on. Same path as _hsenc, mc_cid, mkt_tok.
Frequently asked
Is _hsmi sensitive on its own?
Less than _hsenc. _hsmi names the campaign-send (like utm_campaign); _hsenc names the recipient. Strip both.
Do all HubSpot emails have _hsmi?
Effectively yes — HubSpot's outbound-email tracking enables it by default for any tracked send.
Clean tracking on iPhone, in one tap.
LinkClean strips ~80 vendor-specific tracking parameters from any link, from any app's share sheet — and preserves functional ones like hl, t (YouTube timestamp), and q (search). No account, on-device.