Update on Addressing issues with Marketplace reporting and APIs: General Availability begins this week

Week 1 rollout status update:

Hi everyone! To keep you up to speed on the GA rollout of the new data pipeline, we’ll add a comment here each Monday outlining progress over the past week. Keep watching this post or page if you’d like to receive notifications about these weekly updates.

Last week, on October 13th, we successfully onboarded 3 Marketplace Partners onto the new data pipeline. Everything is working as expected so far with no disruptions.

Please watch the differences you may notice in the new pipeline for new updates.

Based on this feedback and feedback from our early access program (EAP), we will proceed with migrating the next cohort of 45 partners onto the new data pipeline tomorrow, on October 18, 2022.

@MalathiVangalapati are the preview APIs still available?

Hi @DinoStamatiou ,

Yes, the preview APIs are still available.More details here

Thanks @MalathiVangalapati we can see the Licenses…however we cannot see Transactions…is there a preview for Transasctions?

Hi @DinoStamatiou ,

The existing licenses and transactions end points will work when you replace reporting with reporting-preview. Below is the example of transaction API.

https://api.atlassian.com/marketplace/vendor/rest/2/vendors/{vendorID}/reporting-preview/sales/transactions

This is a huge problem for us. Please revert this. If you can’t tell - there is a large trust problem with Atlassian and partners. This does not help at all.

You’re basically saying that Atlassian can install the apps without Partners knowing about why there is an increased load, or why all of a sudden Atlassian mysteriously have managed to copy features into their core apps.

@amardesich @brlee Please help get this reverted.

55 Degrees will be track all SENs etc that use our apps and any that we are not able to sync up with the marketplace licensing database we usually end up escalating to Atlassian about. So all you’re doing is increasing marketplace support costs.

12 Likes

For some reason it seems like Atlassian still does not understand what Marketplace Partners are expecting from the Marketplace reporting APIs.

So here is another try to convey it:

  1. In the licenses endpoint, we want every license. Yes, this includes private listings, evaluation licenses, demonstration licenses, free licenses, internal Atlassian licenses. If a licenses is applied in the UPM, I want it in that report.

  2. In the transaction endpoint, we want every transaction. Yes, this includes free ($0), promotions (even 100% promotions, resulting in $0), demonstration licenses ($0), internal Atlassian licenses ($0), private listings ($0), free for all teams ($0). If there is a valid license, there should be a transaction to it. Every state change from trials/evaluations to paid should result in a transaction.

Why? Because ultimately, we want to decide if, how and when we want to use this information. It is not up to Atlassian to decide what information is or isn’t relevant to us. It is a simple ledger system and you should treat it that way.

The amount of effort it costs us to cross-check active license without transaction (and thus reason) in order for us to know why a customer has access to our apps is just crazy, especially considering that Atlassian has this information but is simply not sharing it with us.

17 Likes

Week 2 rollout status update:

Hi everyone,

Last week on 18 Oct 2022 , we onboarded 42 Marketplace partners to the new data pipeline ,ranging in data volumes through the pipeline from some of the largest to those who are on the smaller size so we do believe we have a reasonably representative sample in the roll out so far.

During this rollout, this group of partners reported three issues:

  1. evaluationOpportunitySize was showing the value “Unknown” for ~2% of the data in this field. This issue has been fixed.
  2. Partner type in transactions and licenses is showing as “Reseller“ in the new pipeline and “Unknown“ in the old pipeline for ~ 150 licenses and transactions. This issue will be fixed by 28 Oct 2022
    Please note that Reseller is not the same as “Corporate_reseller“. Reseller is an option Atlassian allows where anyone can place orders on our website and check a box to outline that they are not the actual end-user and are placing the order on their behalf. Once the order is placed, these “Reseller” orders are treated exactly the same as direct customer orders.
  3. In response to what we stated in the Differences you may notice in the new pipeline section (see below), some partners have expressed concerns and suggested we include all the internal Atlassian licenses. We are currently evaluating the options, will share an update on this shortly.

“In the current pipeline, a few Atlassian licenses were showing up as a result of a bug in reports which ideally should be excluded. In the new pipeline, we are excluding such internal Atlassian licenses. There is an ask from a few partners to excuse licenses of Bugcrowd (licenses created as part of Bug Bounty program), however we are still evaluating partners’ interest in this regard before we exclude this. “

Based on the feedback thus far, we will proceed with migrating the next cohort of 6 partners onto the new data pipeline today, on October 24, 2022.

All the remaining partners will be rolled out on 2 Nov 2022

Keep watching this post if you’d like to receive notifications about these weekly updates.

