Topics started by viralsweep1

3 Topics

V
Contributor I
viralsweep1Contributor I
asked in Developer Group

How to handle updating profile based on email and phone number

We have an integration with Klaviyo that will pass through standard customer fields like name, email, phone, etc and create a profile for them within Klaviyo.If that same user then attempts to fill out one of our forms again in the future, we just update that existing contact record with whatever information they provided. Here is an example John@gmail.com fills out one of our entry forms with: Email: john@gmail.comName: John DoePhone: 111-111-1111Zip code: 90210 In the future, he fills out one of our forms again, and we update the record with any new information:Email: john@gmail.comName: John DoePhone: 111-111-1111Zip code: 78704 However, now that more and more companies are just wanting to collect SMS/name instead of email, how do we handle a use case in Klaviyo where a phone number already exists on a contact profile and they submit new information? Should we just update the contact record as we previously had when they were submitting with an email? The only issue I can see with t

4
Brian Turcotte
Community Manager
7 months ago
V
Contributor I
viralsweep1Contributor I
asked in Developer Group

Constantly updating a custom property with new values via API

With our current integration we are passing a custom field to a Klaviyo contact called “promotion_id” which identifies which of our promotions they came through. For example, promotion_id: 2715If that same email address enters another promotion, it will automatically update the promotion_id field with the ID of the new promotion, overwriting the old value. How do we keep the old value and add a new value, WITHOUT having to first lookup what values currently exist?Ideally, as customers enter different promotions, we can just keep adding new values to the promotion_id field. However, after reading through the API docs, it appears we have to first look up the user to see what values already exist for the promotion_ID field, and pass all the values through? Is there anyway around this to not have to make that extra API call?

2
Kim Strauch
Klaviyo Employee
7 months ago
V
Contributor I
viralsweep1Contributor I
asked in SMS

SMS Consent via API not working for Australia

Hello,We have a client in Australia whose Klaviyo account is approved for use with SMS. In addition, they already have a ton of customers listed in their account with SMS consent. We are passing users with Australian phone numbers to their account, but the SMS Consent is not showing up in Klaviyo for these users. We tested this with our USA customers, and SMS consent shows up just fine. We are making the same exact API call in both cases, but for this Australian customer it is not working. Array( [api_key] => pk_***************** [profiles] => Array ( [0] => Array ( [first_name] => Jacob [last_name] => Smith [source] => viralsweep [refer_link] => [source_name] => [email] => jacob@email.com [$consent] => Array ( [0] => email

1
David To
Klaviyo Employee
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.