CustomFit Destination
Destination Info
- Accepts Page, Identify, and Track calls
- Refer to it as customfitai, or CustomFit.ai in the Integrations object
- This destination is in Beta
CustomFit.ai is an intelligent App Experience Engine
for B2C apps(Mobile/Web/IoT), with which one can effortlessly craft hyper-personalized app experiences & alternative user journeys to each of their user or segment of users with zero code. Every user is unique, so should be your app.
This destination is maintained by CustomFit.ai. For any issues with the destination, contact the CustomFit Support team.
This document is about a destination which is in beta
This means that the CustomFit Destination is in active development, and some functionality may change before it becomes generally available.
Getting Started
- From the Segment web app, click Catalog.
- Search for “CustomFit.ai” in the Catalog, select it, and choose which of your sources to connect the destination to.
- Enter the “Server Key” into your Segment Settings UI which you can find from your CustomFit.ai dashboard.
Identify
Identify
lets you tie a user to their actions and record traits about them. It includes a unique User ID and any optional traits you know about them like their email, name, etc., Read more about the Identify method to understand what it does. An example call would look like:
analytics.identify("user_id", {
name: "Peter Gibbons",
email: "peter@example.com",
plan: "premium",
logins: 5
});
Segment handles the following mapping:
- Segment
identify
event userId to CustomFit.aiuser_customer_id
field. - Segment
identify
event traits to CustomFit.aiproperties
.
Identify calls will be sent to CustomFit.ai as an identify
event. You can find the user details in users profile page.
Track
The track
API call is used to record any actions your users perform, along with any properties that describe the action. Each action is known as an event. Read more about the Track method to understand what it does. An example call would look like:
analytics.track("Registered", {
user_id : "97980cfea0067",
plan: "Pro Annual",
accountType: "Facebook"
});
Segment handles the following mapping:
- Segment
track
event to CustomFit.aievent_customer_id
. - Segment
track
event userId to CustomFit.aiuser_customer_id
. - Segment
track
event properties to CustomFit.ai eventdata
Note : We expect
identify
event to be invoked beforetrack
event for a particular user.
Track calls will be sent to CustomFit.ai as an track
event. You can find the user level track details under events tab of user profile.
Page
The page
call lets you record whenever a user sees a page of your website, along with any optional properties about the page. Read more about the Page method to understand what it does. An example call would look like:
analytics.page("Home", {
title : "CustomFit.ai",
url : "http://customfit.ai"
});
Segment handles the following mapping:
- Segment
page
event name to CustomFit.ainame
.
Page calls will be sent to CustomFit.ai as a pageview
event.
Screen
The screen
call lets you record whenever a user sees a screen, the mobile equivalent of page, in your mobile app, along with any properties about the screen. Read more about the Screen method to understand what it does. An example call would look like:
[[SEGAnalytics sharedAnalytics] screen:@"Home"
properties:@{ @"Feed Type": @"private" }];
Segment handles the following mapping:
- Segment
screen
event name to CustomFit.ainame
.
Screen calls will be sent to CustomFit.ai as a screenview
event.
Engage
You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.
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 false
.
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 CustomFit may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.
Settings
Segment lets you change these destination settings from the Segment app without having to touch any code.
Setting | Description |
---|---|
API Key (required) |
string . Paste the server key of your app here. (Refer https://docs.customfit.ai/customfit-ai/keys) |
This page was last modified: 08 Mar 2022
Need support?
Questions? Problems? Need more info? Contact Segment Support for assistance!