Luma Email Tracking: What Event Hosts See and How to Block It

Someone invited you to a founder dinner or a meetup, and the invite came from Luma, the event platform at luma.com (formerly lu.ma). Luma email tracking is not hidden: Luma's help article on email delivery says "We track opens by inserting a small 1x1 image into the email." The host who sent the invite or the blast can then click your name and see whether you opened it. This guide sticks to Luma's documentation and our own DNS checks, flags the gaps, and shows how to block the tracking in Gmail.

Key Takeaways

• Luma's help center states that it tracks opens "by inserting a small 1x1 image into the email" and calls the method "not a foolproof system."
• Event hosts can click a guest's name under Manage Event, Guests to see every email sent to that guest, with delivery status and whether it was opened; a Clicked status shows a link was followed, but not which one.
• Luma newsletters report sent, opens, clicks and unsubscribes, and a View Stats button shows "detailed recipient-level information."
• Luma routes links in its messages through its own short link domain, luma.link (older emails use o.lu.ma), and its sending domains publish SPF records that authorize Amazon SES.
• Luma documents no setting for guests or hosts that turns open tracking off; guests can only unsubscribe or mute notifications, which stops the emails rather than the pixel.

Does Luma Track Whether You Open Its Emails?

Yes, for some of them, and Luma says so plainly. Its Email Delivery + Open Troubleshooting article opens the topic with "For certain emails, we will show you if a guest opens the email." It goes on: "When the user opens the email, the image is loaded and we mark the email as opened in Luma."

Luma does not say which emails count as "certain," though it notes "We send millions of emails a month." A guest can receive four kinds:

• Invites. Luma's invite guide says "When you send an invite, guests receive an email," plus SMS, WhatsApp or push if you have linked a phone or installed the app.
• Blasts. Host messages about an event. The blasts guide says blasts go to every guest with Going status by default, and its advanced editor allows images and buttons.
• Reminders. Luma's reminder update, first posted September 17, 2024, says automated reminders "go out 1 day and 1 hour before the event."
• Newsletters. Calendar owners can mail their followers.

Luma is honest about the limits: "some email clients will refuse to load images and not mark emails as opened while other email clients will load images before the email is opened." That second case is image prefetching, which logs opens nobody performed. Our piece on Apple Mail fake opens explains why that makes opens a noisy signal.

What Can an Event Host See About Each Guest?

A host sees your email status message by message, alongside your registration data. The same troubleshooting article explains that a host can go to "Manage Event > Guests tab and clicking on the guest's name," which "opens a detailed view showing all emails sent to that guest with their delivery status and whether they opened them." Luma lists six statuses: Sent, Delivered, Opened, Clicked, Bounced and Marked Spam. Clicked is described as "indicating the highest level of engagement," and Luma adds: "We don't show which specific link they clicked, only that they clicked one."

Newsletters go further. Luma's newsletter guide lists Sent, Opens, Clicks and Unsubscribes, then says "Click View Stats on any sent newsletter to see detailed recipient-level information."

Email status is only one layer. Luma's privacy policy says "when you register for an event, we will share your personal data with the event host." According to the guest CSV guide, a host's export includes:

• Your name, email address and phone number, if provided.
• "Responses to custom registration questions," one column per question.
• "UTM parameters and ad click IDs from the link the guest registered through."
• Check in status for in person events, or join status for online ones.

Luma's event insights page adds referral tracking ("who invited who"), and, for online events with Zoom connected, "we track when people join and leave the Zoom." The referrals guide confirms that the ad click IDs saved with each registration include gclid and fbclid.

Where Do Links in Luma Emails Go?

They go through Luma first. The troubleshooting FAQ says "We route links in the messages we send — like event emails and texts — through our own short-link domain, luma.link (you may also see the older o.lu.ma)." A link to an event shows up "as something like luma.link/abc123 and redirects to the real destination when opened."

Luma presents this as a safety note about a first party domain and does not say whether luma.link records the Clicked status. A redirect between you and the destination is, however, the standard way a sender learns about a click, which our explainer on open tracking versus click tracking walks through. Treat that link as our inference, not Luma's statement.

When we queried both hosts on November 2, 2026, each answered through Cloudflare with no Amazon SES headers, so the redirect is Luma's own, not an email provider's click tracker.

Which Servers Send Luma Email?

Public DNS points to Amazon SES. Luma says "we send from our own luma.com and luma-mail.com domains," with team calendars mailing from {calendar-slug}@calendar.luma-mail.com and personal calendars from {username}@user.luma-mail.com. We looked up those domains on November 2, 2026:

• luma.com publishes the SPF record "v=spf1 include:_spf.google.com include:amazonses.com -all" and a DMARC policy of p=reject.
• luma-mail.com authorizes Google and amazonses.com in SPF and also sets DMARC to p=reject.
• luma-mail.com, calendar.luma-mail.com and user.luma-mail.com all list inbound-smtp.us-west-2.amazonaws.com as their mail server, which is Amazon SES's receiving endpoint in the US West (Oregon) region.

