Skip to content

Commit 6490e32

Browse files
committed
[netlify-build]
1 parent 737a0c1 commit 6490e32

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/connections/reverse-etl/setup.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ Once you’ve added a model, you need to add a destination. In Reverse ETL, dest
6969

7070
Reverse ETL supports 30+ destinations: see all destinations listed in the [Reverse ETL catalog](/docs/connections/reverse-etl/reverse-etl-catalog/). If the destination you want to send data to is not listed in the Reverse ETL catalog, use the [Segment Connections Destination](/docs/connections/reverse-etl/reverse-etl-catalog/#segment-connections-destination) to send data from your Reverse ETL warehouse to your destination.
7171

72-
Engage users can use the [Segment Profiles Destination](/docs/connections/destinations/catalog/actions-segment-profiles/) to send data from their warehouse to their Reverse ETL destinations.
72+
Engage users can use the [Segment Profiles Destination](/docs/connections/destinations/catalog/actions-segment-profiles/) to create and update [Profiles](/docs/unify/) that can then be accessed through [Profile API](/docs/unify/profile-api/) and activated within [Twilio Engage](/docs/engage).
7373

7474
> info "Separate endpoints and credentials required to set up third party destinations"
7575
> Before you begin setting up your destinations, note that each destination has different authentication requirements. See the documentation for your intended destination for more details.

0 commit comments

Comments
 (0)