In short, although Klaviyo cannot add additional fields to the WooCommerce Started Checkout event like the company field, your goal can be achieved by either sending Klaviyo a custom Checkout Started event containing the field of your choosing (company) or you can send an identify request to Klaviyo. The latter method would allow you to update company as a custom property on a profile, instead of event data.
In short, although Klaviyo cannot add additional fields to the WooCommerce Started Checkout event like the company field, your goal can be achieved by either sending Klaviyo a custom Checkout Started event containing the field of your choosing (company) or you can send an identify request to Klaviyo. The latter method would allow you to update company as a custom property on a profile, instead of event data.
We’re writing the code to push that additional field.
I know this is outside your control, but it’s just weird that the default field named “Company” in WooCommerce doesn’t get pushed into Klaviyo automatically even though it may line up perfectly with Klaviyo’s default $organization field.
Maybe I misunderstand what Klaviyo is doing.
As a result we have to write our own custom code to push it.
You are not misunderstanding anything at all. The company field just isn’t a field that we pull in from WooCommerce at this time. With that said, I have filed a a proposal for our product team to consider implementing it in the future. If we receive enough interest from the Klaviyo Community, the product team will take steps to implement this field by default for our integration with WooCommerce.
It really baffles me that when Klaviyo did the initial “integration” they didn’t simply take all fields that are core in Woocommerce. Subtotal excl. VAT is also missing
A
Anonymous
0 replies
January 19, 2022
I’d like this as well for my clients. Does Klaviyo have a public list of requested features where I can upvote this request?
I have added a product feature request on both of your behalf as well! Hopefully this will gain some traction, if there is any update on this in the future, we will update you in this thread!
There is currently no new updates on syncing Company field from WooCommerce to Klaviyo unfortunately. The best method is still what @Dov replied in his original post. Either by sending Klaviyo a custom Checkout Started event containing the field of your choosing (company) or you can send an identify request to Klaviyo. The latter method would allow you to update company as a custom property on a profile, instead of event data. If there is an update in the future we will notify you in this thread!
I’d recommend doing an identify API request (as Stephen mentioned) on the order confirmation page and then saving the company to the customer’s profile in Klaviyo.
In this way it doesn’t affect or delay checkout process with outbound requests and saves the info where you can retrieve it in any campaign or flow.
If anyone needs this custom built, please feel free to reach out!
By clicking “Accept All Cookies,” you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts.
Privacy Preference Center
Your Privacy
Strictly Necessary Cookies
Performance Cookies
Functional Cookies
Targeting Cookies
Site Analytics
Your Privacy
When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
Privacy Notice
Strictly Necessary Cookies
Always Active
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
Performance Cookies
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
Functional Cookies
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
Targeting Cookies
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Site Analytics
These cookies record your visit to our website, and are used to track your visit including information such as: web page interactions (clicks, hovers, focus, mouse movements, browsing, zooms and other interactions), referring web page/source through which you accessed the Sites, heatmaps and scrolls, screen resolution, ISP, and statistics associated with the interaction between device or browser and the Sites. If you are accessing our Services with a European IP address, you have been asked to consent to the use of these cookies (you are free to deny your consent).