#rellfy_api
shadow questBOT
👋 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/1292758476262735905
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
smoky onyx
To clarify: I have 1 meter, and 1 customer with 2 subscriptions.
These subscriptions each have a price that points to the same underlying meter.
I update 1 subscription's meter, and that results in the other subscription's usage also increasing.
Do I need 1 meter per price in this scenario?
spring hawk
hi! yes you need two meters for this
smoky onyx
Ok, thanks for the quick reply!
Should it be 1 meter per price per customer, or is just 1 meter per price enough?
spring hawk
I'm not sure to be honest, let me ask someone else.
smoky onyx
I would guess just per price since the event update request contains the stripe_customer_id, but not too sure 😁
Instead of "per price" here I should say "per product" instead, I think I got that part confused a bit
spring hawk
well, when you create an Meter Event, you have to specify the Meter name and also the means to map to a Customer ID, so that kind of covers how the attribution works. Depends how you want this to work overall