Custom Cart Integration and Klaviyo.Identify. When and Where?

Hi @rollbg!

This is definitely not a stupid question! Once a user is cookied, the cookie persists throughout their session and will remain whenever that user accesses the site (so long as it’s via the same device and browser) - this guide explains it more.

For testing, you can use the Chrome DevTools console to see if you are cookied or not. Screenshot 1 is a function you can run in the console for a NON-cookied user. Screenshot 2 shows the function output for a cookied user:
 

Essentially, you can use the javascript function klaviyo.isIdentified() in the console to see if you are cookied or not during testing. You can run the above function as you navigate your site to prove that the cookie will persist as you navigate to different product pages, etc.

I hope this helps, and thanks for using the Community!

- Brian

Thank you very much for your answer. Based on your post I came up with the following solution:
 

if ($('#lnkProfile').data('email')) { //Checks if user is logged in
	console.log('User is logged in. Check if identified.');
	klaviyo.isIdentified(klaviyoIdentify);                            
};
function klaviyoIdentify(result) {
	if (!result) {
		console.log('User is not identified. Identify now.');
		klaviyo.identify({ '$email': $('#lnkProfile').data('email') }).then(() => console.log('Identify has been completed'));                                
	}               
};

The script is placed immediately after the Klaviyo.js snippet and the Klaviyo object definition.
My idea is to check if the user is logged in and then check if “isIdentified”. If not I call klaviyo.identify with the corresponding email.

Unfortunately it does not work as expected. When I load a page with logged in user I get this in the console:

As you can see promise is never returned. And I don’t see a call to Klaviyo’s servers in the network tab of the DevTools. Looks like the identify call fails silently.
But if I then run my function “klaviyoIdentify(false)” manually in the console it works:

My initial thought was that Klaviyo.js was not loaded properly yet when I call klaviyo.identify, but if that was the case I should get an error like “klaviyo is not defined” or something. Furthermore obviously klaviyo.isIdentified works so the library should be properly loaded right? I don’t get it.

According to this doc the isIdentified method supports a callback parameter. So once the isIdentified call resolves, it runs the user code to identify the session if it is not already identified. The results from @rollbg showed that the callback was started, but the identify call inside it doesn’t identify the session.

Hi @TTook

Thanks for pointing that out! I’ll check on that with Engineering and update the thread as soon as possible.

Best,

Brian