I am using the query metric aggregates endpoint to pull unique metrics. I have experienced inflated open and received email rates compared to the clicked emails. I found out that this is due to Apple mail protection policy on the user devices.
Does Klaviyo API have a filter which I can use to separate out this audience? May be like apple_privacy_open = FALSE
I read an old article where there was a workaround to solve this by creating a segment and pulling that data but I wanted to know if this was updated in the newer version of the APIs
Create a segment of Apple Privacy Opens in Klaviyo:
Audience > Lists & Segments > Create new Segment:
What somebody has done > Opened Email > at least once overall time, where Apple Privacy Open = True
Although you can’t query metric aggregates by segment, you can by list. So then, you can convert the segment in a list:
Once it’s created, click on the new “Apple Privacy Opens” segment under Lists & Segments. Then, in the upper right-hand “Manage Segment” menu, click Convert to List.
Then make an API call and Query Metric Aggregates by the List that was converted in step B.
A more recent thread suggests that this is still something that the Klaviyo Product team is working on to add as a native feature:
Create a segment of Apple Privacy Opens in Klaviyo:
Audience > Lists & Segments > Create new Segment:
What somebody has done > Opened Email > at least once overall time, where Apple Privacy Open = True
Although you can’t query metric aggregates by segment, you can by list. So then, you can convert the segment in a list:
Once it’s created, click on the new “Apple Privacy Opens” segment under Lists & Segments. Then, in the upper right-hand “Manage Segment” menu, click Convert to List.
Then make an API call and Query Metric Aggregates by the List that was converted in step B.
A more recent thread suggests that this is still something that the Klaviyo Product team is working on to add as a native feature:
Thanks @Ashley I. I came across across those articles before posting this questions. But I just wanted to know if this had been updated in the new API version.
Looks like, I need to use the temporary workaround for now. Thanks!