Category: Technical

Pardot now allows SSL-enabled URLS – but use with caution!

You can now make your Pardot assets secure with an SSL certificate – which means your content can be hosted on https urls. This long awaited feature is good news for your search rankings as this has become an important indicator for Google to confirm whether content is secure for their users.

Continue reading “Pardot now allows SSL-enabled URLS – but use with caution!”

Patterns in Apex: Dependency Injection, Strategy, and Decorator

When you start out in Salesforce development, there seems to be little need for software design patterns. Perhaps because development starts with little triggers doing this and that in a few lines of code. But, as soon as the requirements, codebase, and team-size grow, then the advantages of patterns and other software engineering practices kick in. Continue reading “Patterns in Apex: Dependency Injection, Strategy, and Decorator”

New Pardot feature: SSL for Pardot Vanity URLs announced

With web security becoming an increasingly important trend, and browsers including Google Chrome clearly flagging mixed content to users, one of the most frequent feature requests for Pardot was enabling SSL for Pardot vanity URLs.

Previously, Pardot only had an SSL certificate for the go.pardot.com URL, meaning that it was unable to support HTTPS in vanity domain URLs. For HTTPS websites, Pardot administrators needed to use the go.pardot.com URLs when embedding forms and other Pardot content to avoid prospects seeing a warning message.

Pardot has recently announced in the success community that SSL for vanity domains will be available from February 1st, and some customers have started to see this functionality appear in their account this week.

With the release just around the corner, we are awaiting the documentation from Pardot in terms of the specific technical information, then we will provide a more detailed overview.

 

I am pleased to announce that this feature finally has a release date! SSL for Vanity Domains will be available to *all* Pardot customers on February 1, 2018. Thank you for your patience through the long wait for this delivery. Keep an eye out for a blog post for more information.

What Does Apple’s New Cookie Change Up Mean for Pardot Users?

Apple’s new ‘Intelligent Tracking Prevention’ means that the first-party cookies used by Pardot will be deleted after 30 days of prospect inactivity in Safari 11. This is going to impact your ability to track visitors on Apple devices who visit your website less than once per month.

The first thing you should do is to check Google Analytics to see what percent of your visitors are Safari users. Typically this will be a higher rate for mobile than desktop visitors. If this percentage is significant enough to cause concern, the article below suggests increasing the frequency of your content and emails to more than once per month to keep visitors coming back to your site and keep their cookies active.

If all else fails and a significant proportion of your Safari audience let their cookies expire, do remember that any prospect re-visiting your site from a Pardot tracked email will be automatically re-cookied, and you can also use the Pardot forms on your website to re-cookie existing prospects in addition to new prospects.

 

What is Apple changing about cookies?
In Safari 11, which is included as the default browser on the new macOS High Sierra, Apple is saying “we’re watching our figure, please hold the cookies.”  

They’re calling it “Intelligent Tracking Prevention,” and long story short, they’re deleting 3rd party cookies after 24 hours, and they’re deleting 1st party cookies after 30 days.