Just started to implementing Klaviyo api to our site and have an issue - dev and production environments separation
Cannot find in the sandbox profile possibility to create an sandbox public & private api keys to split real & test data
Because there is the possible to create separate Lists & Segments, but the events, tracked from the backend are transferred on keys and all get now to the main profile, and it would be great that dev environment was separated not to knock down real statistics
Welcome to the Klaviyo Community! Happy to jump in to help.
The best way to keep your data and profiles safe would be to create a separate Klaviyo account that is linked to your sandbox url for your staging environment. You can use multi-account privileges to make managing your staging environment and live sites easier. You could also create a custom metric in your main account (depending on what you want to test) and create test profiles i.e. using an email alias but I wouldn’t recommend that because if something goes wrong it’ll become a mess. I would check out this additional response from @retention, he provides some additional resources too look into!
Welcome to the Klaviyo Community! Happy to jump in to help.
The best way to keep your data and profiles safe would be to create a separate Klaviyo account that is linked to your sandbox url for your staging environment. You can use multi-account privileges to make managing your staging environment and live sites easier. You could also create a custom metric in your main account (depending on what you want to test) and create test profiles i.e. using an email alias but I wouldn’t recommend that because if something goes wrong it’ll become a mess. I would check out this additional response from @retention, he provides some additional resources too look into!