Klaviyo Track Events Deprecated

The original callin.io app for Klaviyo utilized the Klaviyo V1/V2 API. This version of the Klaviyo API has been deprecated by Klaviyo themselves, and is scheduled for withdrawal on January 1st, 2024.

Consequently, we have developed a new version of the Klaviyo app employing their updated API. However, due to several factors, a straightforward upgrade isn't feasible (the endpoints do not offer a simple 1:1 mapping – refer to here).

Any workflows utilizing the original Klaviyo app modules will continue to function until January 1st. However, prior to this deadline, it will be necessary to substitute those modules with their equivalents in the new Klaviyo app.

We intend to send out an email campaign to all Klaviyo app users to clarify this, and we are also planning further enhancements for the new Klaviyo app.

Wow, okay… I've also posted on the Klaviyo forum. I really miss the capability to send custom metric events to Klaviyo. I don't see anything in the API that I could utilize for that purpose.

I'm still looking into this, but it appears the Track Event API has been superseded by the Create Event API. You can find it here - Create Event.

It would be great if the Klaviyo API could be updated to reinstate Custom Events, so we wouldn't need to rely on the API for this functionality.

It seems the Klaviyo APIs are being updated, but not all powerful features, such as searching for members within a Segment, are being leveraged. I'd appreciate it if this could be addressed.

Thanks for the feedback.

The scale of changes in the Klaviyo API means that we’ve not yet been able to implement the new features as quickly as we would have liked. We do have plans to add some new functionality, including adding a module for the new Get Segment Profiles endpoint to replace the old Check if Someone is in a Segment module, and adding a Make an API Call module to cover any new endpoints that we’ve not added as modules. News of that will go out at the same time as the Klaviyo app upgrade notification.

I’ll make sure our App team is aware of the Track Event → Create Event change as well, though I can’t give any guarantees on when that will be released.

As there’s still 6 months left, if there’s functionality you need in the new App that isn’t yet there, I’d recommend letting us know but staying on the old App until it’s released. Alternatively, you’ll be able to use the Make an API Call module in the new App when it’s released to cover any missing modules.

Klaviyo is a really important partner for us, so we’re keen to ease the pain of the API changes as far as we’re able.

I prefer to address potential issues proactively rather than waiting for them to become fully deprecated. I'd like to tackle this as soon as possible. Perhaps someone here can assist me with this API and point out where I might be going wrong. I'm not a big fan of APIs and still find them challenging, as I'd rather dedicate my time to generating revenue. Can anyone help me identify my mistakes?

This might be quite straightforward… within the profile object, you have "$email ":… I believe that should be without the trailing space!

Yep…That was it! Got it working…Boy do I hate APIs…haha

Big Help

Final Request Content Solved:

{
  "data": {
    "type": "event",
    "attributes": {
      "profile": {
        "$email": "{{1.email}}"
      },
      "metric": {
        "name": "User Logged In"
      },
      "properties": {
        "email": "{{1.email}}"
      },
      "time": "{{now}}"
    }
  }
}

Just wanted to let you know that we're planning to fast-track the Create Event module. It's scheduled for release alongside the other Klaviyo App updates and the upgrade email notification.

Appreciate your feedback!

Great news! Hopefully, the Segment API can also be expedited.

We're planning to release all those App additions (including Get Segment Profiles, Create Event, and Make an API Call) simultaneously. We're targeting a release within weeks rather than months.

Hello,

I was wondering what information you used for authentication. I'm having trouble figuring out what needs to be placed where.
I'm likely worse than you when it comes to APIs.

Here's a screenshot of the "Add a new keychain" pop-up.
I know you had difficulty signing in, but I couldn't find the solution in your thread on how you resolved the issue.
This is the section I don't understand in the Klaviyo documentation regarding authentication:
Klaviyo-API-Key your-private-api-key
What exactly is the Klaviyo API KEY?

Any suggestions?
Thanks

Haha…Yeah…those pesky APIs. Once you establish the connection, you can't retrieve it, so I might be mistaken about some of this. However, the error messages at the bottom will indicate what went wrong.

1. The Name can be any name you select for the API Key.
2. The Key is the actual API key from Klaviyo.
3. API Key Placement is the Header.
4. API Key parameter name is: Klaviyo-API-Key

This is the response I'm receiving:

• status 401
• code not_authenticated
• title Authentication credentials were not provided.
• detail Missing Authorization header.

For your information, this is the API call I am attempting:

I'm unsure if I need to include something in the header section (refer to the screenshot). I've tried using Klaviyo-API-Key, but it's not working.