@Trevin_Chow: For the amplitude integration, we’d like to be able to use a different API key depending on whether we are in our staging env or production. (i.e. we don’t want staging data to be sent to our production amplitude instance).
When looking at the Amplitude integration setup, I only see a single amplitude API key field. I think this means I’d have to create 2 different forms and to be able to setup different integrations.
Is this correct?
@peter: currently that is the case, although it’d be fairly easy for us to extend the integration to support separate api keys for the different environments
@Trevin_Chow: @peter thanks for confirmation. I think that most 3rd party integrations will have different envs and making sure we can split that is really important. So i don’t think this is just an amplitude thing, but def something that we’re focused on since it is a huge part of our data story
@peter: we already support environment separation for a lot of our integrations such as stripe, auth-related ones, webhooks, etc.
if you share which integrations you’re looking to support, we can explore how hard or easy it’d be to get that working for you based on your requirements
@Trevin_Chow: Amplitude, Rudderstack
@peter: Yep, both would be straightforward for us to update for you