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/connections/test-connections.md
+22-26Lines changed: 22 additions & 26 deletions
Original file line number
Diff line number
Diff line change
@@ -3,40 +3,36 @@ title: "Event Tester"
3
3
---
4
4
5
5
6
-
Segment has an Event Tester that enables you to test your connections between Segment and your destination. You can access the Event Tester from your Source Debugger, or from your destination settings.
6
+
Segment's Event Tester enables you to test your connections between Segment and your destination. You can inspect both the request sent from Segment and the response you receive back from the destination. You can use the Event Tester to:
7
7
8
-
> info "Available for server-side event streaming destinations only"
9
-
> This feature is only available for server-side integrations (also known as cloud-mode destinations). You can't use this for client-side integrations (also known as device-mode destinations).
8
+
* ensure an event successfully arrives to a specific destination
9
+
* ensure your new destination is configured correctly
10
10
11
-
## Use Cases
11
+
> info ""
12
+
> This feature is only available for server-side, [cloud-mode](/docs/connections/destinations/#connection-modes) integrations. You can't use this for client-side, [device-mode](/docs/connections/destinations/#connection-modes) integrations.
12
13
13
-
There are two scenarios where you might want to use the Event Tester:
14
+
## How it works
14
15
15
-
* ensuring an event is successfully making it to a specific destination
16
-
* ensuring your new destination is configured correctly
16
+
> warning ""
17
+
> Make sure you have mappings enabled for your destination. The event tester only tests the enabled mappings for the destination.
17
18
19
+
To use the Event Tester:
20
+
1. Navigate to **Connections > Destinations** and select your destination.
21
+
2. Click the **Event Tester** tab.
22
+
3. Select the type of test event. You can choose from: Track, Identify, Page, Screen, Group.
23
+
4. Enter your test event payload. You can type in your own event or choose from **Load event from source** or **Generate sample event**.
24
+
***Load event from source**: Segment loads an event based on your source.
25
+
***Generate sample event**: Segment generates a sample event for you.
26
+
5. Click **Send test event to destination**.
27
+
28
+
If your test event successfully sends to the destination, you can see in the **View test outcome section:
29
+
* The request and the response
30
+
* How many of your mappings matched
31
+
* The total number of API calls that were made
32
+
* Which mappings were successful and which ones failed
18
33
19
-
## Ensuring an event is successfully making it to a specific destination
20
34
21
-
**1. Choose an event from the Source Debugger that you want to debug and select "Validate"**
22
35
23
-
Go to your Source Debugger, select an event and in the top right hand side of the debugger view, select "Validate".
24
-
25
-

26
-
27
-
**2. Choose the destination you want to test with**
28
-
29
-
Select the destination that you want to test this event with. At this time, you can only use the Event Tester for cloud-mode (server side) destinations.
30
-
31
-

32
-
33
-
**3. Send event to destination**
34
-
35
-
The event payload from your debugger that you just selected will automatically load in the JSON view. You have the option to edit the payload if you want. Assuming it looks good, select "Send Event" at the bottom right of the screen.
36
-
37
-

38
-
39
-
**4. Ensure you're happy to send the test event to the destination**
40
36
41
37
This is a real event that will appear in your end tool alongside your existing data. If you're not comfortable with this, then select "Cancel" and do not send the event.
0 commit comments