Skip to content

Commit bedd295

Browse files
authored
Update Segment method styling
1 parent e69c18f commit bedd295

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

src/engage/profiles/user-subscriptions/set-user-subscriptions.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -51,17 +51,17 @@ For example, a user might reach out to you after accidentally unsubscribing to y
5151

5252
With Segment's APIs, you can manage user subscriptions programmatically on a real-time basis. Use the APIs for ongoing subscription status updates, like when users subscribe to your marketing campaigns on a website form or modify their subscription from within a notification center.
5353

54-
### The `track` call compared to the Public API `identify` call
54+
### The Track call compared to the Public API Identify call
5555

56-
To update Engage user subscriptions with Segment's APIs, first choose between a [standard `track` call](/docs/connections/spec/track/), for non-critical subscription updates, or the [Public API `identify` call](https://api.segmentapis.com/docs/){:target="_blank"}, for critical updates that require immediate confirmation, like unsubscribes.
56+
To update Engage user subscriptions with Segment's APIs, first choose between a [standard Track call](/docs/connections/spec/track/), for non-critical subscription updates, or the [Public API Identify call](https://api.segmentapis.com/docs/){:target="_blank"}, for critical updates that require immediate confirmation, like unsubscribes.
5757

58-
When you use the `track` call, Segment replies with a standard HTTP `200 OK` status response code if it successfully received the request. Because the `track` call updates user traits asynchronously, though, the `200 OK` code indicates that Segment has received, but not yet processed, the request. As a result, use the `track` call for non-critical subscription updates, like form signups on your website or adding a subscription from within the user's notification center.
58+
When you use the Track call, Segment replies with a standard HTTP `200 OK` status response code if it successfully received the request. Because the Track call updates user traits asynchronously, though, the `200 OK` code indicates that Segment has received, but not yet processed, the request. As a result, use the Track call for non-critical subscription updates, like form signups on your website or adding a subscription from within the user's notification center.
5959

60-
When you make `identify` calls to Segment's Public API, however, you'll get an immediate response that confirms that Segment both received and processed the request. Use the Public API, then, for unsubscribes, so users immediately find out if their subscription updated.
60+
When you make Identify calls to Segment's Public API, however, you'll get an immediate response that confirms that Segment both received and processed the request. Use the Public API, then, for unsubscribes, so users immediately find out if their subscription updated.
6161

62-
### Format the `identify` call payload
62+
### Format the Identify call payload
6363

64-
For Segment to process the subscription status request, your `identify` call payload must include at least one object with a subscription contact vector, the subscription type, and the subscription status.
64+
For Segment to process the subscription status request, your Identify call payload must include at least one object with a subscription contact vector, the subscription type, and the subscription status.
6565

6666
The following array contains example objects that update both SMS and email subscription statuses:
6767

0 commit comments

Comments
 (0)