Add button in email that has dynamic URL connected, based on Custom property

Hi David,

I have done something similar to this, but with a key difference, and it doesn’t seem to work. I’m looking for guidance. 

Essentially, I am bringing in a unique URL via Make.com, and adding it as a custom attribute. The issue is, I only want the part of the URL that makes it unique - it’s a type of user ID. I want to use that ID in a url. 

So at the moment, I’ve created this:

https://subscribe.transistor.fm/{{ person.Feed_URL | cut:"https://subscribers.transistor.fm/"}}/listen/7917102f

But while it works when text only, it doesn’t work as an href in a button, for example. The result in a button would be https://subscribe.transistor.fm//listen/7917102f as opposed to, for example, https://subscribe.transistor.fm/bfe3b5d9439db3/listen/7917102f.

I’ve only started using Klaviyo in the last few days, so I don’t know if I am missing something simple!

Thanks,

James

@David To to add to the above, this is the link i’m being sent to when I click a button using the above:

https://subscribe.transistor.fm/%7B%7B%20person%7Clookup:'Feed_URL'%20%7C%20cut:

 

Hey @JamesW,

Without knowing the fully story of how you’re passing this data to Klaviyo and how things are setup, it’s a bit hard to grasp. However, reading into your explanation, it appears there may be some encoding occurring that’s causing your URL to break - “%20” typically represents a space in an encoded URL. 

Therefore, this sounds like how the data is being passed and recorded within Klaviyo may not be fully set up correctly. 

If the only dynamic aspect you would need for a URL is the user ID, I’d also be curious to understand why you aren’t just passing and storing just the user ID as a custom profile property. This way instead of needing to use a cut| function, you could simply use something such as: https://subscribe.transistor.fm/{{ person|lookup:'user_id' }}/listen/7917102f

Along the same train of thought, since it seems like the dynamic URL inclusive of the user ID is already built out in your backend with the exception of the static ending (/listen/7917102f), I’d imagine you could potentially manipulate the data in the backend to be inclusive of this data when being passed to Klaviyo.This way, instead of having to build the dynamic URL you were looking for, you can just use a single variable to reference it similar to the solution I posed.

Overall, it seems to me that there may be something going on with your backend on how this data is being passed to Klaviyo that is causing the issue. I would recommend further working with your developer to review how this data is being synced back to Klaviyo as well as seeing if manipulating the data before it's shared to Klaviyo would make more sense. 

David