Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Include Page
Header
Header

Topics

Table of Contents
minLevel1
maxLevel6
include
outlinefalse
indent
style

...

default
excludeTopics
typelist
class
printabletrue

...

Overview

If you are developing for Atlassian Marketplace it has a very good Vendor Management portal with an Open API to pull data from. This portal might be a better source of data for your Accounts in journy.io as opposed to your CRM or journy.io might be a way for you to get proper CRM as a result of an integration.

...

Select More > Import Blueprint

...

Import the Blueprint Attached.

...

Your Atlassian vendor data

...

What?

Why?

How?

Technical, Billing and Reseller Contacts

You might want to propagate it to your CRM via journy.io as journy has very good integration with most popular CRMs and might power your switch from one CRM to another one

Two options:

  1. Either additional properties to account - aka Name and email for each of 3x contacts

  2. Make them Users in journy.io, but suggestion to setup some Role property to differentiate Technical, Billing. Reseller Contacts from future App Users.

    1. amend make.com script above add Segment Identify() call for each contact

    2. following by Segment Group() call to connect user to account.

image-20240610-113219.png

Transactions History

You might want to see all the purchases for clients as events - New, Upgrades, Renewals, Refunds

image-20240610-134222.png
Info

We might update this section if we here feedback from you to make step-by-step guides for the 2 above.

...

What?

Why?

How?

Segments

If you do Atlassian Marketplace business you might want to focus on high paying clients/licences and remove the noise of Free Subscriptions you have for volume.

Therefore, we suggest create Segments in journy.io to use through the App functionality.

Segments

We suggest to create Segments by Tier/LicenceType (that’s the reason we do all the magic with Tier and Opportunity size in make.com script).

Or you can do it by MRR - either estimated via Calculated Property of Tier x AVG Price-per-Tier, or proper MRR you calculate from transactions (see above)

In-App Analytics

Probably the biggest value you can gain from bringing in-App analytics to journy.io (basically how people use your Apps).

If you use MixPanel or Amplitude you should be right at home - we would suggest to change integration to Segment and from Segment put it to MixPanel or Amplitude plus also journy.io.

Connecting your SaaS platform, website and customer apps

Suggestion to make it per Account (meaning all events from individual App users aggregated at account level).

For this use Entitlement Number as Anonymous ID for your Track() call.

If the future you can split per user but also aggregated per account by specifying proper Atlassian User ID for Track() call.

https://releasemanagement.atlassian.net/wiki/spaces/journy/pages/2697068976/The+Track+Spec#Tracking-events-on-user-AND-accounts!

Scores and Health Profiles

Once you bring in-App analytics to can aggregate it into Scores and Health Profiles to drive your further engagements and decisions

Setting up Signals and Scores

Custom Scores

Health Profiles

From Smart Signals to Conversion, Churn & Health Scores

Playbooks

Once you have Scores and Health Profiles defined you can now automate Playbooks for your key Segments and engage with them - automatically or manually

Setting up Playbooks

Playbooks

Inbox

Intercom in your App

If you do Atlassian Marketplace business you probably know that there’s not much value talking to Technical, Billing and Reseller Contacts - you need to talk to real App users

The Intercom Connector

This is where journy.io will become supper powerful, namely:

  • Bring individual users in (you might not event identify them, Atlassian User ID will be enough)

  • Separate in-app Analytics per-user (just specify userID) while keeping it integrated per Account

  • Leverage Intercom integration in journy.io and your App to create engagement channel with your key users.

Proper CRM / change CRM

You can use journy.io as your CRM, but if you want more sophisticated (tier 1) solution you can leverage the fact that journy.io is a middle layer between your Apps and Tier 1 CRM + list of our Tier 1 CRM integrations. Thus you can use journy.io to power up switch from one to another.

Connectors

Optimize toolset / costs

If your solution is stable and you are more in business as usual mode there are couple of areas to optimize

  • Make.com

  • Segment

Make.com - you might get your engineering team to develop appropriate scripts and run them on cadance on your own servers/internet optimizing the cost of no-code platform.

We are also considering to bring it in-house to develop Connecter for Atlassian Marketplace and other popular Marketplaces.

Segment - super powerful and supper flexible solutions that gives you options to change tools/platforms in the future via configuration. But if you are committed to journy.io here’s our API/SDK to remove Segment on the way

The API/SDK Connector

Tip: Need help with your Connectors?

Reach out to our support team

...

or book time to make it together

...

Include Page
Footer
Footer