# Handle Blank Merge Tags in Notification CC & BCCs **URL:** \ **Category:** Feature Requests\ **Tags:** notifications, merge-tags\ **Created:** [August 26, 2019, 4:16pm UTC](https://community.gravityforms.com/t/handle-blank-merge-tags-in-notification-cc-bccs/2553 "2019-08-26T16:16:52Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![lonepc](https://avatars.discourse-cdn.com/v4/letter/l/3ec8ea/32.png) [@lonepc](https://community.gravityforms.com/u/lonepc)\ **Post date:** [August 26, 2019, 4:16pm UTC](https://community.gravityforms.com/t/handle-blank-merge-tags-in-notification-cc-bccs/2553/1 "2019-08-26T16:16:52Z")
The current recommendation is to use multiple notifications and conditional logic or ensuring that all fields that have merge tags in the send to, bcc, or cc settings are set to required. I think it would be much more intuitive (and you wouldn’t need to maintain 2 separate notifications) if GravityForms could handle the following in the TO, BCC or CC field: [test@test.com](mailto:test@test.com),{MergeTag} where {MergeTag} may be blank. ---
**Author:** ![chrishajer](https://sea2.discourse-cdn.com/flex020/user_avatar/community.gravityforms.com/chrishajer/32/88_2.png) [@chrishajer](https://community.gravityforms.com/u/chrishajer)\ **Post date:** [August 26, 2019, 7:13pm UTC](https://community.gravityforms.com/t/handle-blank-merge-tags-in-notification-cc-bccs/2553/2 "2019-08-26T19:13:03Z")
Thank you for the comments. This is on our list of requested features. I will add your vote. ---
**Author:** ![richardw8k](https://sea2.discourse-cdn.com/flex020/user_avatar/community.gravityforms.com/richardw8k/32/2354_2.png) [@richardw8k](https://community.gravityforms.com/u/richardw8k)\ **Post date:** [July 29, 2021, 1:58pm UTC](https://community.gravityforms.com/t/handle-blank-merge-tags-in-notification-cc-bccs/2553/3 "2021-07-29T13:58:36Z")