One thing to keep in mind is that we do not allow for functions or scripting to be added as part of the URL. 

Depends on how you want to use the colors etc. What I have found works really well is to have a list of HTML Hex Colors saved in an expression code fragment. You can then give the colors a variable name so that when you are building your HTML email templates you can replace the color value with the ...

There was some good suggestions below on this thread already, but if you are just worried about triggering the same profile in the same journey within a 24 hr period you can control the Journey re-entrance timing in the Journey properties. This would gate the profile from being able to enter into th...

Yes, you should create a Push template  And in the template set your custom key   Then when someone creates a new Push message they would apply the push template, which will appear in the top right of the content edit screen.    

Take a look at this page on merge policies and see if that helps at all: https://experienceleague.adobe.com/en/docs/experience-platform/profile/merge-policies/overview cc @ShotaId 

@MYSTERIOUSMAN in addition to what was posted above -> if it is a profile attribute the "..." menu will allow you to auto-include a default fallback value  the helper function to include a fallback value for any token:  Hello {%=profile.personalEmail.name.firstName ?: "there" %}! 

Hi @akwankl we are working through planning for this type of schedule grainularity so that the need for expressions will no longer be required. 

@Caveman77  we have plans to bring this into the product soon! You'll have the ability within the surface configraiton to create dynamic expressions i.e. if salesRepID is listed on the profile use salesRep email for the reply-to address, else fallback to default reply-to address. 

Would be great to understand if you are looking to globally prioritize channels i.e. Email first, Push, SMS etc. or if you have a method where you are setting a customer's preferred channel.  We do have some roadmap items coming to help address this. 

I'm not sure i properly understand your usage here. Is the attribute coming from an event payload? Why is the name not part of that payload directly?