Skip to content

Commit fd7739b

Browse files
committed
edits
1 parent 8188078 commit fd7739b

File tree

1 file changed

+22
-26
lines changed

1 file changed

+22
-26
lines changed

src/connections/test-connections.md

Lines changed: 22 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -3,40 +3,36 @@ title: "Event Tester"
33
---
44

55

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:
77

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
1010

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.
1213
13-
There are two scenarios where you might want to use the Event Tester:
14+
## How it works
1415

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.
1718
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
1833

19-
## Ensuring an event is successfully making it to a specific destination
2034

21-
**1. Choose an event from the Source Debugger that you want to debug and select "Validate"**
2235

23-
Go to your Source Debugger, select an event and in the top right hand side of the debugger view, select "Validate".
24-
25-
![Screenshot of the Debugger tab, with a Checkout Started event selected and an error pointing to the Validate button.](images/event-tester_GgyOswJA.png)
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-
![A screenshot of the destination selection pop up modal](images/event-tester_2JfoKddf.png)
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-
![A screenshot of the Event Tester, with a track event selected](images/event-tester_J7TEDYvY.png)
38-
39-
**4. Ensure you're happy to send the test event to the destination**
4036

4137
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. 
4238

0 commit comments

Comments
 (0)