Skip to content

Commit 93fe8a0

Browse files
author
klaviyo-sdk
committed
version 6.0.0
1 parent f401922 commit 93fe8a0

File tree

1,352 files changed

+56248
-424469
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

1,352 files changed

+56248
-424469
lines changed

CHANGELOG.md

+51
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,57 @@ NOTE: For more granular API-specific changes, please see our [API Changelog](htt
99

1010

1111

12+
## [6.0.0] - revision 2023-10-15
13+
14+
### Added
15+
16+
#### Support for returning list suppressions via the [/profiles endpoint](https://developers.klaviyo.com/en/reference/get_profiles)
17+
18+
We now support filtering on list suppression with the get profiles endpoint, which brings us to parity with v2 list suppression endpoint that was the previously recommended solution.
19+
20+
Rules for suppression [filtering](https://developers.klaviyo.com/en/docs/filtering_):
21+
22+
- You may not mix-and-match list and global filters
23+
- You may only specify a single date filter
24+
- You may or may not specify a reason
25+
- You must specify a list_id to filter on any list suppression properties
26+
27+
Examples:
28+
29+
- To return profiles who were suppressed after a certain date:
30+
`filter="greater-than(subscriptions.email.marketing.suppression.timestamp,2023-03-01T01:00:00Z)"`
31+
- To return profiles who were suppressed from a specific list after a certain date:
32+
`filter="greater-than(subscriptions.email.marketing.list_suppressions.timestamp,2023-03-01T01:00:00Z),equals(subscriptions.email.marketing.list_suppressions.list_id,\"LIST_ID\")"`
33+
- To return all profiles who were suppressed for a specific reason after a certain date:
34+
`filter="greater-than(subscriptions.email.marketing.suppression.timestamp,2023-03-01T01:00:00Z),equals(subscriptions.email.marketing.suppression.reason,\"user_suppressed\")"`
35+
36+
#### Optionally retrieve subscription status on Get List Profiles, Get Segment Profiles, Get Event Profile
37+
38+
Now you can retrieve subscription status on any endpoint that returns profiles, including Get List Profiles, Get Segment Profiles and Get Event Profile. Use `additional_fields_profile="subscriptions"` on these endpoints to include subscription information.
39+
40+
### Changed
41+
42+
#### Subscription object not returned by default on Get Profile / Get Profiles
43+
44+
The subscription object is no longer returned by default with get profile(s) requests. However, it can be included by adding the `additional_fields_profile="subscriptions"` to the request. This change will allow us to provide a more performant experience when making requests to Get Profiles without including the subscriptions object.
45+
46+
#### Profile Subscription Fields Renamed
47+
48+
In the interest of providing more clarity and information on the subscription object, we have renamed several fields, and added several as well. This will provide more context on a contact's subscriptions and consent, as well as boolean fields to see who you can or cannot message.
49+
50+
For SMSMarketing:
51+
52+
- `timestamp` is now `consent_timestamp`
53+
- `last_updated` is a new field that mirrors `consent_timestamp`
54+
- `can_receive_sms_marketing` is a new field which is `True` if the profile is consented for SMS
55+
56+
For EmailMarketing:
57+
58+
- `timestamp` is now `consent_timestamp`
59+
- `can_receive_email_marketing` is True if the profile does not have a global suppression
60+
- `suppressions` is now `suppression`
61+
- `last_updated` is a new field that is the most recent of all the dates on the object
62+
1263
## [5.2.0] - revision 2023-09-15
1364

1465
### Added

0 commit comments

Comments
 (0)