Skip to content

Commit 63f399c

Browse files
Updated with suggested changes
Co-authored-by: forstisabella <[email protected]>
1 parent 1e074d9 commit 63f399c

File tree

1 file changed

+1
-1
lines changed
  • src/connections/destinations/catalog/actions-segment

1 file changed

+1
-1
lines changed

src/connections/destinations/catalog/actions-segment/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,4 +34,4 @@ The Segment Connections destination enables you to mold data extracted from your
3434
The Segment Connections destination sends data to Segment's Tracking API, which has cost implications. New users will count as new MTUs and each call will count as an API call. For information on how Segment calculates MTUs and API calls, please see [MTUs, Throughput and Billing](/docs/guides/usage-and-billing/mtus-and-throughput/).
3535

3636
### Test Mapping
37-
The **Test Mapping** feature on the Mapping page does not send events to the Tracking API. It will only validate the mappings and confirm that the event will be accepted by the Tracking API. To send and validate the event in your source, please run a RETL sync.
37+
The **Test Mapping** feature on the Mapping page does not send events to the Tracking API. It only validates the mappings and confirms that the event will be accepted by the Tracking API. To send and validate the event in your source, run a RETL sync.

0 commit comments

Comments
 (0)