Please note: The next major billing and reporting milestone after the new data pipeline is support for app purchasing/paid cloud app customers on our new cloud billing engine. If you have not yet reviewed Marketplace Partners resources for the new billing engine (or the related API changes and UI changes), please do so as soon as you’re on the new data pipeline.

1 Like

Thanks for the feedback @danielwester @remie , we understand the importance of this data in running your business. We are reviewing this and will provide an update shortly.

@MalathiVangalapati I have noticed some weird caching issues. E.g. when I export transactions from marketplace reports I can get today’s transactions and up to date data. However, when this is done from the automation server which I use, it is serving yesterday’s data. This did not happen before. How exactly caching supposed to work here?

Hi @RaimisJ

I am assuming you are using an automation system at your end which uses the Marketplace APIs.
If you are getting today’s data from the Marketplace APIs, we do not see a reason why the same data would not flow to the automation server.
Happy to connect on a call if our understanding of the issue is different here.

RTBF Fields Improvement Update:

Context
As you all know we are masking the PII data in the reports as per GDPR (RTBF).
That being said, company name, country and region do not fall in the classification of PII data. So we will go ahead and remove the masking of these fields in the RTBF records. This will lead to a one-time increase in updates flowing to partners after the fix is implemented.

When
The team is working on the fix and the new unmasked fields should be available by the end of this week. We will update the thread for confirmation.

Thanks to the partners who raised the issue for this improvement.

1 Like

Hi @RituDagar

Yes, this server uses Marketplace APIs with API tokens. Investigating the issue, I did download the same data over marketplace reports and using API tokens and got two different sets. E.g tier field was specified differently - “tier”: “Per Unit Pricing (xxx Users)”, while the one one the marketplace reports lists “tier”: “xxx Users”. It was also getting delayed data. Could the API tokens be served a different data, or was migrated at a different time?

At the moment I can not reproduce this issue, will let you know if it happens again.

1 Like

Hi Everyone,
As many of you would already be aware that this week was Diwali (festival) week in India, wanted to update you all here that the fix has taken a bit longer. The team has been on it though and working through some edge cases.
We would keep the thread updated with the latest by early next week.
Thanks for understanding.

1 Like

Rollout status update:

Hi Everyone,

We went ahead with the GA for all partners today, Nov 2, 2022. Thanks to all the partners for sharing timely feedback to enable full rollout.

Last week’s update

We successfully onboarded 6 more partners on the new pipeline. We kept the number lean due to Diwali holiday week in India.

Some asks from partners post the rollout were

  • if we can remove RTBF masking from Company Name, Country and Region fields in the API. We have rolled out the change of unmasking of Company Name. Unmasking of Country and Region would be a fast follow-up. We will keep this thread updated on this change rollout date.
  • Some asks also came in for confirmation on lookback time for data pull post-migration to the new pipeline. Our recommendation is to get all updated data with lookback starting Sep 1, 2022, onwards.

Update on previous open threads

  1. Partner type in transactions and licenses is showing as “Reseller“ in the new pipeline and “Unknown“ in the old pipeline for ~ 150 licenses and transactions. This issue is fixed and rolled out on the new pipeline. Transactions will always have point-in-time partner information and licenses will have the latest information.
  2. Some partners have expressed concerns and suggested we include Atlassian licenses as well in reports. We have decided to give partners the option to pull Atlassian licenses if they want to and not give them by default as some partners do not want these licenses to skew their numbers. This would be a fast follow-up post the full pipeline GA including the new billing system records by the end of the month. We would keep our partner community posted on this change when implemented.

Thanks again to all partners for the engagement so far. Looking forward to continued collaboration on this.

@RituDagar @MalathiVangalapati can you please also give an update that responds to Update on Addressing issues with Marketplace reporting and APIs: General Availability begins this week - #21 by remie

Hi @remie

As called out in the last update, we would be giving the option to pull Atlassian test/internal licenses to partners as a follow-up as not all partners want this data by default.

For $0 transactions, we shared an update $0 transactions will be added to Marketplace APIs on June 9, 2022 back in June’22.

The other categories would be an iterative enhancement that we are targeting post the new billing system migration is done. We would keep the partners posted on all updates for these additions as and when we roll-out.

Weekly Update:

The unmasking of Country and Region for RTBFed contacts will also be rollout out Monday IST working hours.

The GA for all partners has been successful with no major issues reported. Thanks again to all of you for your tremendous support. :handshake:

We would keep this thread posted for more updates.

1 Like

Hi Team :wave:

Quick Update:

The unmasking of Country and Region for RTBFed contacts was rolled out on Monday and the details of the respective fields are now visible on the new pipeline.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.