Skip to content

Commit eea2fd9

Browse files
gezgblackShamil Ataevsanscontextsanscontext
authored
mabl destination doc change (#1013)
* mabl destination doc change * copy edit Co-authored-by: Shamil Ataev <[email protected]> Co-authored-by: sanscontext <[email protected]> Co-authored-by: LRubin <[email protected]>
1 parent d96d23e commit eea2fd9

File tree

1 file changed

+8
-4
lines changed
  • src/connections/destinations/catalog/mabl

1 file changed

+8
-4
lines changed

src/connections/destinations/catalog/mabl/index.md

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,10 +14,14 @@ _**NOTE:** The mabl Destination is currently in beta, which means that they are
1414

1515
{% include content/connection-modes.md %}
1616

17-
1. From your Segment UI's Destinations page click on "Add Destination".
18-
2. Search for "mabl" within the Destinations Catalog and confirm the Source you'd like to connect to.
19-
3. Drop the "API Key," accessible from into your from your mabl workspace's [API keys page](https://app-dev.mabl.com/workspaces/-/settings/apis), into the Segment Settings UI.
20-
4. mabl processes the usage data into rolling 24 hour summaries hourly. It may take up to an hour for usage to begin to populate in your test coverage metrics.
17+
18+
1. From the Destinations catalog page in the Segment App, click **Add Destination**.
19+
2. Search for "mabl" in the Destinations Catalog, and select the mabl destination.
20+
3. Choose which Source should send data to the mabl destination.
21+
4. Go to the [mabl api settings page](https://app.mabl.com/workspaces/-/settings/apis) (or navigate in the mabl app to **Settings > APIs**), find and copy the API key.
22+
5. Enter the API Key in the mabl destination settings in Segment.
23+
24+
mabl processes the usage data into rolling 24 hour summaries, every hour. It can take up to an hour for usage to appear in your test coverage metrics.
2125

2226
## Page
2327

0 commit comments

Comments
 (0)