#tonin_docs

1 messages · Page 1 of 1 (latest)

shy apexBOT
#

👋 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/1438335775409180824

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

north rover
#

Hmm could you screenshot where do you see that Dimensions parameter?

merry gulch
#

Or maybe Dimensions isn't the key to my problem :/ At the end of the day, I want to know if usage can be attributed to the corresponding subscription (maybe through subscription id) when customers have multiple instances of the same subscription that share the same meter. Right now the behavior is unexpected--one usage event will add usage to all the subscriptions that share the same meter.

The Stripe AI suggested "Dimensions" so I was looking into it.

north rover
#

I see. Agree dimentions here is not what you are looking for

#

In your case, how about using different Meters?

merry gulch
#

we can have customers with many subscriptions. as we scale we can potentially have hundreds of these subscriptions. Don't know if having a meter for each is the way to go about this

#

ideally I want to just have one meter to keep everything clean.

north rover
#

Yes but you dan have a few dozen of meter, each for multiple Sub as well. The definition of Meter is that its Meter event will be shared

#

It’s about design the granularity

merry gulch
#

I'm not sure I understand what you mean by each meter for multiple subscription. I know that meter works across customer. But in our case, the same customers have multiple of the same subscription. We only offer one type of subscription which is a monthly subscription of fix price + overage (which I use the meter for). Each customer can have multiple subscriptions. Subscriptions can be added, cancelled or paused anytime. To me, it seems that I need to create a meter dynamically each time a customer get a new subscription, to avoid the issue.

#

For context, we do tutoring business. A customer (parent) can have multiple of the same monthly subscriptions (such as for different students, subjects). The subscription product is the same as we use the same price.

#

A customer (parent or school) can potentially have 100+ subscriptions with us in the lifetime (different students, subjects, tutor etc).

#

Sorry if this is too complex. If it's not the intended use case for meters, I'll look into something else. But thank you for all your help!

north rover
#

Hmm no worries.