<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Countly Engineering Team on Medium]]></title>
        <description><![CDATA[Stories by Countly Engineering Team on Medium]]></description>
        <link>https://medium.com/@countly_dev?source=rss-a4fbe317bf21------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*CNXIjvTaI8mjVR28SDU1hA.png</url>
            <title>Stories by Countly Engineering Team on Medium</title>
            <link>https://medium.com/@countly_dev?source=rss-a4fbe317bf21------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 18:18:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@countly_dev/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Tracking users in Countly]]></title>
            <link>https://medium.com/@countly_dev/tracking-users-in-countly-80bbe4ed0ad6?source=rss-a4fbe317bf21------2</link>
            <guid isPermaLink="false">https://medium.com/p/80bbe4ed0ad6</guid>
            <category><![CDATA[user-tracking]]></category>
            <category><![CDATA[countly]]></category>
            <category><![CDATA[analytics]]></category>
            <dc:creator><![CDATA[Countly Engineering Team]]></dc:creator>
            <pubDate>Mon, 25 Nov 2019 09:06:31 GMT</pubDate>
            <atom:updated>2023-05-17T08:32:25.622Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*1GthVA4StT8SxdUX9-9j7w.jpeg" /><figcaption>Countly has the ability to track every device or user. This feature presents several approaches spanning different use cases. In this blog post, we depict those approaches, providing the pros and cons of each in detail.</figcaption></figure><p>Before diving into different methods, we need to understand how Countly tracks users. This process is realized through the notion of “device_id”. This ID is normally (by default) generated on the environment the Countly SDK runs on (e.g., a smartphone, a web browser, or a desktop application). It is used to identify the user who directly interacts with the device.</p><p>But what happens if there are several users and several devices that are used interchangeably? What happens if a user can log in and log out, hence transitioning between a known and an anonymous user? In such cases, you should experiment and decide on the correct user tracking strategy before going into production to minimize negative effects.</p><p>Depending on the selected strategy, you can change what a user means in the Countly dashboard.</p><h3>Default user tracking</h3><p>By default, when implementing Countly SDK, Countly will generate a random value (called <strong>device_id</strong>) to identify the user or use some platform-specific value, for example, IDFV for iOS and Advertising ID for Android.</p><p>Generally speaking, this way assigns a unique ID to a particular user who is the owner of that device.</p><p><strong>Pros</strong></p><ul><li>The easiest and fastest implementation, with no additional steps, needs to be followed, apart from doing default SDK implementation.</li></ul><p><strong>Cons</strong></p><ul><li>If multiple different users use the same device, they will be identified as a single user in the Countly dashboard and will have a single profile under User Profiles.</li><li>If the same user uses multiple devices, each device will be identified as a separate user in the Countly dashboard. Hence the same user will have separate user profiles, which is by nature not the case.</li><li>Depending on the platform, if app storage is reset or the app is uninstalled and installed back again, this user may be identified as a new user, and a new user profile is created. This highly depends on how the platform behaves, and we suggest that you check this document to understand what happens in such cases.</li></ul><h3>Tracking known users</h3><p>This method, as opposed to the first one, helps Countly identify and track users if they are “known” to you. It is used in cases when the default Countly generated <strong>device_id</strong> to track the same user across multiple devices or different users on the same device is not appropriate. In this case, you need to provide your own “user identifier”. This unique identifier can be a user email address or an internal customer id — or, simply said, anything unique to that user. Countly SDK then can use this string to use as so it would be used as device_id. From this point on, Countly will know exactly what user it is, and the same <strong>device_id</strong> will be used even on different devices.</p><p>In order to accomplish that, you need to provide device_id upon SDK initialization and not afterward. That might fit applications that can identify their users right away, or have little or no actions before authenticating users.</p><p>This would be the case when the user inside the Countly dashboard directly corresponds to your customer (e.g., 1 Countly user = 1 company customer, regardless of the device/platform they use).</p><p><strong>Pros</strong></p><ul><li>Each of your customers will be exactly one single user inside Countly and have one user profile.</li></ul><p><strong>Cons</strong></p><ul><li>If you don’t know your user ID right away and would know it only after the user authenticates, you will miss all the actions that were made before authentication.</li></ul><h3>Known user with pre-tracking</h3><p>To tackle the problem of missing the data before user authentication, it is possible to launch the Countly SDK in an “offline mode”. It will track data but will not send it until you provide your user ID and enable “online mode”.</p><p>This way, you can initialize SDK in an offline mode right when the app starts, track everything needed, and when the user finally authenticates, you get your user’s ID. Then, you can set it as device_id and enable online mode, so Countly SDK will start sending data. All previously collected data in offline mode will also be assigned to that user.</p><p>For the definition of the user, nothing changes. It still directly corresponds to your customer.</p><p><strong>Pros</strong></p><ul><li>Each of your customers will be exactly one single user inside Countly and have 1 User profile.</li><li>You will have the opportunity to be able to collect and visualize data before the user authenticates, but only after authentication.</li></ul><p><strong>Cons</strong></p><ul><li>If your user doesn’t authenticate, you will never receive any data from this user.</li></ul><h3>Managing anonymous and known users together</h3><p>It is also possible to collect data of both user states (before login and after login), and SDK provides two ways to manage that by allowing to change device_id after SDK initialization.</p><p>First, you can change the <strong>device_id</strong> without merging. That will simply end the session of the old device_id and sync all the left data and start a new session for the new device_id. This is handy, for example, when multiple users use the same device, and you want to switch them.</p><p>The second way is that you change <strong>device_id</strong> without starting a new session but merging both users on the server-side. So this will basically create a new user for the new device_id if it was not already created. Then merge the data of the user with the old device_id into this new one. And afterward, delete the user with the old device_id from Countly.</p><p>This is handy when for example, you are firstly tracking an anonymous user with Countly generated device_id, but then the user authenticates, and you retrieve the id for this user and change it in SDK, allowing to merge both users on the server. It means that all that anonymous user had, all events and properties will now be assigned to an identified user, and the old user will be deleted.</p><p>You can implement different strategies that utilize these two options.</p><p>For example, you can start tracking a user as anonymous with a Countly-generated id. Then upon authentication, change <strong>device_id</strong> to your own id by merging on the server. And then, when the user logs out, you can change it back to anonymous generated id without user merge.</p><p>The problem is that when the user logs out, it will create a new user again inside the Countly dashboard, and there will be two different user profiles: one with your provided id and the other with a random id.</p><p>So the user on the Countly dashboard represents both your customer and anonymous user before authentication. And in some cases, it could be the same user but with two different user profiles inside Countly.</p><p>And for applications like banking, where the user must log in and log out every day, that can basically double the user count, thus skewing the data.</p><p>You can try to tweak this strategy to minimize double-user creation. For example, on logout, let’s not change device_id at all and keep using your provided one. But instead, upon authentication, we check the type of device_id you provided, and then we switch device_id without merging. But if the type of device_id is Countly generated, then we change device_id with user merging.</p><p>Then we would have the scenario that looks like this:</p><ul><li>The app starts for the first time, and a Countly-generated id is used.</li><li>Upon authentication, you check that the current device_id is Countly generated, which means when switching to your provided <strong>device_id,</strong> we need to do merging</li><li>When the user logs out, we don’t do anything.</li><li>When the user logs in, we check the current device_id, and it is your provided one. So we switch to authenticated user’s device_id without merging. If it is the same user and the same id SDK currently has, nothing will happen. But if it is a different id, then probably another user logged in, and SDK will stop the current session and start a new one for a new user.</li></ul><p>These are just a couple of examples of how you could manage tracking data for both known users and anonymous ones. The actual implementations may differ based on your application specifics.</p><p><strong>Pros</strong></p><ul><li>You get to track data for both users before authentication and after</li></ul><p><strong>Cons</strong></p><ul><li>In some cases, aggregated data may be skewed and overreport users and new users due to creating many anonymous users.</li><li>Merging can be quite a performance-intensive process, especially if the user that is merged has a lot of data or there are lots of users to merge.</li><li>In some cases, the same user may have a user profile for both states: a known user and an anonymous one.</li><li>More difficult SDK integration and customization is required</li></ul><h3>Other interesting strategies</h3><p>We have seen our customers using their own different implementations, and one of them was quite effective, to have it mentioned here also. The strategy involved actually dividing the onboarding (pre-authenticated users) and authenticated users into separate Countly apps.</p><p>The customer had quite long and complicated onboarding with the registration form. But once that is done, there is nothing else to do before the login screen. So they wanted to utilize 1 user profile per 1 customer inside the Countly dashboard, but they also wanted to track how a user is on boards, how long it takes, and where they would drop off if registration was not finished.</p><p>That is why sending onboarding data to one app and then sending data of known users to the other app made perfect sense for them.</p><p>You could also leave a custom property with your user id once registration is complete on the onboarding app just to be able to tie both users together. Still, overall, this shows that many different interesting approaches could be taken to find what you need.</p><p>Just to note, this approach would require changing app_key in the running SDK, and currently, not all SDKs support that, and you would need to consult Countly or make modifications yourself on certain SDKs.</p><h3>Conclusion</h3><p>There are different user tracking strategies available. Each one has its own pros and cons. You need to understand what kind of data you want to collect and what you want the word “user” to mean exactly for you in the Countly dashboard. Make sure you know the options, and then you will be able to find the best way that fits you with all its trade-offs. If you have any questions or suggestions, let us know on our community discord: <a href="https://discord.gg/countly">https://discord.gg/countly</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80bbe4ed0ad6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[User Management in Countly]]></title>
            <link>https://medium.com/@countly_dev/user-management-in-countly-b5245cb3555d?source=rss-a4fbe317bf21------2</link>
            <guid isPermaLink="false">https://medium.com/p/b5245cb3555d</guid>
            <category><![CDATA[authentication]]></category>
            <category><![CDATA[user-management]]></category>
            <category><![CDATA[api-integration]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[product-analytics]]></category>
            <dc:creator><![CDATA[Countly Engineering Team]]></dc:creator>
            <pubDate>Thu, 11 Oct 2018 16:07:41 GMT</pubDate>
            <atom:updated>2020-02-13T08:03:54.604Z</atom:updated>
            <content:encoded><![CDATA[<h4>Countly allows you to assign different user roles to many members of your team. These roles include global admin, admin and regular “user”. Each role comes with its own capabilities and restrictions. This blog post will explain how you can manage your dashboard users.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2qLmAj9rSGd73KEP3kNM0Q.png" /></figure><p>Countly, by default, includes a built-in user management system, and to be able to have a higher degree of control, you can take help from many approaches. By default, you can always add any type of users and restrict any menus (sections) if you don’t want that user to reach out to a particular feature.</p><p>However, in an enterprise, there are several management levels, stakeholders, product owners and backend systems that may require a more automated user management infrastructure.</p><p>This may require a better handling of users either via API, tokens, redirection authentication or active directory/LDAP.</p><p>Below we will discuss about each and every authentication and user management methods, other than the usual, dashboard-led way.</p><h4><strong>Method 1: User management through API</strong></h4><p>The main idea behind managing users with Countly API is that you, can hook Countly API calls in your system to mimic what is done there and reflect in Countly.</p><p>Examples:</p><ol><li>Creating a user (<a href="https://api.count.ly/reference#iuserscreate">https://api.count.ly/reference#iuserscreate</a>)</li><li>Updating user’s information (<a href="https://api.count.ly/reference#iusersupdate">https://api.count.ly/reference#iusersupdate</a>)</li><li>Deleting a user (<a href="https://api.count.ly/reference#iusersdelete">https://api.count.ly/reference#iusersdelete</a>)</li></ol><p>API based user management fits well when you want to create, edit and update users remotely, or when you have a large number of users on your Countly instance.</p><h4><strong>Method 2: Authentication through tokens</strong></h4><p>Tokens are similar to API keys — they are created by specific Countly user and inherits creator’s privileges, however they can be easily restricted also.</p><p>As an example, you can create a token that can only be used to <em>login </em>the user, who created a token and would only work for specific amount of time (e.g 15 minutes).</p><p>This method can also work together with User API management mentioned in the first point we explained above, because you would need user’s api key. However, you could also create a login token once, that never expires upon user creation, and use it every time as a link to user’s Countly dashboard access.</p><p>For more information about authentication of users through tokens, please <a href="https://api.count.ly/reference#itokencreate">see this documentation</a>.</p><h4><strong>Method 3: Redirection authentication</strong></h4><p>Countly also has <a href="https://count.ly/plugins/single-sign-on">single-sign-on (SSO) plugin</a> that allows to authenticate users through redirection in browser.</p><p>This would work together with User API management mentioned in method 1, since you would need to know user’s api key (the user, that you want to authenticate). Hence, you would get that when you create user and store somewhere in your system.</p><p>One example use case is when you have your own web service, where user needs to authenticate, and upon that authentication, you also redirect user to Countly and authenticate user there and then redirect back to your system.</p><p>For more information about SSO plugin, please <a href="https://count.ly/plugins/single-sign-on">see this page</a>.</p><h4><strong>Method 4: Active Directory</strong></h4><p><a href="https://count.ly/plugins/active-directory">Active Directory</a> plugin replaces the inner Countly user system and only creates temporary users during authentication and keeps them while user is logged in and deletes upon logout.</p><p>You can define what role and access to which app can specific AD role have by mapping such roles in configuration.</p><p>More information on Active Directory plugin, and how to use it is available <a href="https://resources.count.ly/docs/active-directory-integration">here</a>.</p><h4>Conclusion</h4><p>Just like Countly being very extensive and flexible in terms of features, the same applies when it comes to user management. Countly’s detailed user management capabilities is a very good fit for every enterprise, and we are always adding new ways of authentication as our customers request.</p><p>As usual, your data, your rules.</p><p>— Arturs Sosins</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b5245cb3555d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Exporting data from Countly through DB Viewer]]></title>
            <link>https://medium.com/@countly_dev/exporting-data-from-countly-through-db-viewer-d3d73b06cd48?source=rss-a4fbe317bf21------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3d73b06cd48</guid>
            <category><![CDATA[export-data]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[countly]]></category>
            <category><![CDATA[mongodb]]></category>
            <dc:creator><![CDATA[Countly Engineering Team]]></dc:creator>
            <pubDate>Mon, 22 Aug 2016 16:25:42 GMT</pubDate>
            <atom:updated>2023-05-17T08:47:10.582Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PbSprtrxf0oOm1eijf65Wg.jpeg" /></figure><h3>Exporting data from Countly through DB Viewer</h3><p>DB Viewer is a plugin that provides a UI to browse databases. But it is also a great option to access Database data through REST API, for example, to export data. In this article, we will explain how to navigate the data scheme and find all the needed information to export events and their granular data from Countly.</p><p>Let’s say you have some other database, and you want to populate it with data from Countly. Or you just want to prepare some kind of report through a third-party application. Or write some scripts for getting data out and processing it. These examples should help you in all those cases.</p><h3>1. Getting information about all apps</h3><p>This is a standard API call available in the core and will provide you with info about apps that exist and are accessible for users with provided api_key.</p><p>It is useful for getting a list of app_ids if you are writing a script to iterate through all apps, for example.</p><p>Example call (replacing domain.com and {api_key} for user)</p><p><a href="https://domain.com/o/apps/all?api_key={api_key}"><strong>https://domain.com/o/apps/all?api_key={api_key}</strong></a></p><p>More info about the API call: <a href="https://api.count.ly/reference#oappsall">https://api.count.ly/reference#oappsall</a></p><h3>2. Getting user information about a specific app</h3><p>This API call involves DB Viewer API and will list all documents of all users and their properties that are available for this specific app.</p><p>Example (replacing domain.com and {app_id} for the app you want to get info and {api_key} for user):</p><p><strong>http://domain.com/o/db?dbs=countly&amp;collection=app_users{app_id}&amp;limit=1000000000000&amp;api_key={api_key}</strong></p><p>In the response object, the collections array should have all the user objects with their properties.</p><p>If there are too many users to read in a single request, you can paginate results by using limit and skip parameters. As example:</p><p><strong>http://domain.com/o/db?dbs=countly&amp;collection=app_users{app_id}&amp;limit=100&amp;skip=200&amp;api_key={api_key}</strong></p><p>More information on pagination and filtering: <a href="https://api.count.ly/reference#odbdbsdbcollectioncollection">https://api.count.ly/reference#odbdbsdbcollectioncollection</a></p><p>More information on possible user properties that you might get: <a href="https://support.count.ly/hc/en-us/articles/360037681532-countly-app-users-appID-">https://support.count.ly/hc/en-us/articles/360037681532-countly-app-users-appID-</a></p><p>If you want to monitor only new users, then you can adjust the filter part like this.</p><p><strong>http://domain.com/o/db?dbs=countly&amp;collection=app_users{app_id}&amp;limit=1000000000000&amp;query={&quot;fs&quot;:{&quot;$gt&quot;:1470009600}}&amp;api_key={api_key}</strong></p><p>Replacing 1470009600 with a timestamp of the last data sync. Of course you can do other filtering options or perform any kind of MongoDB query using the filter clause.</p><h3>3. Getting all event data</h3><p>Getting all events data would consist of 2 steps. Basically, what you need to do, is to get all event keys for a specific app, iterate through those event keys and create sha1 hashes, to be able to request data for each event specifically through DB Viewer API.</p><h3>First step.</h3><p>The first step would be getting the list of all event keys that are available for provided app.</p><p>Example call (replacing domain.com and {app_id} for the app you want to get info and {api_key} for user)</p><p><a href="http://domain.com/o?api_key={api_key}&amp;app_id={app_id}&amp;method=get_events"><strong>http://domain.com/o?api_key={api_key}&amp;app_id={app_id}&amp;method=get_events</strong></a></p><p>More information on this API call: <a href="https://api.count.ly/reference#omethodget_events">https://api.count.ly/reference#omethodget_events</a></p><p>There is a property named “list” on the response object, which is an array of all event keys.</p><p>So you got all the event keys that you had used in custom events in your app using Countly SDK.</p><p>Additionally there are some “built-in Countly events” that are stored as events but are internal events, as:</p><ul><li>[CLY]_session to get session data</li><li>[CLY]_crash to get crash data</li><li>[CLY]_push_open to get push opened data</li><li>[CLY]_push_action to get push action data</li><li>[CLY]_view to get view data</li></ul><p>If you need any information on that data from Drill, then include them in your script’s even key array (basically adding them to the array of event keys you retrieved from the API).</p><h3>Second step.</h3><p>So now we need to create sha1 hashes for each event and use them in REST API calls to get information about specific events.</p><p>Hash is formed using the sha1 hash for the event key together with app ID.</p><p>So, for example, for the event with key “Buy” and for app ID “<strong>542e95d747f0be510c000004</strong>” the hash would be <strong>sha1(“Buy542e95d747f0be510c000004”)</strong> and could look like: <strong>“57c2b7d4eeae912495088c3754d0c6cfe9949f06”</strong></p><p>And here is the request to get data about a specific event (replacing domain.com and {hash} for the event hash you want to get info and {api_key} for the user)</p><p><strong>http://domain.com/o/db?dbs=countly_drill&amp;collection=drill_events{hash}&amp;limit=1000000000000&amp;api_key={api_key}</strong></p><p>Again, if there are too many events for a single request, you can paginate using limit and skip parameters as discussed when getting users. Because it is the same DB Viewer API call with same parameters only for another collection.</p><p>And you can then recreate the event timeline using <strong>ts</strong> property, which is the timestamp when the event occurred.</p><p>Another example is if you want to monitor only the latest data, then you can adjust the filter with a timestamp in milliseconds like this (replacing 1470009600000 with a timestamp in milliseconds of the last data sync)</p><p><strong>http://domain.com/o/db?dbs=countly_drill&amp;collection=drill_events{hash}&amp;limit=1000000000000&amp;query={&quot;ts&quot;:{&quot;$gt&quot;:1470009600000}}&amp;api_key={api_key}</strong></p><p>Similar way again, you can modify the filter parameter to perform any kind of MongoDB queries through filter parameter to filter out event data.</p><p>And you can get more info about possible data and properties that you can retrieve using this request here:</p><p><a href="https://support.count.ly/hc/en-us/articles/360038263211-countly-drill-drill-events-ID-">https://support.count.ly/hc/en-us/articles/360038263211-countly-drill-drill-events-ID-</a></p><h3>Conclusion</h3><p>There are many different ways to export data from Countly. For example, we provide some <a href="https://github.com/Countly/countly-server/tree/master/bin/scripts/export-data">exporting and data-syncing scripts</a> that you can use for your data export needs. But if you just want to export a small amount of data or understand how data looks like or is liked, DB Viewer and its REST API are exactly what you need.</p><p>Let us know if you have any suggestions or examples/use cases for DB Viewer on our community discord: <a href="https://discord.gg/countly">https://discord.gg/countly</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3d73b06cd48" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Have you ever had any problems integrating Countly SDK?]]></title>
            <link>https://medium.com/@countly_dev/have-you-ever-had-any-problem-integrating-countly-sdk-ab44517311eb?source=rss-a4fbe317bf21------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab44517311eb</guid>
            <category><![CDATA[tutorial]]></category>
            <category><![CDATA[countly]]></category>
            <category><![CDATA[integration]]></category>
            <dc:creator><![CDATA[Countly Engineering Team]]></dc:creator>
            <pubDate>Mon, 02 May 2016 19:07:34 GMT</pubDate>
            <atom:updated>2016-05-02T19:11:00.298Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GubfbX5rB8Fnih1dcZmAOQ.jpeg" /></figure><p>We try to have good documentation. We really do. We provide as thorough information as we can on our <a href="http://resources.count.ly/">resources page</a> for our SDKs.</p><p>But having over 10 SDKs (including official and community managed) each with its own platform specific feature set (we even have <a href="http://resources.count.ly/docs/sdk-development-guide">SDK development guide</a> about how to implement our SDKs to make them more similar, but still there are differences), errors may happen.</p><p>Sometimes information gets outdated, sometimes missed and sometimes users are in hurry to implement our SDK, that they don’t read the full instruction set. Whatever the reason is, we always feel that we could have done more.</p><p>Basically we would like to provide each and every one of you, with personalized help in implementing our SDKs in your app, website, etc with your specific app ids/packages/other settings and with the feature set that you specifically require.</p><p>And now it is possible with <a href="http://code.count.ly/">Countly Code Generator</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y1VJD3F0ZgfneFebgOPpXg.png" /></figure><p>It will help you by generating step by step personalized tutorials and code snippets to use based on your provided settings and selected features.</p><p>You just select what you want to achieve and follow the wizard to provide information and accomplish your goals with ready to use snippets</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g54dE53QKH3VdzL2WWTJbQ.png" /></figure><p>We even integrated it in our dashboard to help you from the start when you create app in Countly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0Aim7h04mO1FOuhnI0Epiw.png" /></figure><p>For now we just support some of our SDKs and provide help with SDK integration, creating custom events and submitting information about user. But we want to extend and improve it even more.</p><p>So if you spotted an error or have a suggestion, please drop us a line at <a href="/service/mailto:engineering@count.ly">engineering@count.ly</a></p><p>We would like to hear what you have to say.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*LTnSZsLpHl_cBrWyYfSHqg.png" /></figure><p><em>Arturs Sosins is one of the lead engineers at </em><a href="https://count.ly/"><em>Countly</em></a><em>, who’s main goal is making Countly as robust and extendable as possible. In the spare time, when not spending time with his big family, Arturs enjoys game development, game design and music related projects.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab44517311eb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Improvements in App Management]]></title>
            <link>https://medium.com/@countly_dev/improvements-in-app-management-7c1c44319e22?source=rss-a4fbe317bf21------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c1c44319e22</guid>
            <category><![CDATA[countly]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Countly Engineering Team]]></dc:creator>
            <pubDate>Fri, 15 Apr 2016 12:47:05 GMT</pubDate>
            <atom:updated>2016-04-15T12:48:25.881Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mkr4m1YVTPDI4QfpUsyn_g.png" /></figure><p>Similarly to User Management section, we also listened to our users and problems they are having and improved interface a bit to solve those problems in our App Management section.</p><p>Firstly, the purpose of some fields was not completely clear, so we removed fields like category and added small one line tips to other fields that were confusing to our users.</p><p>Secondly, there were problems with some users confusing App ID and App Key and using ID instead of the key in their SDKs, which of course did not work. Thus we decided to move App ID to a much lower section, so the first thing users will see would be App Key, which is most commonly used in SDKs (App ID can only be used in read API requests, if you want to integrate Countly with your own systems).</p><p>And thirdly, some users where moving or starting over or for some other purpose, wanted to change the App Key of the app, to what they already had in SDK for example. Previously it was only possible to do right in the database directly, now we also provide App Key as editable field in App Management itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1EoEJm6eewaKvuaMa84WtQ.png" /></figure><p>If you think we can do better, let us know by dropping us a line at <a href="/service/mailto:engineering@count.ly">engineering@count.ly</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*LTnSZsLpHl_cBrWyYfSHqg.png" /></figure><p><em>Arturs Sosins is one of the lead engineers at </em><a href="https://count.ly/"><em>Countly</em></a><em>, who’s main goal is making Countly as robust and extendable as possible. In the spare time, when not spending time with his big family, Arturs enjoys game development, game design and music related projects.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c1c44319e22" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Improvements in User Management]]></title>
            <link>https://medium.com/@countly_dev/improvements-in-user-management-a3f6df93a45d?source=rss-a4fbe317bf21------2</link>
            <guid isPermaLink="false">https://medium.com/p/a3f6df93a45d</guid>
            <category><![CDATA[countly]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[datatables]]></category>
            <dc:creator><![CDATA[Countly Engineering Team]]></dc:creator>
            <pubDate>Mon, 04 Apr 2016 10:10:02 GMT</pubDate>
            <atom:updated>2016-04-04T11:34:18.730Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hNy_5_yJYB9_ELt-JaEPww.jpeg" /></figure><p>Quite some versions ago we moved almost all our data tables to, well, D<a href="https://www.datatables.net/">ataTables</a> :)</p><p>I say almost, because there was one particular part that was quite large, with lots of functionalities, and expanding rows, etc, that we decided to leave as is for now — User Management (not to confuse with User Profiles, user management allows to give access to Countly dashboard to different users with different access privileges).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4BM4kw2dXbqVU14hbMJGQw.jpeg" /></figure><p>But we started to have more and more requests to improve it, because when amount of users becomes quite large, this user management, becomes “unmanageable”.</p><p>So finally in our <a href="https://github.com/Countly/countly-server/commit/82ce7368044c27133fa904dc12882a0395378e16">latest development code</a>, we moved that part to DataTables too, which automatically brings everything our clients wanted:</p><ul><li>Pagination to deal with long user lists</li><li>Filtering to find specific user</li><li>Exporting data in CSV and Excel</li><li>And sorting by any column you want</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2o4nfRPBtcxziT8d8-HiWQ.png" /></figure><p>And all of this, by simply moving to specific library (with some plugins), I’d say it is pretty neat :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*LTnSZsLpHl_cBrWyYfSHqg.png" /></figure><p><em>Arturs Sosins is one of the lead engineers at </em><a href="https://count.ly/"><em>Countly</em></a><em>, who’s main goal is making Countly as robust and extendable as possible. In the spare time, when not spending time with his big family, Arturs enjoys game development, game design and music related projects.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a3f6df93a45d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DBViewer plugin to view and export your data]]></title>
            <link>https://medium.com/@countly_dev/dbviewer-plugin-to-view-and-export-your-data-8fcae07a8fa9?source=rss-a4fbe317bf21------2</link>
            <guid isPermaLink="false">https://medium.com/p/8fcae07a8fa9</guid>
            <category><![CDATA[countly]]></category>
            <category><![CDATA[countly-plugin]]></category>
            <category><![CDATA[new-features]]></category>
            <dc:creator><![CDATA[Countly Engineering Team]]></dc:creator>
            <pubDate>Tue, 29 Mar 2016 10:41:55 GMT</pubDate>
            <atom:updated>2020-02-13T07:57:11.062Z</atom:updated>
            <content:encoded><![CDATA[<h4>Couple of versions ago we added a DBViewer plugin for our own needs, to easily view the state of database during feature development and also when providing support to clients. This blog post explains how to view and export your data from Countly easily.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CXFxXhYV2nzUvLy6FKmT3g.png" /></figure><p>In the last version we also added deobfuscation of the database collection names, so our users and contributors would get familiar with underlying database structure more easily. But, as it turns out, some users are going even further and use DB Viewer plugin to export data from Countly.</p><p>You see, as with any other Countly dashboard functionality, it is built upon REST API provided by the backend server. So while building dashboard UI for our database browsing, we also “accidentally” on purpose, built a great way to browse our databases through REST API and retrieve needed data, to, for example, export data for events.</p><p>Also pagination options (limit and skip) and option to query specific data (filter) only compliment this ability.</p><p>To be able to do that, you actually need only 2 endpoints:</p><ul><li><a href="https://api.count.ly/reference#odb">To get all databases and their collections</a></li><li><a href="https://api.count.ly/reference#odbdbsdbcollectioncollection">To get documents from specific database and collection</a></li></ul><p><strong><em>To be able to browse the database, you need Global Admin permission and thus api_key with that permission.</em></strong></p><p>The returned data will be in JSON and it will be the raw data retrieved from the database, so if you want to understand what does that data mean checkout our <a href="https://support.count.ly/hc/en-us/sections/360007310592-Database-Schema">Database Schema section</a> or drop us a line for more information at <a href="/service/mailto:engineering@count.ly">engineering@count.ly</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*LTnSZsLpHl_cBrWyYfSHqg.png" /></figure><p><em>Arturs Sosins is one of the lead engineers at </em><a href="https://count.ly/"><em>Countly</em></a><em>, who’s main goal is making Countly as robust and extendable as possible. In the spare time, when not spending time with his big family, Arturs enjoys game development, game design and music related projects.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8fcae07a8fa9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[New Countly Side Menu]]></title>
            <link>https://medium.com/@countly_dev/new-countly-side-menu-87ccfdac24a?source=rss-a4fbe317bf21------2</link>
            <guid isPermaLink="false">https://medium.com/p/87ccfdac24a</guid>
            <category><![CDATA[countly]]></category>
            <category><![CDATA[new-features]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Countly Engineering Team]]></dc:creator>
            <pubDate>Mon, 28 Mar 2016 09:15:13 GMT</pubDate>
            <atom:updated>2016-03-28T09:20:32.459Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/392/1*JKhSvBe6iwL3GHy8TA6s_Q.png" /></figure><p>This is a preview of new Side Bar Menu, which will be available in next Countly release. While a picture can tell you more than thousand words, animated picture can do even more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*fXnbxTpglAL1xYAZRRuXwg.gif" /></figure><p>And let me just elaborate a little on why such change.</p><p>Basically the reason is that we have been growing in quantity of new features/additions/plugins each of them taking up a space on the menu. And on small screens there was already a need to scroll the main menu, but once you expand it vertically, it just become too much scrolling work to find the right menu item.</p><p>So we wanted to make the menu more compact and less scrolling. And achieve all that with same amount of clicks when switching from one submenu item to other, so our menu would not lose it’s efficiency.</p><p>And this solution fits all of the mentioned criterias perfectly, and sub menu sliding on hover makes it easy to check out main menu items and switch between them and sub menu items. You will like it when you try it :)</p><p>Have any more suggestions on UI improvements? We are all ears, drop us a line at <a href="/service/mailto:engineering@count.ly">engineering@count.ly</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*LTnSZsLpHl_cBrWyYfSHqg.png" /></figure><p><em>Arturs Sosins is one of the lead engineers at </em><a href="https://count.ly/"><em>Countly</em></a><em>, who’s main goal is making Countly as robust and extendable as possible. In the spare time, when not spending time with his big family, Arturs enjoys game development, game design and music related projects.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87ccfdac24a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Knowing who your users are]]></title>
            <link>https://medium.com/@countly_dev/knowing-who-your-users-are-efea72a3996c?source=rss-a4fbe317bf21------2</link>
            <guid isPermaLink="false">https://medium.com/p/efea72a3996c</guid>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[countly]]></category>
            <category><![CDATA[new-features]]></category>
            <dc:creator><![CDATA[Countly Engineering Team]]></dc:creator>
            <pubDate>Fri, 25 Mar 2016 08:33:39 GMT</pubDate>
            <atom:updated>2016-03-25T10:21:27.288Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CswwFSjBq_aEiWt5lsT88Q.jpeg" /></figure><p>In the beginning Countly tried to answer what your users do in your app. With the first version of <a href="https://count.ly/user-profiles/">User Profiles</a> plugin we tried to answer who your users are by allowing you to collect some specific information about your users, including any custom properties that you want to attach to your users.</p><p>With the latest <a href="http://blog.count.ly/post/139967525793/countlys-the-most-complete-release-ever-1602">16.02 release</a>, we also added functionality to segment your users</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WKklQuUjSKD5Gs8GMdfZ-g.png" /></figure><p>Countly users who are used to <a href="https://count.ly/segmentation/">Drill</a> interface, will recognize the querying mechanism here. But the biggest difference between Drill and User segmenting is the fact, that Drill queries historical data, what properties user had at that specific time of the action, while user segmenting queries users by their current properties.</p><p>So if you want to know how many users made a purchase on second session, you go to drill, but if you want to know users who have total purchase amount over some specific threshold, you segment your users.</p><p>But it actually does more than that. If you notice every time you create a query, it updates URL’s hash to generated query.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/677/1*bNfQPfwE4xHpA_dDPBh8Vg.png" /></figure><p>Such interface of getting query through hash allowed us to provide external links to query specific user properties. And that is why you will see these kind of “View User List” buttons through out the Countly interface.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*acnuKdUmDVWcCl8Zavb_uQ.png" /></figure><p>That would allow you to see the list of specific users behind those mysterious and anonymous numbers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cbwdEiTFEOh-jxGunxQBTQ.png" /></figure><p>That provides lots of benefits, like being able to contact the user who has specific crash, get list of users who stopped and specific step in funnel and encourage them with a motivational push notification, get the users who came to you through specific source or campaign and provide a promotion specifically for them.</p><p>But that’s just a start. Being afraid of over cluttering the User Interface, we are not putting a face on each number there is on the dashboard (although probably it would be possible), instead we are listening to your (Countly user) suggestions and trying to evolve this feature, step by step.</p><p>So have any interesting ideas or a use cases for this new feature? Drop us a line at <a href="/service/mailto:engineering@count.ly">engineering@count.ly</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*LTnSZsLpHl_cBrWyYfSHqg.png" /></figure><p><em>Arturs Sosins is one of the lead engineers at </em><a href="https://count.ly/"><em>Countly</em></a><em>, who’s main goal is making Countly as robust and extendable as possible. In the spare time, when not spending time with his big family, Arturs enjoys game development, game design and music related projects.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=efea72a3996c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The need for command line tool]]></title>
            <link>https://medium.com/@countly_dev/the-need-for-command-line-tool-b7808b29ee04?source=rss-a4fbe317bf21------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7808b29ee04</guid>
            <category><![CDATA[countly]]></category>
            <category><![CDATA[tools]]></category>
            <category><![CDATA[command-line]]></category>
            <dc:creator><![CDATA[Countly Engineering Team]]></dc:creator>
            <pubDate>Thu, 24 Mar 2016 13:10:40 GMT</pubDate>
            <atom:updated>2016-03-25T10:20:50.090Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*yPG2b29RZLHREgWl9LVjZA.jpeg" /></figure><p>Initially we were using upstart to manage Countly daemon process, and since Ubuntu was our main platform, it was quite enough.</p><p>But since Countly is an open system, other users wanted to port it to other platforms too, including CentOS, Fedora and even OSX. But that would mean to change lots of internals and modify the core, so it either works on one system or the other.</p><p>So we kept such modifications as tutorials to be able to run Countly on different operating systems, but when Countly was updated it meant to apply those changes once again.</p><p>And then one day, Ubuntu released new version, where it used systemd instead of upstarts, completely putting us into dead end.</p><p>We faced a decision either to update to systemd and drop support for upstart, or try to create something more robust, that would cover both problems.</p><p>Of course we went the latter way.</p><p>So we created a command line tool with stub methods to control Countly process and fill them in during installation based on <a href="https://github.com/Countly/countly-server/blob/master/bin/scripts/detect.init.sh">init system detection script</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/433/1*h8Q7iSjNZbSBH67zOPNhOw.png" /></figure><p>And now everyone can add platforms they want, by adding Countly script, that will overwrite stubs and manage Countly process. All that needs to be done is to create a folder with your platform/init system in bin/commands and put all needed files there and symlink countly.sh script overriding countly functions into enabled folder (or update <a href="https://github.com/Countly/countly-server/blob/master/bin/scripts/detect.init.sh">init system detection script</a>, to detect your system too).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/684/1*woQ4mjtXhMU5ty47jEMunA.png" /></figure><p>But eventually it become more than a way to deal with different systems. Countly developers saw the potential of such tool, allowing it to do more.</p><p>Now Countly support team, while providing support to client, can provide precise commands to execute, rather than specifying vague point and click instructions.</p><p>Any Countly developer can connect to server and easily identify Countly version and where Countly is installed, as well as change configuration and enable/disable plugins, without requiring the access to dashboard.</p><p>Countly server admins can create automatic backups using Countly command line and upgrade components periodically, as translations, geolocation database, device mode list, etc.</p><p>If you are interested on more what you can achieve using Countly command line tool, visit our <a href="http://resources.count.ly/docs/countly-command-line">documentation page</a>.</p><p>If you have any great ideas what we could also add to our command line tool, let us know. Drop us a line at <a href="/service/mailto:engineering@count.ly">engineering@count.ly</a> :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*LTnSZsLpHl_cBrWyYfSHqg.png" /></figure><p><em>Arturs Sosins is one of the lead engineers at </em><a href="https://count.ly/"><em>Countly</em></a><em>, who’s main goal is making Countly as robust and extendable as possible. In the spare time, when not spending time with his big family, Arturs enjoys game development, game design and music related projects.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7808b29ee04" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>