Skip to content

Commit 201e39a

Browse files
committed
docs: document Amplitude target users flow and sync cadences
1 parent a18c8ca commit 201e39a

2 files changed

Lines changed: 10 additions & 3 deletions

File tree

docs/docs/third-party-integrations/cohort-synchronisation/amplitude.md

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -43,10 +43,17 @@ application uses as the Flagsmith [identity](/flagsmith-concepts/identities) ide
4343

4444
## 3. Synchronise a cohort
4545

46-
1. In Amplitude, open the cohort you want to use and choose **Sync** (or **Export Cohort**).
46+
1. In Amplitude, open the cohort you want to target and click **Target users**.
4747
2. Select your Flagsmith destination.
48-
3. Choose the sync cadence. Scheduled and real-time syncs keep the Flagsmith segment up to date automatically; a
49-
one-time sync sends the current membership once.
48+
3. Choose the cadence, then click **Sync**:
49+
- **One-Time Sync** sends the cohort's current members once.
50+
- **Scheduled Sync** resends the membership every hour or every day.
51+
- **Real-Time Sync** resends the membership every minute.
52+
53+
Scheduled and real-time syncs keep the Flagsmith segment up to date on their own; with a one-time sync, later changes
54+
to the cohort do not reach Flagsmith until you sync it again.
55+
56+
![Amplitude Define Cadence dialog](/img/cohort-synchronisation/amplitude-define-cadence.png)
5057

5158
Shortly after the first sync, a segment named after your cohort appears on the **Segments** page of your project, ready
5259
to be used in [segment overrides](/third-party-integrations/cohort-synchronisation#using-a-synchronised-segment).
58.6 KB
Loading

0 commit comments

Comments
 (0)