Learnings from someone who has already made all of the mistakes
Posted: Sun Dec 22, 2024 10:20 am
I'll be upfront about this, I've learnt the hard way when it comes to this development business.
I've spent long nights trying to work out why the hell a bit of code isn't working, only to find out it's a weird Pardot quirk or it was in a place Pardot didn't like.
So, to save you some time, I'll write my top tips below:
If you're using a custom font in an email, use phone line in cambodia the @import method. DO NOT USE the link href= method. Why? Because otherwise, it will trigger a link click once you've sent the email and it will really skew reporting.
Utilise the different Pardot content regions available to you. Marketers don't like code and I don't blame them, so make their life easier by locking down parts that don't need to be completely changed. Removing the ability to create a problem essentially removes the problem. More on content regions
When building the template, ensure image regions are set to the width they're supposed to be. If you have a 150px x 150px space, make sure the template automatically keeps the image within that space. Otherwise, users could upload a bigger image and mess with the whole structure of the template. Code with the end-user in mind!
Do not delete files in Pardot that are being used in templates! My best advice here is to use good naming conventions and tag all assets that are being used on a Pardot landing page, form or email. This is because if the file that the asset points to is deleted, it cannot load and will mess up your beautiful, or not so beautiful anymore, template.
Outlook is a *Insert swear word here*. We all know it. So make sure you're testing your emails properly! I mean that, it really is tricky especially when using buttons and tables and even custom fonts. You've got to really make sure you're bulletproof when it comes to Outlook and code with Outlook in mind, your deliverability will thank you for it later.
I've spent long nights trying to work out why the hell a bit of code isn't working, only to find out it's a weird Pardot quirk or it was in a place Pardot didn't like.
So, to save you some time, I'll write my top tips below:
If you're using a custom font in an email, use phone line in cambodia the @import method. DO NOT USE the link href= method. Why? Because otherwise, it will trigger a link click once you've sent the email and it will really skew reporting.
Utilise the different Pardot content regions available to you. Marketers don't like code and I don't blame them, so make their life easier by locking down parts that don't need to be completely changed. Removing the ability to create a problem essentially removes the problem. More on content regions
When building the template, ensure image regions are set to the width they're supposed to be. If you have a 150px x 150px space, make sure the template automatically keeps the image within that space. Otherwise, users could upload a bigger image and mess with the whole structure of the template. Code with the end-user in mind!
Do not delete files in Pardot that are being used in templates! My best advice here is to use good naming conventions and tag all assets that are being used on a Pardot landing page, form or email. This is because if the file that the asset points to is deleted, it cannot load and will mess up your beautiful, or not so beautiful anymore, template.
Outlook is a *Insert swear word here*. We all know it. So make sure you're testing your emails properly! I mean that, it really is tricky especially when using buttons and tables and even custom fonts. You've got to really make sure you're bulletproof when it comes to Outlook and code with Outlook in mind, your deliverability will thank you for it later.