Only mabl offers scriptless cross-browser web testing, auto-healing tests, visual testing, and diagnostics in one simple service. mabl helps you improve the speed and quality of your release pipeline by allowing you to test every release, at scale, on a single platform, with no infrastructure to manage.
This destination is maintained by mabl. For any issues with the destination, please reach out to the mabl team.
NOTE: The mabl Destination is currently in beta, which means that they are still actively developing the destination. This doc was last updated on 10 June, 2019. If you are interested in joining their beta program or have any feedback to help improve the mabl Destination and its documentation, please let their team know!
The first step is to make sure mabl supports the source type and connection mode you’ve chosen to implement. You can learn more about what dictates the connection modes we support here.
- From your Segment UI’s Destinations page click on “Add Destination”.
- Search for “mabl” within the Destinations Catalog and confirm the Source you’d like to connect to.
- Drop the “API Key,” accessible from into your from your mabl workspace’s API keys page, into the Segment Settings UI.
- 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.
If you haven’t had a chance to review our spec, please take a look to understand what the Page method does. An example call would look like:
Page calls are used by mabl to build a model of the pages in your app and determine the number of unique users interacting with each page. Page calls are particularly useful because they can help inform mabl’s model of a page’s URL patterns. You can find this information in your workspace’s coverage page under the “Daily Users” column.
If you haven’t had a chance to review our spec, please take a look to understand what the Track method does. An example call would look like:
analytics.track('Clicked Login Button')
Track calls are used by mabl to build a model of the pages in your app and determine the number of unique users interacting with each page. You can find this information in your workspace’s coverage page under the “Daily Users” column.
For user-property destinations, an identify call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property
order_completed_last_30days: true, and when this user no longer satisfies we will set that value to
When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.
Segment lets you change these destination settings via your Segment dashboard without having to touch any code.
The mabl API Key is available in the mabl up under settings > APIs or bu navigating directly to https://app.mabl.com/workspaces/-/settings/apis
Adding mabl to the integrations objectTo add mabl to the
integrationsJSON object (for example, to filter data from a specific source), use one of the 1 valid names for this integration: