Overview
Lemlist is a sales engagement platform focused on cold email outreach, multichannel sequences, and lead generation automation. It enables sales teams to send personalized email campaigns at scale while tracking engagement metrics like open rates, click-through rates, and reply rates. Its browser-side presence on third-party websites is primarily through tracking pixels and landing page instrumentation rather than traditional JavaScript tags.
What This Script Does
Lemlist's tracking footprint manifests in two primary ways: email tracking pixels and landing page scripts.
Email Tracking Pixels
Outbound emails sent through Lemlist contain a 1x1 transparent tracking pixel — a small image loaded from Lemlist's servers (typically t.lemlist.com or a custom tracking domain). When the recipient opens the email, the image request fires, recording:
- The time of the open event
- The recipient's IP address (used for approximate geolocation)
- The email client or browser user agent string
Links within Lemlist emails are wrapped through a redirect URL (l.lemlist.com or a custom domain) to track click events before forwarding the recipient to the intended destination.
Landing Page Scripts
When recipients click through to landing pages instrumented with Lemlist, the platform may set cookies to:
- Identify the visitor as a known email recipient using a unique identifier parameter in the URL
- Track page visit duration and scroll behavior on the landing page
- Record form submissions and conversion events tied to the outreach campaign
Cookies set on landing pages typically include a visitor identifier with a lifespan of 30 to 365 days, linking the web session back to the originating email campaign in Lemlist's reporting dashboard.
Consent & Compliance
Lemlist operates squarely in the marketing category. Under GDPR and ePrivacy, the tracking pixel in emails and cookies on landing pages constitute processing of personal data for direct marketing purposes. Email tracking pixels are particularly scrutinized under ePrivacy because they access the recipient's device (loading a remote image) without explicit consent.
For landing page cookies, prior consent is required before setting any non-essential cookies on European visitors' devices. The visitor identifier cookies serve marketing attribution purposes and do not qualify for the strictly necessary exemption.
Under CCPA/CPRA, the data collected through email pixels and landing page tracking constitutes personal information. If this data is shared with or accessible to third parties (including within Lemlist's platform for campaign analytics), it may qualify as "sharing" under CPRA, requiring an opt-out mechanism.
Should You Block This Without Consent?
Yes. Lemlist's tracking pixels and landing page cookies serve marketing and sales analytics purposes. They profile recipient behavior across email and web touchpoints for campaign optimization. Consent should be obtained before deploying landing page tracking scripts, and email tracking pixels should be disclosed in your privacy policy.
Consent Categories
Also Known As
Industries
Tracked Domains (1)
lemlist.comMarketingFrequently Asked Questions
Does Lemlist require cookie consent?
Yes. Lemlist sets landing page visitor identifier cookies lasting 30 to 365 days to attribute web sessions to outbound email campaigns. These marketing attribution cookies require prior consent under ePrivacy. Email tracking pixels sent in outbound emails also require disclosure in your privacy policy.
What does Lemlist track?
Lemlist embeds a 1x1 tracking pixel from t.lemlist.com in outbound emails to record open events and recipient IP addresses. Outbound links route through l.lemlist.com for click tracking. Landing page scripts set a persistent visitor identifier (30–365 days) linking web sessions to originating email campaigns.
How does ConsentStack manage Lemlist consent?
ConsentStack classifies Lemlist as marketing and blocks its landing page scripts until the visitor grants marketing consent. This prevents the persistent visitor identifier cookie from linking the web session to an outreach campaign before opt-in. Email pixel usage should be disclosed separately in your privacy policy.
Related Vendors
Manage consent for Lemlist
ConsentStack automatically detects and manages Lemlist trackers so your site stays compliant with global privacy regulations.