You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/mabl/index.md
+8-4Lines changed: 8 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,10 +14,14 @@ _**NOTE:** The mabl Destination is currently in beta, which means that they are
14
14
15
15
{% include content/connection-modes.md %}
16
16
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.
0 commit comments