Those records authorize SES; they do not prove every message leaves through it, and we did not inspect the headers of a live Luma email. Amazon's SES documentation describes the include:amazonses.com mechanism. Luma does not publish the hostname that serves its open pixel, and we will not guess one.

Can Guests Opt Out of Luma Email Tracking?

Not as such. Luma offers ways to stop emails, not ways to stop the pixel. The troubleshooting article lists three: guests "can turn off email notifications in their account settings," they "can unsubscribe from your calendar," and "All Luma emails include unsubscribe options in the footer." None of them is described as disabling open tracking on the emails you still receive.

Hosts get no documented switch either: no help article describes sending an event email without the pixel, so it is effectively on by default. Luma's privacy policy covers Log Data, Google Analytics and cookies, but it never mentions email opens, pixels or link redirects.

What Does EU Guidance Say About Pixels in Event Emails?

European regulators treat an email open pixel as access to your device, which normally requires consent. The EDPB's Guidelines 2/2023, adopted on 7 October 2024, state that "In the case of an email, the sender may include a tracking pixel to detect when the receiver reads the email," and that Article 5(3) of the ePrivacy Directive "is applicable, even if this storage is not permanent."

France's CNIL went further in its recommendation on tracking pixels in emails, which followed a public consultation from 12 June to 24 July 2025. For compliance teams running events on Luma, three points stand out:

• The sender is the controller. The CNIL says the email sender "must therefore be regarded as controller, including when it outsources to third parties." For a Luma event, that points at the host or company running the calendar.
• Open rate analysis needs consent. Measuring opens "to measure and optimise the performance of campaigns" is listed among purposes that require the recipient's consent.
• Reminders are only partly exempt. The CNIL counts "reminders of appointments or reservations" as transactional, but the exemption covers deliverability, and it suggests keeping only "the date (at the day and without recording the time) of the last known opening."

Under the CNIL's reading, a per guest Opened badge on a promotional blast or newsletter is individual open measurement, and the consent question lands on the host, not Luma. Luma's own email consent policy covers consent to receive email ("We do not allow emailing people without their consent"), which is a different thing from consent to be tracked.

What This Means for Your Inbox

Event email reveals more than a newsletter open because it sits next to a social decision. Luma's guest list holds an Invited status for people who have not answered yet. Combine that with an Opened status on the invite and a host can, in principle, tell "opened and ignored" apart from "never saw it." That is our inference from two documented features, not a report Luma advertises.

Gmail blunts part of this. Google's image help page says "Senders can’t use image loading to get information about your computer or location," because Google fetches images through its own servers. The open itself, and roughly when it happened, still reaches Luma. Luma is not unusual here. Event creators on Eventbrite get Opened and Clicked reports on their invitations too, while Calendly puts its tracking on the booking page instead of in an email open rate.

How Do You Block Luma Email Tracking in Gmail?

Stop remote images from loading automatically, then be deliberate about links. Our full guide on how to block email tracking in Gmail compares every option; for Luma specifically:

1. Turn off automatic images. In Gmail on a computer, click Settings, then "See all settings," find the "Images" section, choose "Ask before displaying external images," and click "Save Changes." The 1x1 pixel stays dark until you allow images.
2. RSVP on the event page. If you already know the event address, typing it into your browser skips the luma.link redirect in the email. Luma still knows who you are once you sign in and register, so this only keeps the click on the email out of the picture, at best.
3. Strip the tracking from your registration link. Before registering, delete any utm_ or fbclid parameters from the address bar, since Luma saves them on your registration and hosts see them in the CSV.
4. Check the raw message. Open the three dot menu, choose "Show original," and search for img tags with long unique strings to find the pixel's host yourself. Our guide to detecting tracking pixels in Gmail shows how.
5. Add a custom rule. Once you have found that host, Gblock's custom filters can block it in every future email.
6. Mute what you do not need. Turn off notification channels in your Luma settings and unsubscribe from calendars you no longer follow.

How Does Gblock Compare to Ugly Email and PixelBlock?

No common Gmail blocker documents Luma coverage by name, Gblock included. We checked Gblock's extension source on November 2, 2026, and its built in blocklist has no Luma entry. Our roundup of email tracker Chrome extensions covers the senders' side.

Gblock works inside Gmail and its blocklist updates on its own, which helps against a sender whose pixel host is undocumented. Still, the Gmail image setting is the one option certain to stop a Luma open pixel today, because it stops every image.

What We Could Not Verify

We did not receive a live Luma email for this piece, so we have not seen the pixel's hostname or confirmed which of invites, blasts, reminders and newsletters carry it. Luma's docs do not say whether hosts see open timestamps or whether luma.link records the Clicked status. Everything above rests on Luma's help center and privacy policy as read on November 2, 2026, DNS lookups made the same day, and Gblock's own source code.