Preheader Text: Code is pulling in other text into preheader line.

Julia Falk

• May 02, 2023 15:35

I know BeePro added a section to add your Preheader text, however, it's not achieving what I want in the inbox. See the examples below from Linktree, Warby Parker, Bee's Wrap, and Anthropologie. There is a bunch of open space after their preheader text. When I use the BeePro function, it still pulls in the next line of copy from my design, even if my preheader is super short. Does anybody have tips on how to achieve empty space after a short Subject line and preheader?

0

• 

  Roisin Grieco

  • May 03, 2023 07:09

  Hello Julia!

  There is a potential workaround for this I found on Litmus: You can read about it Here.

  However, the code needed in order to accomplish this isn't compatible with the preheader field on the details page in BEE Pro. It appears that you would need to make this change after exporting manually or with your preferred WYSIWYG HTML editor.

  0
• 

  Shane MacNeill

  • November 22, 2023 02:36

  Hello, 

  Are there any other suggestions for fixing this issue? I tried the potential workaround from Litmus. For some reason, the preheader is pulling half of the first sentence.

  Thanks,

  Shane

  0
• 

  Logan

  • November 23, 2023 10:01

  Hi Shane,

  Thanks for reaching out to our community in Beefree; we're happy you're here!

  Regarding your question, regrettably, my colleague Roisin's previous comment and resources provided by Litmus are the most accurate solutions. Because of the limitations in the preheader field within our builder, you won't be able to apply the necessary code to achieve the results without manually exporting the HTML first and modifying it within an external code editor.

  With that said, this updated article from Email on Acid is a great resource on effectively using Preheader Text within your email campaigns, but also how best to optimize your Preheader Text across several email clients. Sadly, character limits vary by the email client, device, and version, so it's a difficult balance between using code to create the suggested workaround and what limitations each mail client may have.

  I'm sorry we don't have a better solution to offer at this time. If you have any follow-up questions, we're always happy to help!

  0

Please sign in to leave a comment.