Create a typology rule which will be helpful to check whether the content exists or not in the delivery before sending. Configure it like the delivery won't go out if the content is not exist in the delivery (same like subject validation).
Better to check the content of the delivery by sending proofs. Once everything looks good and met the criteria later you can send mail.
Thanks for your input! But we are thinking of not to have any kind of proof check here .
Let me give you context, Content is coming from AEM. There are 10 query builder components in the AEM Email template. If any one of the component gives 0 results, we should not send email from Campaign. We already implemented functionality of hiding a component whenever it gives 0 results in AEM. But when it is synced to campaign, it doesn't understand it as component specific instead it considers it as just plain HTML.
Since the template is getting synced at the time of execution, i want to make campaign understand that it should not send out any email in the above scenario
PS: I can check for content is empty or not. But along with dynamic content, there is a static content too.