Some customers have reported an issue where outside fonts are being counted as clicks in Pardot and some other applications. Why? What can be done about it?
If this sounds like the problem you might be having, read on.
There are two ways to import custom fonts in HTML files: one is via a specific
<link> HTML tag, the other is with via a
@import CSS directive.
The BEE editor uses the first method as we have found that it grants broader compatibility with email clients.
Unfortunately, there are applications - like Pardot - that have decided to track the loading of the custom font as a click in the email: this creates conflicts and alters the results of your email campaign statistics.
We have tried to contact Pardot to alert them about this unusual behavior, but until now they have not been available to discuss the matter with us.
On our side, we plan to run a new analysis of whether or not changing the custom font importing method still creates rendering issues with some email clients.
In the meantime, we can suggest a manual workaround that will help when using BEE-designed emails with Pardot and other applications.
Here's the procedure:
- Download the HTML or ZIP file from BEE Free or your BEE Pro account
- Open index.html and locate the line in which the <link> tag with the font is located (usually around line 14). Example for "Montserrat" font:
<link href="https://fonts.googleapis.com/css?family=Montserrat" rel="stylesheet" type="text/css" />
- Delete that line and insert the following code block:
Save your HTML file and import it into Pardot.
This should solve your issue.
In the meantime, we encourage you to notify Pardot's customer support about this issue as we believe that they could address the problem on their side, and there are many companies designing email templates with BEE and then using them in Pardot. :-)