Solved

Track Profile Activity

  • 15 November 2023
  • 5 replies
  • 80 views

Badge

What REST point I have to use to replace obsolete Track Profile Activity https://developers.klaviyo.com/en/v1-2/reference/track-post
I tried https://developers.klaviyo.com/en/reference/create_event but I don’t see any events even if response is 202

icon

Best answer by saulblum 16 November 2023, 03:10

View original

5 replies

Userlevel 5
Badge +19

What exactly do you need to do? They’ve split the Track endpoint into multiple endpoints now so it really depends on what you’re trying to accomplish. 

Badge

just simple events 
like “remove product” with props productname/sku/price or “placed order” with props orderid/date/ and other custom

Userlevel 5
Badge +19

They have a new event endpoint with all the required datapoints on the api overview page. Just make sure the most recent api version is selected in the upper-left corner. 
 

it looks like that’s the one you’ve already tried so if it’s not working, try ping it from a service like Postman. If that works, you know there’s a problem with the server or app running your code. If it still doesn’t work with postman, you probably have a mistake in your json somewhere. 

Userlevel 5
Badge +7

We actually just published a guide to migrate the old track endpoint to the new Create Event call:

https://developers.klaviyo.com/en/docs/migrate-track-identify-and-subscribe-to-our-new-apis

See if this helps.

There’s also a new Developer Tools section under Integrations, with API logs, that can hopefully help you troubleshoot why you’re getting a 202 response but are not seeing the event:

https://developers.klaviyo.com/en/docs/monitor-api-usage

 

Userlevel 5
Badge +19

Ironically enough, I’m trying to troubleshoot an issue with the Subscribe endpoint right now too. The Developer Tools section is fantastic. I’m not sure when you announced it, but I must have missed it.

I’m in there right now, and I made a successful ‘202’ call but the profile was not actually subscribed to the list. I’m not sure how to debug this further since it’s reporting that everything is correct and no errors.

 

Request body:

{
  "data": {
    "type": "profile-subscription-bulk-create-job",
    "attributes": {
      "custom_source": "Download Itinerary form",
      "profiles": {
        "data": [
          {
            "type": "profile",
            "attributes": {
              "email": "test@example.com",
              "subscriptions": {
                "email": [
                  "MARKETING"
                ]
              }
            }
          }
        ]
      }
    },
    "relationships": {
      "list": {
        "data": {
          "type": "list",
          "id": "LISTID"
        }
      }
    }
  }
}

But in the actual profile record:

 

And yes, the list is set to single opt-in.

Reply