Skip to content

Commit 15d6b78

Browse files
committed
[netlify-build]
1 parent c38b468 commit 15d6b78

File tree

3 files changed

+52
-21
lines changed

3 files changed

+52
-21
lines changed

src/_data/sidenav/main.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -288,7 +288,7 @@ sections:
288288
- path: /connections/regional-segment
289289
title: Regional Segment
290290
- path: /connections/test-connections
291-
title: Event Tester
291+
title: Testing Connections
292292
- path: /connections/data-export-options
293293
title: Data Export Options
294294
- path: /connections/destination-data-control

src/connections/test-connections.md

Lines changed: 39 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,34 @@
11
---
2-
title: "Event Tester"
2+
title: Testing Connections
33
---
44

5+
Segment provides these 2 testing tools to enable you to test your connections between Segment and your destination:
6+
* [Event Tester](#event-tester): Test all of your enabled mappings within a destination.
7+
* [Mappings Tester](#mappings-tester): Test a single mapping configuration for your destination.
8+
9+
Both testing tools share the same underlying testing infrastructure, which ensures consistent results across your testing workflows. The results from both testers display API requests, responses, and success/failure status to help you diagnose any issues.
10+
11+
You can use the Event and Mappings Tester for these products:
12+
* [Connections](/docs/connections/)
13+
* [Linked Audiences](/docs/engage/audiences/linked-audiences/)
14+
* [Linked Events](/docs/unify/data-graph/linked-events/#testing-with-linked-events-enrichments)
15+
* [Reverse ETL](/docs/connections/reverse-etl/)
16+
* [Journeys](/docs/engage/journeys/)
17+
18+
## Event Tester
19+
520
> 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.
21+
> The Event Tester 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.
722
><br><br>You must have write access in your Segment workspace to use the Event Tester.
823
9-
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:
24+
The 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. The tester provides a comprehensive view of how your event data flows through multiple mappings. You can use the Event Tester to ensure:
1025

1126
* An event successfully arrives to a specific destination
1227
* Your new destination is configured correctly
1328

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](/docs/connections/)
16-
* [Linked Audiences](/docs/engage/audiences/linked-audiences/)
17-
* [Reverse ETL](/docs/connections/reverse-etl/)
18-
* [Journeys](/docs/engage/journeys/)
29+
The Event Tester sends a real event that appears in your end tool alongside your existing data.
1930

20-
## Using the Event Tester
31+
### Using the Event Tester
2132

2233
> info ""
2334
> The event tester only tests the enabled mappings for the destination.
@@ -31,20 +42,35 @@ To use the Event Tester:
3142
* **Generate sample event**: Segment generates a sample event for you.
3243
5. Click **Send test event to destination**.
3344

45+
3446
If your test event successfully sends to the destination, you can see in the **View test outcome** section:
35-
* The request and the response
47+
* The request, response, and status for each API call
3648
* How many of your mappings matched
37-
* The total number of API calls that were made as one test event can result in multiple API calls.
49+
* The total number of API calls that were made as one test event can result in multiple API calls
3850
* Which mappings were successful and which ones failed
51+
* The destination's API endpoint used to make the request
3952

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

42-
You can use the filter to navigate to specific mappings.
55+
You can navigate between the different API calls and can use the filter to navigate to specific mappings.
4356

4457
![Screenshot of the Event Tester filter with dropdown of different mappings](images/event-tester-filter.png)
4558

4659
## Mappings Tester
47-
When you add a destination and create a mapping in Reverse ETL, Linked Audience, and Journeys, you can test the specific mapping you created using the Mappings Tester. The Mappings Tester only tests a single mapping, and you can edit values before initiating a test.
60+
When you add a destination and create a mapping in Connections, Reverse ETL, Linked Audience, and Journeys, you can test the specific mapping using the Mappings Tester. The Mappings Tester only tests a single mapping at a time and you can edit field values before initiating a test. This helps you verify that your configured mapping works as expected.
61+
62+
Use the Mappings Tester when you need to:
63+
* Verify a single mapping configuration
64+
* Edit field values before testing a mapping
65+
* Troubleshoot a specific mapping that isn't working as expected
66+
67+
### Using the Mappings Tester
68+
To use the Mapppings Tester:
69+
1. Navigate to the product (Connections, Reverse ETL, Linked Audience, or Journeys) you want to test the mapping for.
70+
2. Select the destination that has the mapping you want to test.
71+
3. Select **Edit mapping**.
72+
4. Edit any values in the **Send test record** section.
73+
5. Click **Send test event**.
4874

4975

5076
## FAQs

src/unify/data-graph/linked-events.md

Lines changed: 12 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -180,18 +180,23 @@ In the Mappings tab, locate the **Select Mappings** section where you can enrich
180180

181181
1. Select the property field that you'd like to enrich, then select the **Enrichments** tab.
182182
2. Select the entity you want to send to your destination.
183-
- You’ll have access to all rows/columns in your data warehouse associated with the property you've selected in the previous step.
183+
- You have access to all rows/columns in your data warehouse associated with the property you've selected in the previous step.
184184
3. Add the key name on the right side, which is what Segment sends to your destination.
185+
4. Click **Save**.
185186

186-
> warning ""
187-
> At this time, Linked Events doesn't support a preview of enriched payloads.
187+
#### Testing with Linked Events Enrichments
188+
The [Event Tester and Mappings Tester](/docs/connections/test-connections/#) support testing enrichments from Linked Events, allowing you to verify that entity data is correctly attached to your events before they reach destinations. When you have Linked Events configured, these enrichments appear in your test payload, showing you exactly how profile traits will add to your events.
188189

189-
### Save your enrichments
190+
When you test mappings with Linked Events Enrichments:
191+
* You can view the enriched fields in the **Request** section of the test results.
192+
* Verify that the correct entity traits are attaching to your events based on your entity matching configuration.
193+
* The tester includes any configured Linked Events enrichments in the sample payload.
190194

191-
When you're satisfied with the mappings, click **Save**. Segment returns you to the Mappings table.
195+
This helps you confirm that the right information sends to your destinations when testing activation scenarios that rely on profile data enrichment
196+
197+
> info ""
198+
> If an enriched field appears empty in your test results, this could indicate either that the entity matching failed to find a matching profile, or that the profile exists but does not have data for that specific trait.
192199
193-
> warning ""
194-
> At this time, when you select mappings or test events, you won’t see enrichment data. Enrichment data is only available with real events.
195200

196201
## Enrichment observability
197202

0 commit comments

Comments
 (0)