#arvindsinghu
versed veldt
prime kraken
they use to get stored somewhere in the stripe but now they simply get redirected to the success page.
To clarify, are you saying that the redirect used to happen differently, or are you just saying that it used to get stored while they were redirected?
prime kraken
Does this doc section help? It looks like you may need to set specific fields to have them passed on like this https://stripe.com/docs/payments/payment-links#utm-codes
Oh and you are already using them
stray sail
i read that but not sure if they get stored
prime kraken
Do you know where this used to be stored? I am unfamiliar with the intended flow here but will look in to it
stray sail
in subscription meta data
prime kraken
Do you have an example ID of a subscription (sub_123) that you saw get created with this data set properly? Looking in to this and that could be a helpful reference
prime kraken
Gotcha, I will see what I can find from our docs. Server is a bit busy so it might be a few more minutes before I can properly look
stray sail
sure
prime kraken
Unfortunately I am not seeing a way to have this go directly to metadata. If you can customize the URL further, you may be able to set a client_reference_id and may be able to use that to link the UTM details to the specific payment that got redirected back to you
Oh or you can include the {CHECKOUT_SESSION_ID} template parameter (this shows it for Checkout but it works for PaymentLinks). That will be replaced by the actual checkout session ID on the redirect, so you can use that to set metadata for the UTM params https://stripe.com/docs/payments/checkout/custom-success-page#modify-success-url