You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/engage/journeys/send-data.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ Follow these steps to send a test event:
26
26
27
27
1. From the **Send to destinations** window, select **+ Add destination**.
28
28
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)).)
30
30
4. From the **Event Type** dropdown, select the event you want to test. Segment generates a test user ID.
31
31
5. Select **Send Event**, then view the test event results in the **Event lifecycle** section.
32
32
@@ -69,6 +69,6 @@ When the user enters the step:
69
69
70
70
### List destination
71
71
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.
73
73
74
74
For more information, see [Using Engage Data](/docs/engage/using-engage-data/).
0 commit comments