Replies posted by ChrisR

5 Replies

C
Contributor III
ChrisRContributor III
asked in Developer Group

klaviyo not registering trackViewedItem

Thanks @Brian Turcotte, I was wondering about this, as I had just noticed that little box in the lower right.This raises a couple of questions.I assume the track as opposed to trackViewedItem is required to trigger the browse abandonment flow? If the answer to 1 is “yes”, then what’s the use case for trackViewedItem?Thanks!Chris

8
S
Klaviyo Employee
1 year ago
C
Contributor III
ChrisRContributor III
asked in Developer Group

klaviyo not registering trackViewedItem

I’m going to reach out to Engineering to provide some more context on this and then I’ll update the thread ASAP Thanks Brian!Any update from engineering?I also gave it another shot, attempting to use the promise functionality of the new Klaviyo object, but still no dice. Here’s the updated NextJS code: <Script id='klaviyo-viewed-product' dangerouslySetInnerHTML={{ __html: ` !(async function () { if (window.klaviyo) { await klaviyo.trackViewedItem({ ProductName: "${data?.seminarDetails?.name}", ProductID: "${data?.seminarDetails?.id}", SKU: "${data?.seminarDetails?.__typename}", URL: "${url}", Price: ${data?.seminarDetails?.price} })

8
S
Klaviyo Employee
1 year ago
C
Contributor III
ChrisRContributor III
asked in Developer Group

klaviyo not registering trackViewedItem

Thanks @Omar . Yes, I’m sure. The other events for the same profile are firing, and I put in the debug logging which makes it clear that on the page in question the script is being loaded.

8
S
Klaviyo Employee
1 year ago
C
Contributor III
ChrisRContributor III
asked in Developer Group

klaviyo not registering trackViewedItem

Thanks @Brian Turcotte . Yes, confirmed that both are working.Here’s the generic activity tracking:{/* Klaviyo per-page scripts */}<Scriptid='klaviyo-active-on-site'src={`https://static.klaviyo.com/onsite/js/klaviyo.js?company_id=${process.env.NEXT_PUBLIC_KLAVIYO_KEY}`}/> <Scriptid='klaviyo-object'dangerouslySetInnerHTML={{ __html: ` !(function () { if (!window.klaviyo) { window._klOnsite = window._klOnsite || []; try { window.klaviyo = new Proxy( {}, { get: function (n, i) { return "push" === i ? function () { var n; (n = window._klOnsite).push.apply(n, arguments); } : function () { for (var n = arguments.length, o = new Array(n), w = 0; w &

8
S
Klaviyo Employee
1 year ago
S
Problem Solver I
StefProblem Solver I
asked in Developer Group

$body payload structure – klaviyo-api-php

Yeah, the documentation hasn’t quite caught up with the new APIs yet, but I’m 99% sure you’re having the same problem I was with the Node API. The format for the body should be: "data": {          "type": "profile-subscription-bulk-create-job",          "attributes": {               "subscriptions": [                    {                         "email": "bob@eample.com"                    },                    {                         "email": "tom@example.com"                    }               ],               "list_id": "12345"          }     }(taken from the second link you posted). Notablythe whole thing needs to get wrapped in a “data” (which is different, and internal to the ‘data’ object in the POST request (i.e., the actual POST request will be `data { data: { type ...`)). you need to specify the “type” (the SDK very much makes you think you don’t need to, and you shouldn’t need to, but at least in this iteration, the SDK is just a thin wrapper, so you have to specify everyt

6
S
Problem Solver I
1 year ago

Most helpful members this week

Terms & ConditionsCookie settings

Links & Resources

Platforms

Partners

Useful Things

About

  • Terms and Privacy
    © 2024 Klaviyo All rights reserved. Klaviyo and the Klaviyo logo are trademarks or registered trademarks of Klaviyo, Inc. or its affiliates.