Skip to content

Commit 41f1dc4

Browse files
authored
Apply suggestions from code review
1 parent 04326c1 commit 41f1dc4

File tree

1 file changed

+3
-3
lines changed
  • src/connections/destinations/catalog/actions-amplitude

1 file changed

+3
-3
lines changed

src/connections/destinations/catalog/actions-amplitude/index.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -220,11 +220,11 @@ You configure the Amplitude (Actions) destination through Filters and Actions. C
220220
221221
### Set Once/Set Always fields
222222

223-
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).
223+
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"}.
224224

225-
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.
225+
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.
226226

227-
Conversely, to send top-level user properties, map only to the User Properties field and exclude mappings for Set Once and Set Always fields.
227+
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.
228228

229229
{% include components/actions-map-table.html name="amplitude" %}
230230

0 commit comments

Comments
 (0)