Skip to content

Commit 0fc10b8

Browse files
committed
[netlify-build]
1 parent 31ebae3 commit 0fc10b8

File tree

4 files changed

+20
-13
lines changed

4 files changed

+20
-13
lines changed
347 KB
Loading
Loading
-297 KB
Binary file not shown.

src/connections/test-connections.md

+20-13
Original file line numberDiff line numberDiff line change
@@ -2,25 +2,25 @@
22
title: "Event Tester"
33
---
44

5+
> info ""
6+
> This feature is only available for server-side, [cloud-mode](/docs/connections/destinations/#connection-modes) integrations. It doesn't work for client-side, [device-mode](/docs/connections/destinations/#connection-modes) integrations.
7+
><br><br>You must have write access in your Segment workspace to use the Event Tester.
58
69
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 ensure:
710

811
* An event successfully arrives to a specific destination
912
* Your new destination is configured correctly
1013

11-
The Event Tester sends a real event that appears in your end tool alongside your existing data.
12-
13-
14-
> info ""
15-
> This feature is only available for server-side, [cloud-mode](/docs/connections/destinations/#connection-modes) integrations. It doesn't work for client-side, [device-mode](/docs/connections/destinations/#connection-modes) integrations.
14+
The Event Tester sends a real event that appears in your end tool alongside your existing data. You can use the Event Tester for these products:
15+
* Connections
16+
* Linked Audiences
17+
* Reverse ETL
18+
* Journeys
1619

1720
## How it works
1821

1922
> info ""
20-
> You must have write access in your Segment workspace to use the Event Tester.
21-
22-
> warning ""
23-
> Make sure you have mappings enabled for your destination. The event tester only tests the enabled mappings for the destination.
23+
> The event tester only tests the enabled mappings for the destination.
2424
2525
To use the Event Tester:
2626
1. Navigate to **Connections > Destinations** and select your destination.
@@ -37,13 +37,20 @@ If your test event successfully sends to the destination, you can see in the **V
3737
* The total number of API calls that were made as one test event can result in multiple API calls.
3838
* Which mappings were successful and which ones failed
3939

40-
![Screenshot of the Event Tester with a Track test event that resulted in 4 API calls](images/event-tester2025.png)
40+
![Screenshot of the Event Tester with a Track test event that resulted in 4 API calls](images/event-tester-2025.png)
4141

42-
## FAQs
42+
You can use the filter to navigate to specific mappings.
4343

44-
#### Why can't I see the Event Tester when I log into my workspace?
44+
![Screenshot of the Event Tester filter with dropdown of different mappings](images/event-tester-filter.png)
4545

46-
The Event Tester is only accessible to users with write access in their Segment workspace (read-only users will not see the Event Tester in their workspace). 
46+
### Mappings Tester
47+
The Mappings Tester only tests a single mapping. To test specific mappings for Linked Audiences and Reverse ETL:
48+
1. Navigate to **Connections > Destinations** and select the **Reverse ETL** tab.
49+
2. Select the destination you want to test the mappings for.
50+
3. Select the mapping and click **Edit mapping**.
51+
4. Click **Test Again** in the **Send test record** section.
52+
53+
## FAQs
4754

4855
#### The Event Tester experienced an error when sending my event. Why did this happen?
4956

0 commit comments

Comments
 (0)