Skip to content

Release 24.23.1 #6653

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 60 commits into from
Jun 4, 2024
Merged

Release 24.23.1 #6653

merged 60 commits into from
Jun 4, 2024

Conversation

cmastr
Copy link
Contributor

@cmastr cmastr commented Jun 4, 2024

No description provided.

MStephen024 and others added 30 commits September 30, 2023 16:37
Added the "Why can't I connect the audience/computed trait to an existing destination in my workspace?" section to the Engage FAQ doc.
Updated the FAQs with info on connecting Engage tool to an existing destination. Also fixed a typo.
Added the following info in Time Comparison section: 
----------------------------------------------------- 
While in the audience builder, the time you see on the UI will be based on your local timezone but it is converted to UTC on the backend. Please take note of this while you are setting time on the audience builder UI.
### Why am I receiving the error "The audience would create a cycle by referencing another audience"?

This error occurs when creating audiences that reference each other, meaning audience X refers to audience Y in its trigger condition, and later you attempt to modify audience Y's trigger condition to refer back to audience X. To avoid this error, ensure that the audiences do not reference each other in their conditions.
Correct folder name to match slug
Update index.md Unify Identity Resolution link broken
Add section on native Amplitude events
Update mobile spec to reflect new libraries
Provide information on sending email data to Iterable destination
Update facebook-app-events-swift.md
cmastr and others added 25 commits June 3, 2024 09:52
Update set-user-subscriptions.md - update to include RETL option
…-permissions-should-the-private-api-key-have

Add more granual permissions information to Klaviyo (Actions) destination
Master to develop after one-off
Fix typo for Arrays
@cmastr cmastr added the release For Release PRs label Jun 4, 2024
@cmastr cmastr requested review from pwseg and a team as code owners June 4, 2024 18:30
@cmastr cmastr merged commit 3139656 into master Jun 4, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release For Release PRs
Projects
None yet
Development

Successfully merging this pull request may close these issues.