Merge pull request #6024 from segmentio/repeater-changes

[Segment][Segment Profiles] Add FAQ regarding mapping-tester behavior

Author: varadarajan-tw

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

@@ -34,3 +34,6 @@ The Segment Profiles destination is not subject to API call or MTU costs. Any us
 
 ### Succesful syncs but no changes on profiles
 Make sure that the Endpoint Region setting matches the region of your workspace. If the region is correct and you don't see any profile changes, [contact Segment](https://segment.com/help/contact/){:target="_blank"}.
+
+### Test Mapping
+The **Test Mapping** feature on the Mapping page does not send events to Profiles. 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 profile, please run a RETL sync.

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

@@ -32,3 +32,6 @@ The Segment Connections destination enables you to mold data extracted from your
 
 ### API Calls and MTUs
 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/).
+
+### Test Mapping
+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.