Skip to content

Commit 6052ebe

Browse files
committed
event tester [netlify-build]
1 parent fd7739b commit 6052ebe

File tree

3 files changed

+14
-22
lines changed

3 files changed

+14
-22
lines changed

src/connections/destinations/actions.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -157,14 +157,13 @@ To delete a destination action: click the action to select it, and click **Delet
157157
This takes effect within minutes, and removes the action completely. Any data that would have gone to the destination is not delivered. Once deleted, the saved action cannot be restored.
158158

159159
## Test a destination action
160-
To test a destination action, follow the instructions in [Testing Connections](/docs/connections/test-connections/). You must enable a mapping in order to test the destination. Otherwise, this error occurs: *You may not have any subscriptions that match this event.*
160+
To test a destination action, follow the instructions in [Event Tester](/docs/connections/test-connections/). You must enable a mapping in order to test the destination. Otherwise, this error occurs: *You may not have any subscriptions that match this event.*
161161

162162
You can also test within the mapping itself. To test the mapping:
163163
1. Navigate to the **Mappings** tab of your destination.
164164
2. Select a mapping and click the **...** and select **Edit Mapping**.
165-
3. In step 2 of the mappings edit page, click **Load Test Event from Source** to add a test event from the source, or you can add your own sample event.
166-
4. Scroll to step 4 on the page, and click **Test Mapping** to test the mapping and view the response from the destination.
167-
165+
3. In step 2 of the mappings edit page, click **Load event from source** to add a test event from the source, or you can select **Generate sample event** for Segment to generate a sample event for you. Optionally, you can enter your own event instead.
166+
4. Scroll to step 5 on the page, and click **Send test event** to test the mapping and view the response from the destination.
168167

169168
> info "Test Mapping might not return the events you're looking for"
170169
> Segment only surfaces a small subset of events for the Test Mapping feature and might not always return the event you're looking for. If you'd like to test with a specific event, copy a specific event from your [Source Debugger](/docs/connections/sources/debugger/) and paste it into the **Add test event** interface.
297 KB
Loading

src/connections/test-connections.md

Lines changed: 11 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -8,11 +8,17 @@ Segment's Event Tester enables you to test your connections between Segment and
88
* ensure an event successfully arrives to a specific destination
99
* ensure your new destination is configured correctly
1010

11+
The Event Tester sends a real event that will appear in your end tool alongside your existing data.
12+
13+
1114
> 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.
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.
1316
1417
## How it works
1518

19+
> info ""
20+
> You must have write access in your Segment workspace to use the Event Tester.
21+
1622
> warning ""
1723
> Make sure you have mappings enabled for your destination. The event tester only tests the enabled mappings for the destination.
1824
@@ -25,28 +31,15 @@ To use the Event Tester:
2531
* **Generate sample event**: Segment generates a sample event for you.
2632
5. Click **Send test event to destination**.
2733

28-
If your test event successfully sends to the destination, you can see in the **View test outcome section:
34+
If your test event successfully sends to the destination, you can see in the **View test outcome** section:
2935
* The request and the response
3036
* How many of your mappings matched
31-
* The total number of API calls that were made
37+
* The total number of API calls that were made as one test event can result in multiple API calls.
3238
* Which mappings were successful and which ones failed
3339

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

35-
36-
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. 
38-
39-
![Screenshot of the popup that appears when you click the Send test event button.](/docs/guides/images/asset_Yxw1DJqb.png)
40-
41-
**5. View the Partner API response**
42-
43-
On the right hand side of the Event Tester you will see the response from the partner API. At the top, Segment provide of summary of the response. Below is the raw response payload Segment received that you can use for further debugging if necessary. 
44-
45-
![A screenshot of the Event Tester with a successful response from the destination](images/event-tester_il6mvexS.png)
46-
47-
If you are receiving an error and are unsure how to fix the issue, visit the partner docs (for example [https://developers.google.com/analytics/devguides/reporting/core/v3/errors](https://developers.google.com/analytics/devguides/reporting/core/v3/errors){:target="_blank”}) or contact the partner support team. 
48-
49-
## FAQ
42+
## FAQs
5043

5144
#### Why can't I see the Event Tester when I log into my workspace?
5245

0 commit comments

Comments
 (0)