Braze email templates
We have quetions about email templating. 1. Is it possible to validate email templates, for example - check whether certain elements such as Buttons and images have URLs? We are creating content blocks and we want to make sure they contain expected value types. 2. How to prevent changing the styles of an element? For example, we create a content block and the editor should not be able to change the typography styles of the content block when he/she imports and uses it. 3. How to disable automatic color inversion for dark mode on Email clients? Our main theme is light and we don't want to customize our email for dark mode. 4. How to achieve "View in Browser" feature? I read a response in FAQ. I would like to understand how we can automate creating web pages from emails. Is there an event we can listen to and make a webpage that can pull Email for us to process and host? 5. How can we pass variables from template to content blocks when content blocks are added via Liquid code? Let's say there is a button block that should render text inside dynamically. We want this text to be passed from its consumer template. 6. How to remove elements such as Button, Text, Image if they don't have data before sending email?Help with darkmode
hi all! I have an image that's a black icon with a transparent background that overlays an off-white background. in dark mode (specifically on gmail ios), the off-white background becomes a darker blue, so it makes the black icon inaccessible. does anybody have any good workarounds? like ways to display a white version of the image only in dark mode? thanks!Determining Engagement Recency
The older I get, the more my definition of "recent" expands. When I talk about something that "just" happened I might mean 2 days ago, or maybe 2 years. I remember being about 10 years old, and laughing when my Nana described an event from 30 years ago as something that occurred "the other day", but now I get how that much time can pass in the blink of an eye (especially because THAT convo feels like it just happened and was now 30 years ago itself. 🥲) As someone who often succumbs to bouts of nostalgia, I understand the inclination to embrace the past. And while it's fun to reminisce, the unfortunate truth is that when it comes to deliverability, we have to face the passage of time and the toll it takes on both people and their email addresses. Since inbox placement is rewarded based on positive engagement, it's important to send to users who interact with your emails, and eventually stop contacting those who don't. When determining who to sunset and who to stay in touch with, weigh what impacts engagement recency for your brand and customers: 🕰️ How & why do subscribers sign up for your emails? Are people opting in because they want your newsletters, or are they being enticed with a special offer? If they want email updates, their interest is likely to last longer than if they initially subscribed because they wanted a quick coupon. Do users go through a confirmed opt-in process (aka double opt-in)? If email addresses are eligible for mailing immediately after signup without verification, pay close attention to their early engagement. Users who do not engage may not be valid or valuable contacts over the longer term, so proceed with caution. ⏰ How often do people receive mail from you? How often do they purchase? The more you send, the more opportunities there are for recipients to engage (or not!). This means that a daily mailer will need a more aggressive sunset policy than a monthly mailer. If you sell cars, you'll want to send less often than a brand selling car insurance or accessories. ⏱️ How varied is the content? Conventional wisdom says that history will repeat itself, buuuut your content probably shouldn't. If your messaging seldom changes, it would be wise to send less often to avoid fatiguing your users. They need a compelling reason to open, click, and convert, and email has come a long way from the full-page ads of the past. Today's subscribers expect unique offers, compelling updates, and valuable product info. As users become familiar with monotonous messages, their engagement will become a thing of the past. ⌚ What about alternate channel engagement? SMS, push, and in-app messaging can work well in tandem with, or as an alternative to email, but engagement isn't universal. Mailbox providers can't see how users engage with your brand outside of email, meaning that someone who actively visits your site and logs into your app can still negatively impact your sender reputation if they're not interacting with your emails.
Sending out Mails without Product if matching doesn't work in Catalog Collection
Hi, we send out emails with product suggetions to customers, but sometimes the data in the attributes doesn't match the data in our catalog. If that happens the user gets an email without content. Is there a way to send out the back up products if the data cannot be matched (besides fixing the data problem obviously)?Selections: Advanced
Hi there, I am creating some selections on my catalogs. I noticed that you can only pick EQUALS or DO NOT EQUAL as the criteria. This seems very very limited. Is there a workaround that I can add "contains"? Or is there any plans to change this? For instance, I would like to say voucher_id (ad_fr_1234 or ad_de_1234 or ad_es_1234) CONTAINS language (fr, de, es). Right now I don't have a language/country column but the info is within other columns at the moment. Another thing I would like to have start_date (2023-12-03T23:00:00Z) is todays date. Since the format of my date (2023-12-03T23:00:00Z) includes the time, I don't really know how to do this. I would have done: start_date CONTAINS {% assign date = "now" | date: "%Y-%m-%d"%} {{ date }} But the time is an issue. And of course I can't see "CONTAINS" as an option. A workaround could be compare the first 10 character (2023-12-03 T23:00:00Z ) to {% assign date = "now" | date: "%Y-%m-%d"%} {{ date }} but I'm not sure how to do that either?
Canvas error - action path/event properties
Hi all, I'm trying to add a reminder email to an existing Canvas. However, it gives me this error no matter what I do. I've tried adding another action path before the reminder email and also referencing the event property again in the targeting, but no luck. Anyone have an idea?
