Dear Klaviyo Community,
We have a custom site developed using Laravel & Vue.
Our site works like a service reservation site wherein guest users are allowed to make transaction. But upon putting all the codes and following the contents from the API documents we are still getting issues on the above subject for guest users but if we try a transaction for a logged-in user the thing works.
Are we missing something or is Klaviyo codes is designed for logged-in users only?
We appreciate any response or help that may clarify the above subject.
Thank you in advance.
Best answer by julie.accardoView original
Thanks for reaching out in the Community!
If you are using email address as the unique identifier within your account, which is the recommended setup, then you will need to ensure that the email address is being passed with the triggering event. Is there a reason why you are not passing this information even for a guest checkout? I would assume that you’d be collecting email address at some point in the guest reservation for transactional communication (i.e. reservation confirmation).
Also, it would be helpful to have more detail around the specific event that you are trying to trigger and the API calls that you’re making.
Sorry for reverting too late. We were able to resolve the email error by that time your inputs were helpful. We just recently went back on the project and found out that even if the code snippet is already there its not triggering to track the activity of the user going to the site.
Does this happen in general to customized sites like us, by the way our site is created using Vue.JS. Any feedback/inputs will be appreciated. Or is there anything we need to send you to further verify this item.
Thank you and keep safe.
I am glad you were able to resolve the email error! And thank you
@julie.accardo for your helpful input on the issue.
This doesn’t happen in general to customized sites - users who decide to build a custom solution are usually able to follow our guide here to successfully set up their custom solution.
Thanks for being a member of our Community.
Thank you for the valuable reply.
Would it have to do something in this scenario that’s why some of the tracking activities does not function?
Our site is a online services booking system, wherein the way a customer transacts is as a “Guest User/Account” only and registering a user account is optional at the end of the Checkout process. So whenever they comeback to book services again, they have to repeat the same process.
Would it be better or advisable to require the customer to logged-in first with a registered account before doing transactions? Coz’ initially when we developed the system we are more almost done with the whole thing then along the way Klaviyo was decided to be used so I guess the original design inside has not considered the components of Klaviyo prior unfortunately.
Thank again in advance for your feedbacks
Thanks for your follow-up reply.
Potentially. In order to successfully track users, you would have to meet one of the criteria I outlined in my previous reply.
This can occur through any of the following methods:
Also, there is nothing about using a online services booking system that would preclude the ability to log web tracking metrics, you will just need to keep in mind the requirements for logging a web tracking metrics for Klaviyo and also keep in mind that there may be potential conflicting code from VueJS (or another application/plug-in) preventing the Klaviyo onsite javscript from working as it should. This would be best to be investigated by a developer or one of our wonderful partners.
I hope that is helpful!
Thanks again for giving time to respond to our inquiries and clarifications.
I think the system we designed and coded needs to be reviewed and modified to comply with what Klaviyo has on its guidelines. Like what I’ve mentioned on earlier messages, we are almost done with the whole system when we are requested to put Klaviyo inside. It was not yet considered that time to be part of the whole system development design from Day 1 not until the day arrived.
The Dev team may have to restructure or modify the existing components of the system in order to meet the requirements of Klaviyo as per document reference guidelines is concerned.