When an API is called using a subscription key, you can access specific information about the subscription via context.Subscription in your policy expressions. The context.Subscription.Id
would be the ideal choice to leverage considering it would be unique for each subscription. You would however require a mapping between this ID and any ID you may have for your own system to identity customers.
You could also use the context.User properties if subscriptions to your API are tied to a user account.
Alternatively, if you'd prefer, you could protect your APIs using OAuth 2.0. This way you could extract customer details after validating the JWT and pass the same to your backend (or the token itself if required).