Skip to content

Commit bde5518

Browse files
authored
Segment's data flow to destination.
**Note:** Segment's data flow is primarily unidirectional, from Segment to integrated destinations. It does not inherently support a bidirectional flow where events, once delivered and processed by a destination, are sent back to Segment.
1 parent e382fa1 commit bde5518

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

src/connections/destinations/index.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -125,6 +125,8 @@ To add a Destination:
125125

126126
Segment increases deliverability to destinations in two ways: [retries](#retries) and [replays](/docs/guides/what-is-replay/). Retries happen automatically for all customers, while replays are available on request for [Business](https://segment.com/pricing/) customers.
127127

128+
**Note:** Segment's data flow is primarily unidirectional, from Segment to integrated destinations. It does not inherently support a bidirectional flow where events, once delivered and processed by a destination, are sent back to Segment.
129+
128130
### Retries
129131

130132
#### Retries in Segment's client libraries
@@ -176,4 +178,4 @@ You can see the current destination endpoint API success rates and final deliver
176178

177179
### IP Allowlist
178180

179-
{% include content/ip-allowlist.md %}
181+
{% include content/ip-allowlist.md %}

0 commit comments

Comments
 (0)