Is consent required for Benchmark Email on my website?

Yes. Benchmark Email scripts embed subscription forms and set cookies, requiring consent under the ePrivacy Directive. Collecting email addresses also requires a lawful basis under GDPR — typically explicit consent for marketing list building purposes.

What does Benchmark Email collect from website visitors?

Benchmark Email form scripts capture visitor email addresses and may set suppression or interaction cookies. Email tracking pixels embedded in outbound emails report open events, link clicks, and recipient IP addresses and device information back to the platform.

How does ConsentStack manage Benchmark Email consent?

ConsentStack classifies Benchmark Email as a marketing vendor. The form embed script is blocked until the visitor grants marketing consent. When consent is given, the script loads enabling subscription capture. Denial keeps the script blocked and no cookies are set.

What tracker domains does Benchmark Email use?

ConsentStack has catalogued tracker domains for Benchmark Email including benchmarkemail.com. These are the network destinations Benchmark Email's scripts contact, which a consent platform blocks until a visitor agrees.

Benchmark Email - Email Marketing Privacy Controls

Back to Vendor Library

Overview

Benchmark Email is a US-based email service provider that serves small and mid-sized businesses. When website operators embed Benchmark Email's subscription forms, the platform delivers embed scripts and form markup from Benchmark's servers. The platform's primary cross-site presence comes from subscription widgets embedded on third-party sites and tracking pixels inserted into outbound email campaigns.

What This Script Does

Benchmark Email's client-side presence takes two forms: form embed scripts and email tracking pixels.

Form embed scripts: JavaScript loaded from Benchmark Email's CDN renders subscription forms inline or as popups. These scripts capture visitor email addresses and optional profile fields, transmitting them directly to Benchmark's servers via form submission. Session cookies may be set to suppress repeat display of popup forms.

Email tracking pixels: One-pixel images embedded in outbound email newsletters report back to Benchmark's servers when recipients open a message. Each open event records the recipient's IP address, email client, and timestamp. Click tracking wraps links with redirect URLs routed through Benchmark's servers before resolving to the destination.

Data flows: Subscriber data collected via embedded forms (email address, name, any custom fields) is stored in Benchmark's platform. This data is used for list segmentation and campaign delivery. No third-party advertising profiles are built from this data.

Consent & Compliance

GDPR and ePrivacy Directive: Capturing an email address via a form requires a lawful basis — typically consent or legitimate interest depending on context. Embedding form scripts that set suppression cookies also triggers the ePrivacy cookie consent requirement. Email tracking pixels process recipient data (IP address, device info) without additional consent after the initial subscription, which requires careful privacy notice disclosure.

CCPA/CPRA: Subscriber data collected through embedded forms constitutes personal information under CCPA. Benchmark Email acts as a service provider processing data on behalf of the merchant; it does not sell subscriber lists. The embedded form itself collects personal data that must be disclosed in the site's privacy policy.

The consent category is marketing. The purpose of the embed is list growth and email marketing.

Should You Block This Without Consent?

Yes.

Benchmark Email embed scripts collect personal data (email addresses) and set display-suppression cookies before a visitor has agreed to marketing communications. The form itself should not render until the visitor has consented to marketing data collection. Blocking the script pre-consent prevents both cookie setting and unsolicited data capture.

Is Benchmark Email GDPR compliant?

Benchmark Email typically loads marketing trackers, which are not strictly necessary for your site to work. Under the GDPR and the ePrivacy Directive, non-essential cookies and trackers must stay blocked until a visitor gives clear opt-in consent. So Benchmark Email can be fully GDPR compliant, but only if your site holds its scripts until consent is granted and lets visitors decline just as easily. Compliance depends on how your site loads Benchmark Email, not on Benchmark Email itself.

Visit website