From 04326c1ced475afc7243fad1ea6171fd243e7a10 Mon Sep 17 00:00:00 2001 From: bobbyatsegment <93934274+bobbyatsegment@users.noreply.github.com> Date: Tue, 26 Sep 2023 13:59:27 -0400 Subject: [PATCH 1/2] Add section on Set Once/Set Always fields --- .../destinations/catalog/actions-amplitude/index.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/actions-amplitude/index.md b/src/connections/destinations/catalog/actions-amplitude/index.md index 04a648e268..9a3b55797a 100644 --- a/src/connections/destinations/catalog/actions-amplitude/index.md +++ b/src/connections/destinations/catalog/actions-amplitude/index.md @@ -216,7 +216,15 @@ Keep the following in mind if you plan to move to Amplitude (Actions) from a cla You configure the Amplitude (Actions) destination through Filters and Actions. Consult the table below for information about configuring your Amplitude (Actions) destination similarly to your classic Amplitude destination. > info "" -> Contact Segment support if you find features missing from the Amplitude (Actions) destination that were available in the classic Amplitude destination. +> Contact Segment support if you find features missing from the Amplitude (Actions) destination that were available in the classic Amplitude destination. + +### Set Once/Set Always fields + +Amplitude restricts the mixing of top-level user properties with $set, $setOnce, or $setAlways operations in a single request, [as outlined in Amplitude’s documentation](https://www.docs.developers.amplitude.com/analytics/apis/identify-api/#user_properties-supported-operations). + +To circumvent this within Segment, users can opt to exclusively map event parameters to either the User Properties field or to one of the user property operations (Set Once and/or Set Always) available in mappings, avoiding mixing them in the same request. Specifically, if you are utilizing Set Once and/or Set Always fields, include all relevant fields in their respective mappings and do not configure mappings for User Properties in the same request. + +Conversely, to send top-level user properties, map only to the User Properties field and exclude mappings for Set Once and Set Always fields. {% include components/actions-map-table.html name="amplitude" %} From 41f1dc4d63441d37d27bb89ccae92a3d93057de1 Mon Sep 17 00:00:00 2001 From: rchinn-segment <93161299+rchinn-segment@users.noreply.github.com> Date: Thu, 7 Dec 2023 10:24:53 -0800 Subject: [PATCH 2/2] Apply suggestions from code review --- .../destinations/catalog/actions-amplitude/index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/connections/destinations/catalog/actions-amplitude/index.md b/src/connections/destinations/catalog/actions-amplitude/index.md index 9a3b55797a..b7b005f519 100644 --- a/src/connections/destinations/catalog/actions-amplitude/index.md +++ b/src/connections/destinations/catalog/actions-amplitude/index.md @@ -220,11 +220,11 @@ You configure the Amplitude (Actions) destination through Filters and Actions. C ### Set Once/Set Always fields -Amplitude restricts the mixing of top-level user properties with $set, $setOnce, or $setAlways operations in a single request, [as outlined in Amplitude’s documentation](https://www.docs.developers.amplitude.com/analytics/apis/identify-api/#user_properties-supported-operations). +Amplitude restricts the mixing of top-level user properties with `$set`, `$setOnce`, or `$setAlways` operations in a single request, [as outlined in Amplitude’s documentation](https://www.docs.developers.amplitude.com/analytics/apis/identify-api/#user_properties-supported-operations){:target="_blank"}. -To circumvent this within Segment, users can opt to exclusively map event parameters to either the User Properties field or to one of the user property operations (Set Once and/or Set Always) available in mappings, avoiding mixing them in the same request. Specifically, if you are utilizing Set Once and/or Set Always fields, include all relevant fields in their respective mappings and do not configure mappings for User Properties in the same request. +To circumvent this within Segment, users can opt to exclusively map event parameters to either the **User Properties** field or to one of the user property operations (Set Once and/or Set Always) available in mappings. If you use the **Set Once** and/or **Set Always** fields, include all relevant fields in their respective mappings and do not configure mappings for **User Properties** in the same request. -Conversely, to send top-level user properties, map only to the User Properties field and exclude mappings for Set Once and Set Always fields. +Conversely, to send top-level user properties, map only to the **User Properties** field and exclude mappings for the **Set Once** and **Set Always** fields. {% include components/actions-map-table.html name="amplitude" %}