AB Smartly Destination
A/B Smartly provides an on-premise, full-stack experimentation platform for engineering and product teams that do continuous experimentation embedded into their development process. A/B Smartly’s real-time analytics helps engineering and product teams ensure that new features will improve the customer experience without breaking or degrading performance and/or business metrics.
This destination is maintained by A/B Smartly. For any issues with the destination, contact A/B Smartly’s Support.
A/B Smartly works differently than other Segment destinations. Because A/B Smartly SDKs are used to modify and deliver experiences to users, you must implement them at a point in your website or app that allows them to make visual modifications for users.
A/B Smartly requires you to integrate the A/B Smartly SDKs natively, before the Segment snippet or implementation.
Even though Segment maps
track, and in some cases
screen events to A/B Smartly’s
track events, you must implement the snippet on your site to ensure that experiments run.
Segment provides specific implementation details for A/B Smartly in the sections below, in addition to details of the out-of-the-box mappings that Segment’s A/B Smartly integration handles transparently.
- From the Destinations catalog page in the Segment App, click Add Destination.
- Search for “A/B Smartly” in the Destinations Catalog, and select the “A/B Smartly” destination.
- Choose which Source should send data to the “A/B Smartly” destination.
- Go to the A/B Smartly dashboard(https://your-org-name.absmartly.com/apikey/list), find and copy the “API key” that you created for segment.
- Enter the “API Key” in the “A/B Smartly” destination settings in Segment.
- If the integration requests for an Application name go to your A/B Smartly dashboard (
https://your-org-name.absmartly.com/application/create) and create an Application named “Segment”, or whatever you would like to call it. Use that name in the Application field of the integration settings.
- Add also your A/B Smartly Collector endpoint. It’s the same endpoint that you are using in all your A/B Smartly SDKs.
- Enter the environment from your Environment list (
https://your-org-name.absmartly.com/environment/list) that should receive your Segment data. Most likely it will be the production one.
- And finally a mapping of Segment Identities to A/B Smartly Units(
https://your-org-name.absmartly.com/unit/list). You should map all of your Segment identities that you would like to use in your A/B tests to the units that you already have in A/B Smartly. Users must map all the identity types, but not for the individual users. Map all of your ids in your Unit List(
- Optionally go to “Goal Mapping” and start adding the track calls that you would like to see showing up on A/B Smartly as goals. You only need to create a name mapping if the name of the goal on A/B Smartly’s platform is different from the name of the track call in Segment.
Take a look at the Page method documentation to understand what it does. An example call would look like:
Segment sends Page calls to A/B Smartly as a
pageview goal. The goal name is
<page_name>_pageview. The page name is lower-cased and any spaces or special characters are replaced with underscores. For example, a view of the “Home” page triggers the
home_pageview goal. If the goal doesn’t exist in the A/B Smartly web console, it is ignored.
Take a look at the Screen method documentation to understand what it does. An example call would look like:
[[SEGAnalytics sharedAnalytics] screen:@"Home"];
Segment sends Screen calls to A/B Smartly as a
screenview goal. The goal name is
<screen_name>_screenview. The screen name is lower-cased and any spaces or special characters are replaced with underscores. For example, a view of the “Home” screen triggers the
home_screenview goal. If the goal doesn’t exist in the A/B Smartly web console, it is ignored.
Take a look at the Track method documentation to understand what it does. An example call would look like:
analytics.track('Login Button Clicked')
Segment sends Track calls to A/B Smartly as a
track event. A/B Smartly’s track calls are the way to track goals.
analytics.track('booking') is equivalent to an A/B Smartly SDK track call
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 AB Smartly 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.
|Enable App Screen View Tracking
Send Segment Screen view events to A/B Smartly as goals. The goal name will be
|Enable Exposure Tracking
Send Group event payloads directly to the A/B Smartly collector.
|Enable Page View Tracking
Send Segment Page view events to A/B Smartly as goals. The goal name will be
Optional mapping of Segment event to A/B Smartly goal. Find and create goals in the settings page of the A/B Smartly web console.
Mapping of Segment identities to A/B Smartly units. Find and create unit types in the settings page of the A/B Smartly web console.
This page was last modified: 25 Apr 2022
Questions? Problems? Need more info? Contact Segment Support for assistance!