Contributor I

Solved

"machine_open: true" Filtering

Forum|Forum|1 month ago
July 30, 2026
9 replies
325 views

This is not regarding Apple Privacy Opens.

I would like to be able to segment opens while filtering by machine_open: true to isolate all machine opens, not just MPP. This is not achievable through the segment builder. For the purposes of this engagement segment, relying solely on clicks would not suffice.

Will this ever be possible?

Best answer by ArpitBanjara

Yeah, the segment builder won't do it, which is annoying because the data is right there.

Klaviyo records it on every open, they just never added it to the properties you're allowed to filter on. Yes, Apple Privacy Open made that list, Machine Open didn't. No idea why, and I haven't seen anything from Klaviyo about changing it.

I am not sure if this will work but can you try this? - The Events API does return those properties, so you can you try to pull Opened Email events for your window, find who has zero opens where Machine Open is false, and write that back as a custom profile property you can segment on normally.

I hope this helps and let me know if this works.

I will also tag @GabbyEsposito @Temi O. from klaviyo support team. maybe they have more info on this?

Cheers

Arpit

ArpitBanjaraAnswer

Principal User II

Yeah, the segment builder won't do it, which is annoying because the data is right there.

Klaviyo records it on every open, they just never added it to the properties you're allowed to filter on. Yes, Apple Privacy Open made that list, Machine Open didn't. No idea why, and I haven't seen anything from Klaviyo about changing it.

I am not sure if this will work but can you try this? - The Events API does return those properties, so you can you try to pull Opened Email events for your window, find who has zero opens where Machine Open is false, and write that back as a custom profile property you can segment on normally.

I hope this helps and let me know if this works.

I will also tag @GabbyEsposito @Temi O. from klaviyo support team. maybe they have more info on this?

Cheers

Arpit

Arpit Banjara - Lead Email Marketing Specialist at Flowium

KeviSunshine

Expert Problem Solver III

I just ran into this use case too. Why does Klaviyo not expose the `machine_open` property within flows or segments? This seems like an oversight, particularly as “User has opened an email at least once since starting this flow” feels like one of the most basic engagement metrics to use within a flow.

I’m guessing the machine_open property is a bit unreliable and Klaviyo doesn’t want to get burned on that, but if you’re going to include it as a property metric, it should be filterable.

Posting here for some more visibility– any Klaviyo folks able to chime in on this?

JessFosnough

Expert Problem Solver IV

I’d like to see this functionality as well. Sadly, I’m guessing my engaged subscribers are not really as engaged as I think they are - but it’s hard for me to know for sure if I can’t filter out machine opens.

Jessica

GabbyEsposito

Community Manager

@KeviSunshine @ArpitBanjara @JessFosnough @thomas.delacruz hey everyone! I missed this before, but it’s on my radar now and I am looking into it and sharing this to see if i can get some answers.

Gabby

GabbyEsposito

Community Manager

Hi @KeviSunshine @ArpitBanjara @JessFosnough @thomas.delacruz – I wanted to follow up with a status update after looking into this internally.

The machine_open field is present in event data, but in Klaviyo it currently maps to the Apple Privacy Open signal rather than serving as a universal flag for all automated or proxy opens. That is why the Segment Builder uses Apple Privacy Open, and why there is not currently a separate condition for non-Apple activity such as Google or security-provider proxies.

This request is known internally and has been captured as product feedback, but it is still in triage. There is no committed timeline or active release I can share at this point. For now, Apple Privacy Open = false is the supported way to reduce MPP-related noise, while clicks and other engagement signals remain the closest workaround for broader engagement qualification.

I agree this does not fully solve the use case, and I will keep this thread updated as I learn more.

Gabby

KeviSunshine

Expert Problem Solver III

Hi Gabby,

I’m a little confused–is the `machine_open` property logically equivalent to the “Apple Privacy Open”, meaning there is no non-Apple `machine_open` logic within Klaviyo? (Klaviyo only detects Apple-based machine opens.)

Or is it that “Apple Privacy Open” is essentially just the label for the underlying machine_open property, meaning there is non-Apple `machine_open` logic, it’s just poorly named “Apple Privacy Open”?

Thank you!

Kevin.

GabbyEsposito

Community Manager

@KeviSunshine

Thanks for surfacing the older thread, @JessFosnough ! I can see why this is confusing because the guidance there says that all Apple Privacy Opens are machine opens, but not all machine opens are Apple Privacy Opens. That’s different from the more recent internal explanation I found, or maybe that was my misinterpretation… clearly this is confusing!

Bringing this up to have someone who knows more confirm.

I do know for sure that the broader request to make machine-open data filterable is still in product-feedback triage, and there is no committed timeline to share yet.

Gabby

Sign up

Use your Klaviyo credentials

Log in to the Community

Use your Klaviyo credentials