Skip to content

Commit 3f20204

Browse files
committed
date updates
1 parent b0ac809 commit 3f20204

File tree

1 file changed

+2
-2
lines changed
  • src/connections/destinations/catalog/klaviyo

1 file changed

+2
-2
lines changed

src/connections/destinations/catalog/klaviyo/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ To configure Klaviyo as an Event Source to get data into your warehouse or other
2626
2727
## Migrate to the Klaviyo (Actions) destination
2828

29-
Starting on June 7th, 2024, Segment will automatically migrate all classic Klaviyo destinations to the new Klaviyo (Actions) destination. Migrated Klaviyo (Actions) destinations will have the same name as your classic destination, with "Migrated" appended.
29+
Starting on June 20th, 2024, Segment will automatically migrate all classic Klaviyo destinations to the new Klaviyo (Actions) destination. Migrated Klaviyo (Actions) destinations will have the same name as your classic destination, with "Migrated" appended.
3030

3131
For example, if you named your classic destination "Email Marketing Campaigns", Segment would name your migrated destination "Email Marketing Campaigns Migrated".
3232

@@ -48,7 +48,7 @@ To enable your new Klaviyo (Actions) destination:
4848

4949
**If your destination is connected to a Journey**, Segment will create your migrated Klaviyo (Actions) destination, but will not enable it for you. All existing Journeys will remain connected to the classic Klaviyo destination. You must [build new Journeys](/docs/engage/journeys/build-journey/) that reference the new, migrated Klaviyo destination.
5050

51-
Segment will disable all instances of the classic Klaviyo destination after June 30th, 2024.
51+
Segment will disable all instances of the classic Klaviyo destination in July 2024.
5252

5353
## Getting started
5454
1. From the Segment web app, click **Catalog**.

0 commit comments

Comments
 (0)