Skip to content

Commit 4936249

Browse files
authored
Update send-data.md Updated page with List Destination info
1 parent 1687f2d commit 4936249

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/engage/journeys/send-data.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ Follow these steps to send a test event:
2626

2727
1. From the **Send to destinations** window, select **+ Add destination**.
2828
2. Choose the Destination that you want to connect.
29-
3. In the Destination pane, select **Event tester**.
29+
3. In the Destination pane, select **Event tester**. (This is only available for [Event Destinations]([url](https://segment.com/docs/engage/using-engage-data/#engage-destination-types-event-vs-list)).)
3030
4. From the **Event Type** dropdown, select the event you want to test. Segment generates a test user ID.
3131
5. Select **Send Event**, then view the test event results in the **Event lifecycle** section.
3232

@@ -69,6 +69,6 @@ When the user enters the step:
6969

7070
### List destination
7171

72-
The destination receives a list of users who qualify for the associated journey step. Unlike lists associated with Engage Audiences, users who are added to a journey list cannot be subsequently removed. See [best practices](/docs/engage/journeys/faq-best-practices#suppress-targeting-with-journey-lists) for techniques to suppress targeting with journey lists.
72+
The destination receives a list of users who qualify for the associated journey step. Unlike lists associated with Engage Audiences, users who are added to a journey list cannot be subsequently removed. See [best practices](/docs/engage/journeys/faq-best-practices#suppress-targeting-with-journey-lists) for techniques to suppress targeting with journey lists. List destinations do not have access to the Event Tester.
7373

7474
For more information, see [Using Engage Data](/docs/engage/using-engage-data/).

0 commit comments

Comments
 (0)