Once the Segment library is integrated with your app, toggle Countly on in your Segment destinations catalog, and add your application’s App Key and Server URL which you can find in your Countly Application Management. If you’re using their cloud hosted solution (not hosting your own Count.ly server), then your Server URL is
These new settings will take up to an hour to propogate to all of your existing users. For new users it’ll be instanteneous!
Countly is built to help you better understand your user’s behavior. To accomplish that, you’ll want to
track your user’s actions in detail.
All you have to do is make a
track call to send a custom event to Countly. The event name will map to the countly “key” and we automatically set “count” to 1. If you add properties to the event those will be passed to Countly as well.
It’s easy to track revenue in Countly through Segment. All you have to do is use our
track method with a property labeled
revenue. The value must be a number.
Supported Sources and Connection Modes
The first step is to make sure Countly 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.
To learn more about about Connection Modes and what dictates which we support, see here.
This destination requires a Device-based Connection Mode for Mobile data. Follow the steps above to ensure you have packaged the Countly SDK with Segment’s.
Segment lets you change these destination settings from your Segment dashboard without having to touch any code.
You can find your App Key on your Countly server. It should be 40 characters long, and look something like this:
You’ll need to add your own Countly Server URL here.
Questions? Problems? Need more info? Contact us, and we can help!