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, contact the Mabl Support team.
This document is about a destination which is in beta
This means that the Mabl Destination is in active development, and some functionality may change before it becomes generally available.
- From the Destinations catalog page in the Segment App, click Add Destination.
- Search for “mabl” in the Destinations Catalog, and select the mabl destination.
- Choose which Source should send data to the mabl destination.
- Go to the mabl api settings page (or navigate in the mabl app to Settings > APIs), find and copy the API key.
- Enter the API Key in the mabl destination settings in Segment.
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.
If you’re not familiar with the Segment Specs, 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’re not familiar with the Segment Specs, 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 is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property
order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Engage sets that value to
When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.
Real-time to batch destination sync frequency
Real-time audience syncs to Mabl may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.
Segment lets you change these destination settings from the Segment app without having to touch any code.
This page was last modified: 08 Mar 2022
Questions? Problems? Need more info? Contact Segment Support for assistance!