@@ -31,14 +31,15 @@ application uses as the Flagsmith [identity](/flagsmith-concepts/identities) ide
3131
3232## 2. Add Flagsmith as a destination in Amplitude
3333
34- 1 . In Amplitude, go to ** Data > Destinations** and find ** Flagsmith** in the cohort destinations catalogue.
35- 2 . Add the destination and paste your synchronisation key into the ** API Key** field.
36- 3 . Give the destination a recognisable name — including the Flagsmith environment name is a good idea, since the key
34+ 1 . In Amplitude, go to ** Data > Catalog > Destinations** and find ** Flagsmith** in the cohort destinations catalogue.
35+ 2 . Give the destination a recognisable name — including the Flagsmith environment name is a good idea, since the key
3736 determines which environment cohorts are synchronised into.
37+ 3 . Paste your synchronisation key into the ** Cohort sync api key** field.
38+ 4 . Check the ** Identifier Mapping** : Amplitude's ** User ID** must map to the Flagsmith ** Identifier** .
3839
3940![ Amplitude destination catalogue showing Flagsmith] ( /img/cohort-synchronisation/amplitude-destination-catalogue.png )
4041
41- <!-- Screenshot: Amplitude Flagsmith destination configuration with the API Key field -->
42+ ![ Amplitude Flagsmith destination configuration] ( /img/cohort-synchronisation/amplitude-destination-config.png )
4243
4344## 3. Synchronise a cohort
4445
@@ -47,8 +48,6 @@ application uses as the Flagsmith [identity](/flagsmith-concepts/identities) ide
47483 . Choose the sync cadence. Scheduled and real-time syncs keep the Flagsmith segment up to date automatically; a
4849 one-time sync sends the current membership once.
4950
50- <!-- Screenshot: Amplitude cohort sync dialog with the Flagsmith destination selected -->
51-
5251Shortly after the first sync, a segment named after your cohort appears on the ** Segments** page of your project, ready
5352to be used in [ segment overrides] ( /third-party-integrations/cohort-synchronisation#using-a-synchronised-segment ) .
5453
0 commit comments