| ||||
| ||||
|
Best answer by Taylor Tarpley
View original
| ||||
| ||||
|
Best answer by Taylor Tarpley
View originalHi
Thanks for bringing this to light in the Developer Community and ensuring that your peers are up to date on this change to our API!
Yes, the term ‘in-house’ and ‘built-in’ integration are both referring to an integration in the Klaviyo system. A custom solution refers to a custom connection made as there is no native connection between two platforms. Essentially, any custom or third-party integration, that is using our Identify API to update profile information will need to be made aware of our new implementation of the Klaviyo Profile API and make the change accordingly. This change will help us increase our security and protection of customer information by utilizing a private API key from now on.
Thanks for making good use of this new group!
-Taylor
Thank you. But I don’t see any clear step-by-step directions for what I’m supposed to do to make sure that integrations still work. For example Facebook integration. What do I need to do to make sure that keeps working?
Hi
Happy to share more insight here! First, you will need to evaluate if any of your custom/third-party integrations are were even using the Identify API in this manner. If not, no worries! However, if you are, then you’ll essentially want to work with your developer to resolve this and instead of leveraging the Identify API to update an existing profile's Unique identifier, you’ll want to use the Profiles API. The next exact steps you need are on an individual case-by-case basis depending on how each company is using these Identify API endpoints presently to know what to do next.
-Taylor
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.