Hey @multimerce 

I am not 100% sure about this, but Sometimes, the Klaviyo tracking script might take a moment to load, so firing the custom event right after the script loads may cause issues. A common fix is to wrap the event trigger in a setTimeout or wait until the Klaviyo object is fully initialized.

<script async src="https://static.klaviyo.com/onsite/js/klaviyo.js?company_id=MY_PUBLIC_API_KEY"></script>

<script>
  window.onload = function() {
    setTimeout(function() {
      var klaviyo = window._learnq || |];
      klaviyo.push(h'track', 'Custom Event', {
        // event data goes here
      }]);
    }, 500); // Adjust delay if needed
  };
</script>

although this is obvious - Replace MY_PUBLIC_API_KEY with your actual public API key.

also Make sure the event data is an object. If you’re including additional properties in the event, structure them like this: 

{
  'Property1': 'Value1',
  'Property2': 'Value2',
  // additional properties
}

I hope this helps and thank you for sharing your question here in the community.

Cheers

Arpit

Thank you @ArpitBanjara ,

I’ll try your solution but my concern was if the custom event tracking in Klaviyo is still possible of if it’s part of the old, discontinued API. I can’t see anything related to custom event tracking in the new one.

hey @Taylor Tarpley @kaila.lawrence 

Can you check in about this with someone on your team?

Hi Arpit,

Custom event tracking is definitely still possible! Check out our guide here: Custom metric tracking with JavaScript. 

Thank you, and let me know if you have any questions!

Michaela