@GeorgeVi2  - you should also take a look at recent improvements that provide the ability to set global variables in expression fragments that can be replaced easily: Customizable fragments | Adobe Journey Optimizer

@Hurston - the links you are talking about are they specific to an individual profile? or are the 1:Many. If they are one to many, then using global variables and expression fragments could be a great way to update. In this case, you would have your email template set with variables like  {{primaryC...

Hi @ShashiCh this is coming in a feature to be released this year. We will have the ability to create conditional rules for the email execution field at the channel surface / configuration level. 

Additional updates to decisioning are forthcoming to better support all AJO channels. 

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" %}!