Creating dynamic content rule in delivery with first...

[George-CT5]

Hi all,

I'm looking to create a dynamic content rule targeting those who have a first name that is more than characters long.

I have done this in JavaScript in a segmentation node to give them a separate delivery, but I want to do it within the same delivery.

JavaScript used in segmentation node: Length(@firstName)>2

Does anyone know how to apply this rule within delivery dynamic content?

Thanks,

George

[anasso83525035]

Hello @George-CT5,

There are two ways to do this depending on your end goal :

• If the difference in content is just a greeting sentence you may want to use a content block and do your JS conditions in it directly.

• If the content difference is significant you should go with dynamic content directly in your delivery by leveraging the segment codes in your split activity :

Hope this is clear enough.

[shelly-goel]

@George-CT5

There's also a possibility to use advanced mode in dynamic condition where you can enter the length condition (as not available in basic mode) like context.profile.firstName.length > 2. If you have simple content display condition based on length you might also want to try out with "Visibility Condition". Refer this for detailed steps.

[George-CT5]

Hi Shelly, the rule seems to have worked, but it also displays a lot of code above the fragment that has the dynamic rule. Image attached. Do you know how this can be deleted?

[shelly-goel]

Screenshot would definitely help to understand the issue better, you might not be able to add it while adding the comment but you can edit the comment and then add it. You might want to look at the source in the designer and try removing the extra code from there

[George-CT5]

Thanks Shelly. I have updated my previous comment.

[shelly-goel]

This looks like some syntax error in content (missing open or close tag). You can click on <> to see source and check the syntax. Does it go away if you remove the advanced condition?

[George-CT5]

Hi Shelly, no the error still stays there now. I'm assuming this is because it doesn't understand the advanced method.

[shelly-goel]

I don't think it's related to advanced mode. It this text stays after removing the advanced condition, it could be something else. From the image it looks like you've combined the length > 2 with !== '' which seems to be creating the issue.

[George-CT5]

I'll take a look. Thank you!

[Sukrity_Wadhwa]

Hi @George-CT5,

Were you able to resolve this query or do you still need more help here? Do let us know.

Thanks!

[George-CT5]

The answers provided haven't helped me resolve the issue, but I'm happy to leave this question and continue using the way we used before as we know this works. Thanks.

[Sukrity_Wadhwa]

Okay. Thanks for the update!