Replies posted by TheSuburbs

6 Replies

T
Problem Solver I
TheSuburbsProblem Solver I
asked in SMS

Collecting SMS consent with Client Subscription API

Thanks Omar, I’m in need to a client  side subscription so I couldn’t use the ‘subscribe profiles API.However, upon further testing, simply including a phone number with the Client API seems enough to be provide consent, no need for a specific ‘subscriptions’ object in the data

3
Omar
Partner - Platinum
5 months ago
T
Problem Solver I
TheSuburbsProblem Solver I
asked in Email Templates and Coupons

Access Shopify {{ gift_card }} object

Thanks @Global_sale1 . I understand how to view and use Gift Cards in Shopify. But what I’m after is a way to add Gift Card data into a Klaviyo email/flow.For example, if someone buys a gift card, I want to send them an email through Klaviyo with the code {{ gift_card.code }}, or at the very least a link to the code {{ gift_card.url }}

3
alex.hong
2 years ago
T
Problem Solver I
TheSuburbsProblem Solver I
asked in Sign-up Forms

Collect SMS consent with legacy form

@david.to I’ve just checked the account again and we now have one sms subscriber so it looks like our signup form is working. Thanks everyone for the help!

6
T
Problem Solver I
2 years ago
T
Problem Solver I
TheSuburbsProblem Solver I
asked in Sign-up Forms

Collect SMS consent with legacy form

Thanks for the follow up @david.to . Yes defiantly looks like the double opt-in could be one of the issues here although I’ve just tried turning off double opt-in and retesting but I’m still not having any luck. Also when I export the profile data, it doesn’t include the $consent or sms_consent data objects like when @spacedeveloper exported their data with double opt-in still enabled. So it looks like the SMS data isn’t being saved to my profile at all: { "object": "person", "id": "01F7VRSXXXXXXCX7APST75HNE", "$address1": "", "$address2": "", "$city": "Los Angeles", "$country": "United States", "$latitude": 34.0544, "$longitude": -118.244, "$region": "California", "$zip": "", "$email": "xxxxxxx@gmail.com", "$first_name": "Test", "$last_name": "Testerson", "$organization": "", "$title": "", "$phone_number": "+11234567890", "$timezone": "America/Los_Angeles", "$id": "", "$source": "Footer", "Shopify Tags": "Kids,Baby,Womens,Homewares", "Accepts Marketing": "true",

6
T
Problem Solver I
2 years ago
T
Problem Solver I
TheSuburbsProblem Solver I
asked in Sign-up Forms

Collect SMS consent with legacy form

Thanks for your help so far @dov.derin — I’ve just tried ‘$phone_number’ in the data object but it still doesn’t seem to be saving the SMS consent. The SMS consent should be displayed below the email address in Channel right? (see screenshot below). It seems both phone_number and $phone_number save the phone number to the Klaviyo property, although when it is saved with $phone_number the number is prefixed with + and the country code.     I’m aware that SMS can only be used on Klaviyo with US numbers so I was wondering if consent could only be gathered from US numbers. But I’ve tested that but still no luck:  

6
T
Problem Solver I
2 years ago
T
Problem Solver I
TheSuburbsProblem Solver I
asked in Email Templates and Coupons

Customizing product data feed

Thanks for the help so far @dov.derin . I think the Klaviyo Product feed would be preferable over a web feed so we can show products relevant to the customer. So the question would be how do we access that feed data in a table. That article you’ve referenced is related to the flow event data, but I’m not sure how to pull a product feed’s data into the table? Also the feed preview seems to only be available on web feeds. The Klaviyo Product feed only has the option to edit (no preview) so if I was able to use the product feed in the table, I’m still not sure what data objects the feed contains:  

5
alex.hong
2 years 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.