Pre-defined TemplateWe made your life easier with pre-defined templates that will extract all data from to any destination.

Popular Use Cases

Bring all your Appsee data to Amazon Redshift

Load your Appsee data to Google BigQuery

ETL all your Appsee data to Snowflake

Move your Appsee data to MySQL

Bring all your Atlassian data to Amazon Redshift

Load your Atlassian data to Google BigQuery

ETL all your Atlassian data to Snowflake

Move your Atlassian data to MySQL

Integrate Appsee With Atlassian Today

Free 7-day trial. Easy setup. Cancel any time.

Appsee's End Points

Events

Track a variety of data related to events that happened during user sessions, such as the number of total events in a given period, the properties associated with those events and the number of occurrences of a specific property. This endpoint can also be used to signal when an event occurrence might warrant further examination of the video recording to see when and why it occurred.

Screens

Monitor how users interact with your screens, including how many times a screen was accessed, what types of gestures were used, and what screen was accessed next. This can give you a broader view of how your users interact with your app. Use this information to gauge the effectiveness of your screen designs and know which features are being used more or less frequently.

Analytics

Get analytics data for your app, including the number of users that accessed it and the number of sessions that occurred. This data can be filtered by a set of parameters, including country, date, OS, device, and session duration.

Sessions

Request data about a user’s session, which can be filtered by things like user ID, included events, device type and screen. Appsee will return any pertinent data and include information like the video URL, crashes that occurred and any other events that occurred during the session.

Funnels

Retrieve data about your conversion funnels and sort it by parameters, including date range, app version, device and platform. Then, Appsee will return a list of steps in the funnel, along with how many users accessed that step and what their completion percentage was.

Atlassian's End Points

Info

Request information about your service desk instance, including its version number, how long the instance has been running and what build it is. Accessing this data will, among other things, allow you to more successfully integrate your service desk with other relevant data sources.

Customers

Create a customer entity in JIRA Service Desk by providing Atlassian with the customer’s name, email and display name. Then, use this data in other endpoints to track service requests for a specific customer or integrate it with customer service data from other sources to provide a more comprehensive view of a customer’s journey.

Organizations

Retrieve data on organizations that are engaging with your service desk, including the organizations’ names, IDs, properties and associated users. Then, access this endpoint to track those organizations, their users and their service requests so that you can have a better understanding of your service interactions with them.

Requests

Track any and all customer service requests and get relevant data, such as the customer’s contact info, the reason for the request, and the status of the request (what step it is on in your customer service process). Use this data to evaluate how well your company is responding to these requests and/or monitor customer service trends.