#giorgio-nocera-nabla_best-practices

1 messages ¡ Page 1 of 1 (latest)

wooden ridgeBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1478788035276570644

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

bitter goblet
#

Hello, so the main difference is whether you separate the credits into one product or three?

sterile oxide
#

Thank you for the speed!!
Yeah, we are thinking about those two differences:

Option A:

  • Product: Essential Plan (with license, with prices: monthly, yearly)
  • Product: Professional Plan (with license, with prices: monthly, yearly)
  • Product: Elite Plan (with license, with prices: monthly, yearly)
  • Product: Credits (pay-as-you-go, with prices: essential-monthly, essential-annual, professional-monthly, professional-annual, elite-monthly, elite-annual)

Option B:

  • Product: Essential Plan (with license, with prices: monthly, annual)
  • Product: Essential Credits (pay-as-you-go, with prices: monthly, annual)
  • Product: Professional Plan (with license, with prices: monthly, yearly)
  • Product: Professional Credits (pay-as-you-go, with prices: monthly, yearly)
  • Product: Elite Plan (with license, with prices: monthly, yearly)
  • Product: Elite Credits (pay-as-you-go, with prices: monthly, yearly)

We started with only 3 different product (one per plan) including also the credits as different price, but this causes very bad UX, as you can see from the image.

image.png
bitter goblet
#

In general, we reccommend separate products for each distinct that you sell, so even a red vs blue shirt would be two different products. So as a baseline: are these different credits actually different things, or is it kind of the same thing in different contexts? If these are the same credits, they're just paid for differently wtih different packages, that would lean more towards being one product.

#

My team also admittedly doesn't know much about reporting or analytics, but I will see if I can find quick info on that. Even if this is the same thing, it may make sense to separate it out if you want separate graphs, though I'm less sure on how that works.

sterile oxide
#

Thanks for the clarification!

The credits are the same thing - they represent the same unit of consumption (e.g., 1 API call = 1 credit) regardless of which plan you're on.

What changes based on the plan is:

  1. How many credits are included for free (Essential: 15, Professional: 50, Elite: 150)
  2. The price per extra credit consumed (Essential: $1.33, Professional: $1.00, Elite: $0.80)

So it's the same product (credits), just with different pricing based on the subscription tier - kind of like volume discounts, but tied to which plan you subscribe to.

Based on your guidance, this sounds like it should be 1 product with multiple prices (Option A)?

The only concern is analytics: can we still see "revenue from Essential credits" vs "revenue from Professional credits" separately if they're all under one product? Or would we only see total "credits revenue"?

bitter goblet
#

Gotcha, and I do see we mention something called "Dimensions" in this doc for basically this use case

(Optional) Under Advanced settings, specify the Dimensions that you want to tag your usage data with ... submit your usage data with dimensions that are populated for analytics and reporting.
Though from this doc it looks like that feature may be in private preview so you would have to request access.

#

Double checking if this is generally available yet or not.

#

Not generally available, so I'd say definitely request access in that doc if you are open to working with preview features. If not, you could do either one or multiple products to represent these. One product would mean worse analytics now but when that is available it should be pretty straightforward to add dimensions then. Or you could do multiple products now, and that would continue to work after dimensions are out, but you'd have to put specific effort into transitioning to one product if you do want to leverage that.

sterile oxide
#

Perfect! Thank you very much!

wooden ridgeBOT