Klaviyo announced the retirement of their version 1 and 2 API endpoints over a year ago. Those endpoints will be officially retired at the end of this month – June 30, 2014 . Version 3 of the API offers a lot of benefits and frankly its much easier to use and integrate. We were never a fan of sending data in the old base 64 format using via the legacy API.
On the downside, everything broke as other than functionality there is not much similarity between the old legacy versions and the new version. This has forced us to do a complete rebuild of our Contact Form 7 integration, which was not necessarily a setback, as it resulted in a much more robust plugin with additional features and improved code quality. Unfortunately, as a result of the rebuild all our clients will need to reinstall and reconfigure our plugin 😔
What’s New with Klaviyo Contact Form 7 Integration – Version 3
We have focused mainly on improving the existing feature set, but we also have a few new additions.
Updated Documentation
We did not have comprehensive documentation initially. However, there was much greater demand for our PRO plugin than we anticipated. As a result, we ended up with many support requests all of which we have been handling over email until now. Check out our new help center. Our clients can track support tickets and find documentation in a central location. Our previous help desk was reserved only for our maintenance clients, however, users of our plugin deserve the same treatment. This will be the new home for all our upcoming plugins and Sitecare support going forward.
Plugin Features
Refresh Lists
Users can now refresh their Klaviyo lists to synchronize any new additions with their contact forms.
International Phone Number Formatting
Klaviyo Requires phone numbers to be in E.164 Format. In the past we had many clients reach out to us to figure out why the form data is not being sent to Klaviyo only to realize users don’t always enter phone numbers in international format. This feature will validate phone numbers and display them in the correct format to users. You can see an animated demo in the documentation.
Enable/Disable Logs
Logging every request can be an unnecessary strain on your website database and lead to performance issues. Users of our plugin now have the option to disable logging every request and this feature can be saved for when it needed, which is generally during debugging. The logs are also a bit more detailed now, thanks to the version 3 API.
Deactivate License
Users of the pro version of our plugin often reach out asking to remove the license from their old domain. It was always possible through their Sitepact account, but now they can also deactivate their license from the plugin settings screen.
There are many new changes made under the hood but these are the primary features that have a visual or user-interactive front.
What is Improved with Klaviyo Contact Form 7 Integration – Version 3
We have made numerous improvements to the plugin, especially since rebuilding it, allowing us to incorporate all user feedback into our decision-making process. We will not explore everything that was improved as most of it is technical only the user-facing and database portion.
UI Improvements
The interface for mapping fields is so much cleaner and uniform. Buttons and colors now match the default style of the WordPress Admin interface. The old design used some bootstrap styling which was removed and we ended up using way less CSS for styling. We also removed image icons and replaced them with WordPress Dashicons instead and used the default styling for all input, select, and checkboxes. Now our Klaviyo Contact Form 7 Integration looks like a real WordPress plugin 😊
Database Improvements
We made improvements to the database by renaming tables (done during updates) with shorter, more recognizable names and removing unnecessary meta. Previously, there were issues with creating tables during activation in different environments. We’ve also added backup support for such cases. Tied to this is the request logging. Now you don’t need to save every request to the database, you can simply keep this disabled during production. We may add further improvements to this in the future.
What is Removed with Klaviyo Contact Form 7 Integration – Version 3
There is not much overhead that we would consider removing however, 2 things are gone. Metric Flow and Resubmit to API from the log screen.
Metric Flow
Klaviyo has changed a lot over the last 3 years. We assessed the best way to work with Flows in Klaviyo as we concluded that in the vast majority of cases, users will set up their flows in Klaviyo and trigger those flows using custom fields or some other form of subscriber segmentation.
Resubmit Requests to Klaviyo
This is a feature we will add again in the future. It is not a heavily utilized feature as it is mostly used in debugging. With logging every Klaviyo request on contact form submission now optional, the feature will be utilized even loss so it was not a high priority at this redevelopment stage.
Wrapping up
The transition to Klaviyo Contact Form 7 Integration Version 3 signifies a significant improvement despite initial challenges with retiring legacy API endpoints. While rebuilding our plugin requires clients to reinstall and reconfigure, resulting in some inconvenience, Version 3 introduces valuable updates such as enhanced documentation, new features like list refreshing and international phone number formatting, and improved UI and database efficiency. We are committed to delivering a more user-friendly experience that aligns with WordPress standards and meets the evolving needs of our users, and we look forward to further enhancing our offerings based on feedback and technological advancements in collaboration with Klaviyo.
Check our the free version of our plugin from the WordPress repository – Get Free Klaviyo Plugin. You can also install this from the plugin section of your WordPress website.
Kudos!
