Replies posted by JeffV.klaviyo

6 Replies

A
Contributor I
andrewbarkerContributor I
asked in Integrations and Reviews

My Add to cart event is not firing on the Analytics

Hello @andrewbarker! Generally, for Add to Cart snippet troubleshooting we should look for these things:Is your Viewed Product metric successfully syncing? The Add to Cart snippet relies on variables created in the Viewed Product snippet, so the Viewed Product snippet must be working correctly in order for the Add to Cart snippet to work. Do you see your snippet in the source code? You can confirm this by opening up a product page on your website. Then do a right click > View Page Source > open up a search box (cmd + f on mac, or ctrl + f on PC) > search for your snippets (using “learnq” as the search term should locate them for you. Is the user browsing your site cookied? In order for the metric to sync to your account, the user browsing your site must be cookied. You can cookie yourself by visiting your site and appending ?utm_email=youremail@email.com to the end of the URL (ex. yoursite.com?utm_email=jeffklaviyo@inbox.com). Once you are cookied, you can view a product page

1
JeffV.klaviyo
Klaviyo Employee
2 years ago
O
Contributor I
ojhurstContributor I
asked in Developer Group

When using Subscribe API and Zapier its creating two profiles (one for email and one for phone)

Hi there,Jeff with support engineering here. We resolved this offline, but for the sake of transparency, the reason why two profiles are being created is because the payload has two profile objects within the profile array:{"profiles": [ { "email": input_data["email"] }, {    "first_name": input_data["name"],    "phone_number": input_data["phone_number"],    "sms_consent": sms_consent,    "$consent": ["sms","email"] }]} The curly bracket {} signify separate profiles. So if we wanted all this information to sync over as one profile it would look like this:payload = {    "profiles": [{        "email": input_data["email"],        "first_name": input_data["name"],        "phone_number": input_data["phone_number"],        "sms_consent": sms_consent,        "$consent": ["sms", "email"]    }]} In the above payload, we include all information within one set of curly brackets {} and they will sync to Klaviyo as one profile. 

2
JeffV.klaviyo
Klaviyo Employee
2 years ago
D
Contributor I
dramlakhContributor I
asked in Analytics and Deliverability

API - Trying to retrieve all the Events using the metric timeline

Hi all, Jeff here with Klaviyo Success Engineering. I was the individual who Alex connected with to resolve this issue. Wanted to provide the resolution here for visibility purposes in case anyone else hits this issue.In our API endpoint to get events for a specific metric (https://developers.klaviyo.com/en/reference/metric-timeline), we allow for users to set a batch size that determines the numbers of events to return in a given batch (max is 100). If an API call has more events than your batch size, we provide you with a pagination token obtained from the ‘next’ attribute of a prior API call. This pagination token can be used as the value for the ‘since’ key/value pair in the parameters of the call and allows you to pick up where you left off in the previous API call.You can learn more about this by reading the description of the ‘since’ parameter in the documentation for this endpoint here: https://developers.klaviyo.com/en/reference/metric-timeline

4
JeffV.klaviyo
Klaviyo Employee
1 year ago
KeviSunshine
Expert Problem Solver II
KeviSunshineExpert Problem Solver II
asked in Developer Group

Base64 Encoding a stringified JSON object

To close the loop here, we resolved part 1 of @KeviSunshine’s original question with the flow webhook action. The next step was to give Kevin the ability to base64 encode the following text:"phone: <customer_phone_number>"This was a bit tricky as we needed to take a string (“phone: “) and combine it with a dynamic variable (customer_phone_number), and then 64 encode the entire thing. Since our email templates use Django syntax, we needed to do the following:{% with phoneNum=person.phone_number text='{"phone": ' %}{{ text|add:'"'|add:phoneNum|add:'"}'|base64_encode }}{% endwith %}Essentially, we need to save the string “phone: “ as one variable and then the customer’s phone number ( {{person.phone_number}} ) as another variable. We then used the django |add filter to concatenate/combine the two strings, and the |base64_encode django filter to encode everything.Thank you for your patience @KeviSunshine and let us know if there is anything unexpected occurring with this solution. 

4
JeffV.klaviyo
Klaviyo Employee
1 year ago
L
Contributor I
laughteamContributor I
asked in Developer Group

Developer documentation outdated - legacy form custom properties

Hey @laughteam yep that was me...I’m one of the support engineers at Klaviyo that Alex contacted about this. Happy that was able to resolve the issue for you. I’ll be having the docs team take a look at this as well to ensure our documentation includes the necessary info/gotchas.  For anyone else in the community who might come across this. As @laughteam mentioned, Klaviyo Lists have Double Opt-in enabled by default, and users will not be added to the list or have custom properties added to the profile until they confirm their subscription. They will, however, have an “empty” klaviyo profile sync upon filling out the form. The profile will fill out with custom props/list additions once they confirm their subscription. You can learn more about the Double Opt-in process (including how to shut off this functionality) here: https://help.klaviyo.com/hc/en-us/articles/115005251108-Understanding-the-double-opt-In-process

3
JeffV.klaviyo
Klaviyo Employee
1 year ago
S
Contributor IV
santiagosantiContributor IV
asked in Developer Group

getting invalid action id error

Hi @santiagosanti  Hope all is well. It sounds like you might be missing the action ID or some other resource in your API call.Correct me if I am wrong, but it sounds like you are first making an API call to our “Get Flow Actions For Flow” endpointhttps://developers.klaviyo.com/en/reference/get_flow_flow_actions https://a.klaviyo.com/api/flows/{id}/flow-actions/When making this API call, you need to enter the Flow ID into the {id} section of the API endpoint. Once you successfully make this call, your response will have all the actions in that Flow, and will provide you with an Action ID for each action: Once you have an Action ID, you can use that value in an API call to “Get Messages For Flow Action”https://developers.klaviyo.com/en/reference/get_flow_action_messages https://a.klaviyo.com/api/flow-actions/{id}/flow-messages/ It sounds like you are failing to include an action ID in some of your API calls

2
JeffV.klaviyo
Klaviyo Employee
10 months 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.