Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions src/connections/spec/semantic.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,13 +4,11 @@ title: 'Spec: Semantic Events'

One of the core components of the Segment [Spec](/docs/connections/spec) is the [Track](/docs/connections/spec/track) call. It describes any arbitrary event that the user has triggered. For some industry verticals and applications, Segment has standardized event names. For Ecommerce tracking, for example, there are **specific event names and properties** that we recognize semantically. This semantic meaning allows Segment to specially recognize and transform key events before sending them off to each different tool.

There are a few places where Segment has standardized event names and properties already:
Segment currently standardizes event names and properties in the following places:

- [Mobile](/docs/connections/spec/mobile)
- [A/B Testing](/docs/connections/spec/ab-testing)
- [Ecommerce](/docs/connections/spec/ecommerce/v2/)
- [Email](/docs/connections/spec/email)
- [Live Chat](/docs/connections/spec/live-chat)
- [Video](/docs/connections/spec/video)

In the future Segment plans to standardize event names from other data sources as well.
10 changes: 5 additions & 5 deletions src/connections/test-connections.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
---
title: Testing Connections
title: Testing connections
---

Segment provides these 2 testing tools to enable you to test your connections between Segment and your destination:
* [Event Tester](#event-tester): Test all of your enabled mappings within a destination.
Segment provides two tools for validating the connection between Segment and a destination:
* [Event Tester](#event-tester): Test all enabled mappings within a destination.
* [Mappings Tester](#mappings-tester): Test a single mapping configuration for your destination.

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.
Expand Down Expand Up @@ -36,7 +36,7 @@ The Event Tester sends a real event that appears in your end tool alongside your
To use the Event Tester:
1. Navigate to **Connections > Destinations** and select your destination.
2. Click the **Event Tester** tab.
3. Select the type of test event. You can choose from: Track, Identify, Page, Screen, Group.
3. Select the type of test event. You can choose from: Track, Identify, Page, Screen, and Group.
4. Enter your test event payload. You can type in your own event or choose from **Load event from source** or **Generate sample event**.
* **Load event from source**: Segment loads an event based on your source.
* **Generate sample event**: Segment generates a sample event for you.
Expand Down Expand Up @@ -77,7 +77,7 @@ To use the Mapppings Tester:

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

If you experience an error, [let Segment know](mailto:[email protected]) and the Segment team will help you troubleshoot the issue.
If you experience an error, [contact Segment support](mailto:[email protected]) and we'll help you troubleshoot the issue.

#### Is this feature available for Data Lakes?

Expand Down
2 changes: 1 addition & 1 deletion src/unify/profiles-sync/overview.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
title: Profiles Sync Overview
title: Profiles Sync overview
plan: unify
---

Expand Down
Loading