I just finished building a few scenarios that include connecting to Klaviyo. I used a custom webhook at the beginning of the scenarios, but I used the Klaviyo “Add/Subscribe Profiles to a List” module (and tested the “Create and Add a Profile to a List” module too) to add profiles that have opted-in to email marketing to my Newsletter list in Klaviyo. Everything is working as expected (profiles are appearing in my Newsletter list), but I am still seeing this:
I have added a few custom properties so I can confirm if, how, where, and when a profile consented to receiving email marketing, and then add filters accordingly to my flow triggers, so this isn’t a huge deal. But I am wondering if anyone knows how to make this happen instead?
I have tried setting my Newsletter list to “single-opt in.” I have tried adding $consent, Consent, Status, and $consent_method to the module as custom properties, but so far nothing has worked. I am using “email” as the value for the “$consent” key, and Make and Klaviyo are both interpreting this key-value pair as an array.
Thank you so much!
Hello again @Kari_G,
Could you please share screenshots of the module fields and filters in question? It would really help other community members to see what you’re looking at.
You can also export the scenario blueprint file to allow others to replicate the issue. At the bottom of the scenario editor, you can click on the three dots to find the Export Blueprint menu item.
Uploading it here will look like this:
blueprint.json (12.3 KB)
If possible, could you also please provide the input/output bundles of the modules by running the scenario, then clicking the bubble on the top-right of each module, taking screenshots of, and copying the contents into this discussion thread:
This will allow others to better assist you. Thanks!
Can you please share the screenshot of the scenario for better assisstant.
It’s possible that this is a Klaviyo feature, rather than anything you’re doing wrong in Make!
I noted that the Klaviyo Subscribe Profiles to a List API endpoint help mentions “Note: If you have double opt-in enabled (default behavior), users will not be added to list until they opt-in …”
This Klaviyo help article explains more on double opt-in, and this article talks specifically about using the API for email consent (and touches on double vs single opt-in).
It looks like there’s no way to set a list to single opt-in through the API - it seems like you need to do that through the Klaviyo UI.
Thank you so much once again for all of these quick replies! I managed to get this sorted out thanks to these suggestions. What a great community this is!
@DavidGurr_Make - Yup! The list in Klaviyo has to be set to “single opt-in” from inside the Klaviyo app. I also used the Klaviyo API documentation you mentioned in your reply to to help me solve this. Thank you, thank you!
@samliew , your troubleshooting suggestions got me thinking about potential issues with output. Thank you for that as well! Because of your suggestions, I decided to try creating my own HTTP module API call to troubleshoot this.
It looks like Klaviyo is updating their entire API surface with new endpoints. It’s a lot to keep up with and updates are happening quickly and often right now it seems. When I looked at the new “Subscribe Profiles” API documentation (here), they listed a header requirement that is rather recent:
–header ‘revision: 2023-08-15’
Also, whoever created the “HTTP Module” tutorials on your Make YouTube channel, thank you! I found these super helpful as I wasn’t sure how to set up an HTTP module.
I created a very simple test scenario and I was able to get the green checkbox to show up in Klaviyo - screenshots are below. I excluded SMS subscription information from my call, as I currently don’t use that feature in Klaviyo.
Thank you again for all of your help! I’m learning so much from you all, and having a great time - this platform is super fun! Hope you all have a great weekend!
Postman post request to Make webhook:
HTTP module configuration - Klaviyo endpoint, etc. info here:
Jane Doe profile page in Klaviyo:
Hey @Kari_G! I’m glad to hear you’re having fun with Make. That’s always part of our goal!
The Klaviyo API doc is slightly misleading with the API revision headers. You don’t have to use the latest API revision. Usually that’s only necessary if you’re using functionality that’s only available in a later revision - see their Changelog.
All the Klaviyo app modules in Make are using the 2023-02-33 revision of the API, including the
Add/Subscribe Profiles to a List module (which uses the Klaviyo API endpoint
Hi @DavidGurr_Make ! Thank you so much for this additional information about the Klaviyo APIs, and for the link to the Changelog. I bookmarked that one. I appreciate your in-depth knowledge of Klaviyo as well - the Klaivyo modules are one of the many reasons I chose Make. So thank you so much for sharing your expertise with me! It help a lot!
Have a great weekend!
You’re very welcome! Glad to have you on board