Replies posted by CoBE_Sean

6 Replies

CoBE_Sean
Contributor II
CoBE_SeanContributor II
asked in Developer Group

Javascript tracking not working in sandbox (custom integration)

Ok, I think I finally resolved my own issue here.  A few things to keep in mind, that might help others:-Using Klaviyo.push for the identify call was wrong method here.  Klaviyo.Identify is what seems to work.  I’m still not 100% clear on the use cases for each method though. -By using the testing URI variable ?UTM_email=[email_address] in the beginning, I never really saw that the identify call wasn’t working, because the variable ‘forced’ the identify call through.  So, if you are trying to identify users from a website login (not a klaviyo cookie), I recommend getting that working, before forcing it with the UTM variable.So in the end, it had nothing to do with credentials or authentication.  Just not using the correct method for the Indentify call.  I think the documentation could be a little more clear on what the difference and use cases for ‘pushing’ the identify call vs. using the klaviyo.identify call. 

6
Brian Turcotte
Community Manager
1 year ago
M
Contributor II
mchuContributor II
asked in Analytics and Deliverability

For users that are coming to a webpage that has Klaviyo.js but don't have the cookie, is there a way to track events for those "guest" profiles?

@marissa.petterutiI have been struggling with why my tracking in our test integration stopped working.  I added the ?utm_email=example@gmail.com variable to the URL and it started working again. However, we do have the identify tracking in place, so I’m wondering why I would need to run this URL variable to re-cookie my user, if we are identifying them through our website’s account login? Is there a cookie we can add/force when a user logs in and is identified?  Thanks

4
David To
Klaviyo Employee
1 year ago
CoBE_Sean
Contributor II
CoBE_SeanContributor II
asked in Developer Group

Javascript tracking not working in sandbox (custom integration)

So, I think I figured out why my tests stopped tracking. I guess if you have this setup, you need to run this on  your URL before you test, or after you clear your browser cache/cookies:Add the following to the end of your store url, replacing example@gmail.com with your email address:?utm_email=example@gmail.comHere’s the page with that info: https://help.klaviyo.com/hc/en-us/articles/115005076767-Klaviyo-Web-Tracking#who-klaviyo-tracks...because:When you add the Klaviyo.js snippet to your site, we are only able to track the browsing activity of "known browsers" - browsers that have visited and engaged at least once before. Klaviyo will not track anonymous browsers.  I’m now going to search the community for more info on ‘known browsers’ and what this really means for how much website tracking we’ll really see from this.  I’ll paste any links I find here.  However, if anyone can explain exactly what this means, that would help. I’m starting to gather that just because a user signs int

6
Brian Turcotte
Community Manager
1 year ago
CoBE_Sean
Contributor II
CoBE_SeanContributor II
asked in Developer Group

Javascript tracking not working in sandbox (custom integration)

@Brian Turcotte Just checking to see if you saw my last reply?  Still haven’t been able to get any of this tracking working again, on either live or sandbox profiles.  Thanks

6
Brian Turcotte
Community Manager
1 year ago
CoBE_Sean
Contributor II
CoBE_SeanContributor II
asked in Developer Group

Placed Order value not showing up in Profile metric data

Thank you @retention that did the trick!  👍

2
CoBE_Sean
Contributor II
1 year ago
CoBE_Sean
Contributor II
CoBE_SeanContributor II
asked in Developer Group

Javascript tracking not working in sandbox (custom integration)

Thanks Brian.  Please see the attached screenshot, which shows my source code and our API settings page, in Klaviyo.  You’ll see the key matches.  *This is for our Sandbox account.It’s my understanding that this is the only credential that the JS tracking metrics use to authenticate...So I’m not sure what other credentials I should be checking on, for ‘authentication issues’. As I mentioned before, this was all working fine before, when we were just testing using the live api keys.  All I did was switch the public key to our sandbox account and now it doesn’t track in either.  I let the sandbox creds site overnight, cleared browser cache/cookies, etc.  and it still isn’t tracking.  I’m also including a screenshot of the event calls (identify and viewed product), which should be tracking to my test profile (sandy_sean@cobedev.com), but is not. Public API key matches settingsevents that should be tracking (identify and viewed product) 

6
Brian Turcotte
Community Manager
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.