Integrate Fullstory with Atlassian
Fullstory helps companies record and analyze their customer communications by recording user sessions, providing detailed step-by-step logs of everything customers did during their sessions and storing that information for later retrieval and analysis. Fullstory can then be searched for specific events, including link usage, rage clicks or dead clicks. In addition to data on individual sessions, Fullstory can also retrieve analytics on aggregate customer behavior, showing the most clicked items, the most rage clicked areas, the most navigated to sites, etc.
Millions of users globally rely on Atlassian products every day for improving software development, project management, collaboration, and code quality. Atlassian products include: JIRA Software, JIRA Service Desk, JIRA Core, StatusPage, Confluence, HipChat, Bitbucket, SourceTree, Bamboo, Cover, FishEye, Crucible.
Popular Use Cases
Bring all your Fullstory data to Amazon Redshift
Load your Fullstory data to Google BigQuery
ETL all your Fullstory data to Snowflake
Move your Fullstory 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 Fullstory With Atlassian Today
Free 7-day trial. Easy setup. Cancel any time.
Fullstory's End Points
Provide a user ID and/or email address to get a list of every session associated with a specific user up to the defined limit. Entries in that list include the user ID and email address, the time the session occurred, and the Fullstory session URL, all of which can be used to access the data from that session if desired.
Retrieve a list of 20 available data bundles from a specific timestamp onward. Then, export the most valuable data bundles from that list so that they can be integrated with other relevant data sources to give you a deeper overall view of your customer’s experience.
Atlassian's End Points
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.
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.
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.
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.