Skip to contentSkip to navigationSkip to topbar
On this page
Looking for more inspiration?Visit the
(information)
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

Countly Destination


Destination Info
  • Accepts Page, Alias, Group, Identify and Track calls.
  • Refer to it as Countly in the Integrations object
Connection Modes
Device-modeCloud-mode
Web Web
Mobile Mobile
Server Server

The Countly destination source code for iOS(link takes you to an external page) and Android(link takes you to an external page) is available on GitHub.


Getting Started

getting-started page anchor

To get started with Countly and Segment, add the iOS, Android or React Native libraries to your mobile app.

After you integrate the appropriate destination with your app, add the Countly destination from the destination catalog, and add your application's App Key and Server URL which you can find on the Countly Application Management screen.

These new settings take up to an hour to propagate to existing users, but is instantaneous for new users.


Countly helps you better understand your user's behavior. To accomplish that, track your user's actions in detail.

When you call track from the iOS or Android library, Segment records an event with Countly. track takes the name of the event and any optional properties you want to associate with the event.

Custom Events

custom-events page anchor

Make a track call to send a custom event to Countly. The event name maps to the Countly "key" and "count" is set to 1. Segment passes properties you add to the event to Countly.

It's easy to track revenue in Countly through Segment. Use the track method with a property labeled revenue. The value must be a number.


Segment lets you change these destination settings from the Segment app without having to touch any code.

Property nameTypeRequiredDescription
App Keystring
required

You can find your App Key on your Countly server. It should be 40 characters long, and look something like this: c801156663bfcc4694aafc0dd26023a6d9b9544a.


Server URLstring
required

You'll need to add your own Countly Server URL here.