_hsenc
Email marketing · HubSpot · introduced ~2011
What is _hsenc?
What _hsenc and _hsmi do together
HubSpot tags every outbound link in a HubSpot-sent email with two parameters: _hsenc (the encoded engagement token — per-recipient, identity-bound on HubSpot's side) and _hsmi (the message ID — names which specific email send the link came from). Both feed HubSpot's contact-engagement scoring.
_hsenc joins a click back to your contact record in HubSpot's CRM. Forwarding it has the same blast radius as forwarding mkt_tok: another person's click gets attributed to you, and HubSpot picks up a join key tying that pageview back to your email address.
How LinkClean removes them
Both _hsenc and _hsmi ship default-on in LinkClean's email-marketing catalog.
Frequently asked
Is _hsenc the same as _hsmi?
No. _hsenc is per-recipient (identity-bound, like mc_eid); _hsmi is per-message (names which email send). Both ride along on HubSpot links.
Why is _hsenc on every HubSpot link?
HubSpot uses it to score contact engagement — which contacts opened, which clicked, which converted. _hsenc is the join key.
Is _hsenc personal data?
Yes. It identifies the specific HubSpot contact the email was sent to. Functionally identity-linked.
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.