Skip to content

Commit eccf20b

Browse files
authored
Merge pull request #7913 from segmentio/profiles-sync-audit
Batch edits (Profiles Sync, Semantic, and Test Connections)
2 parents 43a82b7 + 9cde989 commit eccf20b

File tree

3 files changed

+7
-9
lines changed

3 files changed

+7
-9
lines changed

src/connections/spec/semantic.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,13 +4,11 @@ title: 'Spec: Semantic Events'
44

55
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.
66

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

99
- [Mobile](/docs/connections/spec/mobile)
1010
- [A/B Testing](/docs/connections/spec/ab-testing)
1111
- [Ecommerce](/docs/connections/spec/ecommerce/v2/)
1212
- [Email](/docs/connections/spec/email)
1313
- [Live Chat](/docs/connections/spec/live-chat)
1414
- [Video](/docs/connections/spec/video)
15-
16-
In the future Segment plans to standardize event names from other data sources as well.

src/connections/test-connections.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
---
2-
title: Testing Connections
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.
5+
Segment provides two tools for validating the connection between Segment and a destination:
6+
* [Event Tester](#event-tester): Test all enabled mappings within a destination.
77
* [Mappings Tester](#mappings-tester): Test a single mapping configuration for your destination.
88

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

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

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

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

src/unify/profiles-sync/overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Profiles Sync Overview
2+
title: Profiles Sync overview
33
plan: unify
44
---
55

0 commit comments

Comments
 (0)