Topics started by tmchow-bc

2 Topics

T
Contributor I
tmchow-bcContributor I
asked in Lists, Segments, and Profiles

How do I get a "manage preferences" link for inclusion in our product?

Since Klaviyo is the source of truth whether a user is subscribed or not, we want to provide a link from our web app to the preferences for that user on klaviyo’s side.  However, for the life of me, I cannot find a link for this. I expected some global link where we pass in a URL encoded email address or user ID. In email campaigns you create within klaviyo, you can use the syntax `{% manage_preferences %}` or `{% manage_preferences_link %}`, Unfortunately that link looks dynamic and not consistent even for a given user. I found a year old post that seems to indicate this is only possible with HOSTED pages:https://community.klaviyo.com/lists-segments-and-profiles-35/is-there-a-way-to-change-default-link-for-manage-preferences-tag-6569?postid=26616#post26616 However, this seems crazy to require a full blown custom page for this scenario. If that is true, I also cannot find good boiler plate code to use to create a reasonably good preferences page. I’d settle for just re-creating the def

5
kaila.lawrence
Community Manager
1 month ago
T
Contributor I
tmchow-bcContributor I
asked in Email Templates and Coupons

Multiple variables fallback in personalization not working

I found this article:https://help.klaviyo.com/hc/en-us/articles/4408802648731This syntax is super bizarre, but setting that aside, it which indicates a way to not only use nested variables, but to then have multiple fallbacks it seems.Assume I have a 2 user profile properties, one is nested and other is not:"Custom Domains": { "Enabled": true, "Url": "foo.com"},"Shop Url": "bar.com"However, i’m having problem with these personalization templating:{{ person|lookup:"Custom Domain"|lookup:"Enabled"|default:"not found"}}{{ person|lookup:"Custom Domain"|lookup:"Url"|default:"not found" }}{{ person|lookup:"Custom Domain"|lookup:"Url"|person|lookup:"Shop Url"|default:"not found" }}Am I interpreting the docs wrong and we cannot use nested properties?  It’s a total pain to not have the UI expose nested props correctly.

2
T
Contributor I
9 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.