How to be Successful with the Pardot Drag-and-Drop Landing Page Builder

In the Salesforce Winter ’22 release, Pardot launched the new drag-and-drop Landing Page builder, which allows users to create nativey responsive landing pages and control when pages are published and/or removed. This builder uses the same integration as the drag-and-drop email content builder, so if you are already using that feature there is nothing new to set up!

This post will cover a few things you can do to ensure your users are successful with this new builder. For a great demo of this new feature, check out the Pardot Release Readiness Winter ’22 Webinar (The landing page builder demo starts around the 14-minute mark).

Requirements and System Usage

Before you get started with the landing page builder, you’ll need to ensure:

You’ll also want to take a look at your landing page usage and limit. Landing pages published with the new drag-and-drop experience plus landing pages published with the classic experience will both count toward your account’s limit. 

To check your usage and limit, navigate to Pardot Settings > Usage and Limits

pardot landing page builder

Ensure consistent use of naming conventions

Good naming conventions are going to be especially helpful when using this new builder. Naming conventions will allow users to quickly and easily locate the correct campaign, images, and form while building a new landing page. 

If you are using multiple Pardot Business Units (PBU) it will be even more important to have good naming conventions. When you create a new landing page, you will need to associate it with a connected campaign. The campaign you select determines which PBU the landing page belongs to as well as which forms can be used on this landing page (the landing page can only use Pardot forms that exist in the same PBU as the page). To make sure your users can determine which PBU a campaign or asset belongs to at a glance, I highly recommend adding your PBU name to the naming convention. 

To ensure naming conventions are used correctly on Salesforce Campaigns, check out our previous blog post on how to automate Salesforce Campaign Naming Conventions.

Vanity URLs

You’ll also want to make sure you have a good policy around using vanity URLs and ensure your users know how to check if a vanity URL is already in use before attempting to publish their new landing page. Vanity URLs are not validated until the landing page is published, meaning a team may center their marketing materials around the URL being www.sercante.com/really-cool-awesome-stuff only to find out upon publishing that this URL is already in use for another marketing initiative. More considerations for vanity URLs can be found here

Salesforce Navigation and Page Layout Edits

Make sure your users know where to find this new feature by adding the Landing Page tab to the Pardot Lightning App navigation.

  1. Navigate to Setup >  App Manager
  2. Locate the Pardot app (ensure the App Type says “Lightning”)
lightning experience app manager
  1. Select the dropdown arrow and click Edit
  2. Select Navigation Items
  3. Move Landing Pages over to the Selected Items pane, click Save
navigation items - landing pages

Also edit your Landing Page layouts to include the new Publication Details section:

example landing page

You can edit this page layout by navigating to Setup > Object Manager > Landing Page > Page Layouts

Create New Landing Page List Views

With more granular control over when Pardot Landing Pages are published and unpublished, as well as additional tracking of changes, creating a few list views will help you easily audit your pages. 

You can create new landing page list views by navigating to Landing Pages, clicking the Action wheel, and then New.

all landing pages

Configure a “Published Landing Page” view to keep an eye on metrics

  • This view is filtered to only show “Status equals Published”
published landing pages

Configure a “In Progress Landing Pages” view to monitor which pages are unpublished but in progress:

in progress landing pages
  • The “Content Last Saved” fields are updated anytime the landing page name, campaign, content, search engine indexing, and/or vanity URL are changed. Publishing and unpublishing a landing page does not update these fields.
  • This view is filtered to only show “Status equals Draft”

Finally, configure a list view of landing pages that have a status of “Published (Changes Pending).” Unlike the classic landing page builder, new and updated pages will need to be pushed to “published” when they are complete. Landing pages will not auto-publish upon saving. This new change in functionality may cause some users to leave their page in the “Published (Changes Pending)” state and a list view can help you keep on eye out for these. 

For this list view, clone your “In Progress Landing Pages” view but change the filter to only show “Status equals Published (Changes Pending)”

published pending landing pages

Automate Reminders to Publish

Since users will need to publish landing pages when changes are made, you can set up a flow to remind landing page owners that their pages are not published. I set this up with a flow. My flow looks for landing pages with a status of “Published (Changes Pending)” and a Content Last Saved date of three days ago or less. My Flow will send an email reminder to the user who last updated the landing page for up to three days after their edits were made (unless the page is published). 

automate reminders to publish landing pages

What excites you about the new Pardot Landing Page builder? Tell us in the comments!

The post How to be Successful with the Pardot Drag-and-Drop Landing Page Builder appeared first on The Spot For Pardot.

By |2021-10-22T11:01:21+00:00October 22nd, 2021|Categories: Content Marketing, Design, Release Notes, Salesforce|

Marketing Hocus Pocus: 6 Pardot Horror Stories to Avoid

The life of a marketing and sales consultant is never boring at Sercante, working with companies of all shapes and sizes on tasks both large and small.

The days flow along in a sensible cadence … until …

Are you a Halloween horror story fan?

Marketing has its own kind of terror — not in the chainsaw/demonic way, but on the topics of spam, user roles, missing form follow-up, sync mishaps — you get the picture.

Read on — if you dare! (But really, you should — you’ll learn a few tricks.)

Avoid these 6 Pardot horror stories

marketing horror story 1

Soothsayer Sales Team?

Picture this: You’ve placed a clean and crisp “contact us” form on your website. It’s nice and trim (not too many fields) and has prominent placement on a main page. The sales team is rubbing their hands together in anticipation of ALL of the leads.

Your worst fears come true: The sales team gets nothing, zilch, nada, zero — NO leads.  😱

You frantically look around for the culprit. Finally, the ugly truth bubbles to the surface: The beautiful “contact us” form is missing a critical step. (Are you hearing the “Psycho” sound? I am.)

Pardot Horror Story 1: An inspection reveals that form completions aren’t being assigned or sending notifications to the sales team.

🤦 Of course. The sales team doesn’t have a crystal ball and can’t “see” the leads without a little form-based action.

It’s time for you to optimize your form setup so leads make it to the right people.

Read this post for more details »

marketing horror story 2

Ghostly Links

Your day starts with an urgent note from your boss: “An email must be sent asap on ProductX because sales numbers aren’t as expected.”

Between back-to-back calls and a multitude of Slack messages, you prep the email, to get it ready for the final copy you are not-so-patiently awaiting. The copy arrives,and you review it while on yet another call, then drop it into the email you already started. Cool. Looks good 👍.

You send a test to the boss, copywriter and your own inbox, and review the test email while still on a call (you are crushing the multi-tasking game 💪).

You wait for approvals, then wait some more, and finally message your boss (“Please respond so I can get the email out!”). He comes back with a not-so-convincing “Yeah, it’s fine — send it” (and you never hear back from the copywriter).

You hit the “send” button — “asap” as requested — unaware of the horror to come.

Ding! The email hits your inbox. Ding! Ding! Emails from coworkers: “The button doesn’t work.” Uh-oh.

While distractedly rushing to get the email done, the link in the CTA button was forgotten.

Pardot Horror Story 2: Everyone’s messaging you to say your CTA button leads nowhere because it’s a dead link 😱.

Anyone in charge of sending emails has been there — I feel you. It’s easy to miss test-clicking a link. And, as we all know, a rushed task is an invitation for errors.

Implementing a better quality assurance process can help you feel confident the next time you hit the ‘send’ button.

Read this post for more details »

marketing horror story 3

The WitchWhich List Mystery

One day your database size is X, the next day it is X+5000! Where did the extra records come from? Magic? Sorcery? 🧹

You dig around, looking at new records trying to find the answer.

Hmmm — you see a few imports that you did not perform. Only one other user has import access — your boss. You message her: “Hey, I see you imported some lists into Pardot. Can you tell me where they are from?” She proudly comes back with, “We purchased a few small opt-in lists!”

Oh boy.

Pardot Horror Story 3: You find out that the zombie prospects in your Pardot org came from purchased lists.

Say it with me now: “Purchased lists are noncompliant with Pardot.”

Seriously, Pardot will put a hex on your account if you use those purchased prospects. Don’t do it. Just don’t.

(Learn more about Pardot’s Permission-Based Marketing Policy – which, by the way, you must agree to EVERY time you import a list!)

Read this post for more details »

marketing horror story 4

Zombie Admins

There are four default Pardot user roles defined by their level of access/ability (Administrator, Marketing, Sales Manager, and Sales).

Salesforce user profiles are mapped to Pardot user roles.

You’re with me, right? Great.

According to the Thesaurus, “administrator” is also authority, commander, head, official, head honcho. You would probably agree that this would be a title reserved for the very top-most spots (I’m thinking 1-5, depending on how large the organization is).

How about 31,634 users with the Administrator role 😲.

Yes, we’ve actually seen that IRL (this sounds like a Farmers Insurance® ad).

Pardot Horror Story 4: You discover that most of the users in a Pardot org have Administrator user roles.

🧟‍♂️ Keep the zombies at bay: Be selective with assignments to the Pardot Administrator role!

With admin access comes great power. Determine who really needs full access to everything in Pardot when assigning this role.

marketing horror story 5

Marketing-Killer Troll

Once upon a time, ABC Company sent out emails marketing its products and services to an opt-in list. People on the list were not a match for ABC Company, so they opted OUT of receiving emails.

Seeing this made ABC Company very angry, so they consulted the Troll living in the basement. Smashing his club into the ground, Troll decided these people MUST receive the emails 👹.

Every email was then sent as an operational email. Every. Single. One.

Who knows where this story is going? 🙋‍♀️

An operational email is just that: operational. As in: service announcements, transactional messages, legal notices. As in: NOT marketing.

If you send an operational email and it does contain marketing information, then it is SPAM.

Pardot Horror Story 5: A quick check reveals that all emails are being sent as operational emails.

Don’t be a marketing killer, don’t send unsolicited messages and get shut down (or worse).

Read this post for more details »

marketing horror story 6

The Prospect Sync Coffin

Something is killing your synced information. Leads and contacts are dropping like flies directly into the Pardot Recycle Bin ⚰.

No, it’s not the work of a serial killer, but it could be the work of a Marketing Data Sharing mismatch.

Pardot Horror Story 6: You realize prospects are being sent to the recycle bin because of a Marketing Data Sharing (MDS) criteria mismatch.

If you rely on specific data values to control information that syncs from Salesforce to Pardot (leads, contacts, opportunities, custom objects), then you are likely using Marketing Data Sharing (MDS).

When data values change in the field that the MDS criteria is using, the match won’t happen and prospects will be archived. If you import prospects that don’t match the MDS criteria, they’ll automatically be stuffed into the recycle bin too.

Explore the gotchas and learn how to set up MDS in this post »

Marketing Shouldn’t Spark Fear

Your daily life in marketing shouldn’t rival ghost stories or legends of monsters. With proper planning and constant education, it can be a quite happy tale. 

Here are 4 ways to start:

  1. Market with morality.
    • Make sure you understand Pardot’s stance on permission-based marketing.
    • Build a good base of GDPR knowledge.
    • Put yourself in the shoes of your recipients and send helpful email messaging, not spam.
  2. Stay on top of updates and new features.
  3. Always be learning.
    • There is a TON of free content for you to discover, from Trailhead to blogs (like this one!), and more.
    • Bookmark your favorites — or add them as startup tabs in your browser — for easy access.
    • Get certified — Salesforce offers a lengthy list of options.
  4. Join a community

Reach out to the team at Sercante if you need help along the way. Or tells us about your biggest marketing horror story in the comments section… if you dare.

The post Marketing Hocus Pocus: 6 Pardot Horror Stories to Avoid appeared first on The Spot For Pardot.

By |2021-10-20T21:04:32+00:00October 20th, 2021|Categories: Compliance, Content Marketing, Data Management, Email Marketing|

Implementing Pardot External Activities Natively in Salesforce

Pardot is delivering a whole new way to leverage your prospect data in the Salesforce Winter ‘22 release. Our earlier blog post covers this new feature and how to set up the Pardot External Activity in Salesforce so any third-party service can begin sending these activities to Pardot via API. This post explains what third-party services need to do to send these activities to Salesforce using Salesforce declarative solutions (Flow/Process builder). 

At a high level, we need to:

  • Configure Salesforce to allow our solution to call the Pardot API
  • Implement Salesforce APEX code to handle the Pardot API request
  • Add an action to a Flow to make use of our new code
  • Test

This solution is a little more technical than our post on Zapier. Once you are done, you will end up with a Flow like this:

Start Record-triggered flow

Configure Salesforce

Any time we want to work with the Pardot API, we need to “authenticate” with Salesforce in order to get an Access Token. 

First, follow the steps in our earlier blog post Connecting to Pardot API from APEX. By the end, you should have:

  • A brand new Connected App (to avoid issues, don’t re-use previously created Connected Apps unless they were created using the instructions above) 
  • Named Credential for connecting to the API 

Salesforce APEX code

To build this capability, we need to create an @InvocableMethod so that our Salesforce declarative automations can see it and call it to do our bidding.As with any code solution, there are a variety of ways that we can tackle this. The code sample below will work for readers with one Pardot Business Unit. The original code file (and APEX Tests) can be found in our GitHub repository: export-activities-sfdx

public with sharing class PardotExternalActivityPublisher {
    public static final Integer HTTP_REQUESTS_PER_BATCH = 50;
    public static final String ONLY_ONE_BUSINESS_UNIT_ID = '0UvB00000004000AAA';
    public static final String NAMED_CREDENTIAL = 'APEX_Pardot_Credential';

    public class ExternalActivity {
        // @InvocableVariable(label='Business Unit Id')
        // public String businessUnitId;
        @InvocableVariable(label='Extension' required=true)
        public String extension;
        @InvocableVariable(label='Type' required=true)
        public String type;
        @InvocableVariable(label='Value' required=true)
        public String value;
        @InvocableVariable(label='Prospect Email' required=true)
        public String email;
    }

    @InvocableMethod(label='Send Activity to Pardot')
    public static void sendActivityToPardot(List<ExternalActivity> activities) {
        //Very quickly pass this request into the ASYNC Queue, eliminating delays for Users
        System.enqueueJob(new QueueablePardotCall(activities));
    }

    /**
     * Handles Asynchronously firing each Activity to Pardot
     */
    public class QueueablePardotCall implements System.Queueable, Database.AllowsCallouts {
        private List<ExternalActivity> activities;

        public QueueablePardotCall(List<ExternalActivity> activities) {
            this.activities = activities;
        }

        public void execute(System.QueueableContext ctx) {
            //depending on how many Activities we are processing, 
            //we might hit the APEX limit of 100 Web Callouts
            List<ExternalActivity> remainingActivities = new List<ExternalActivity>();
            Integer processedCount = 0;

            for(ExternalActivity activity : activities) {
                if(processedCount < HTTP_REQUESTS_PER_BATCH ) {
                    HttpRequest req = new HttpRequest();
                    req.setHeader('Pardot-Business-Unit-Id', ONLY_ONE_BUSINESS_UNIT_ID);
                    req.setHeader('Content-Type', 'application/json');
                    // req.setHeader('Pardot-Business-Unit-Id', activity.businessUnitId);
                    // activity.businessUnitId=null;

                    req.setEndpoint('callout:'+NAMED_CREDENTIAL+'/v5/external-activities');
                    req.setMethod('POST');
                    String body = System.JSON.serialize(activity, true);
                    System.debug('Submitting: ' + body);
                    req.setBody(body);
                    Http http = new Http();
                    try {
                        http.send(req);
                    }
                    catch(Exception e) {
                        //we fire it off and don't do anything if there's an error
                        //probably not the best approach for Production, though it will
                        //be up to you how to handle it
                        System.debug('There was an error submitting the External activity');
                        System.debug('Message: ' + e.getMessage() + '\n' +
                                        'Cause: ' + e.getCause() + '\n' +
                                        'Stack trace: ' + e.getStackTraceString());
                    }
                    processedCount++;
                }
                else {
                    //we will process this in the next batch of Payloads
                    remainingActivities.add(activity);
                }
            }
            if(!remainingActivities.isEmpty()) {
                System.enqueueJob(new QueueablePardotCall (remainingActivities));
            }
        }
    }
}

To use this code, make sure you replace the Business Unit ID at the top of the code with your Business unit ID (to find this, navigate to Salesforce Setup > Pardot Account Setup).

For readers with multiple Pardot Business Units, remove the constant ONLY_ONE_BUSINESS_UNIT_ID and then uncomment the businessUnit lines throughout. You will need to either specify the Business Unit ID in your Flow, or you could write additional APEX to iterate through your Pardot Business Units by working with the PardotTenant object in Salesforce.

You might also want to specify how you want to handle any exceptions you get from making the Pardot API call. In our example, we simply write exceptions to the debug log.

Our APEX code does assume that the Contact has synced over to Pardot already. If you can’t make this assumption, you may consider calling a Pardot Form Handler to make sure that the prospect is in Pardot already. We have an APEX example for that too (which follows a very similar pattern, so it should be easy to merge them).

Adding an Action to a Flow

Once the APEX has been deployed, you will now be able to use it declaratively.

In our example, we have a Zoom Webinar Member (which is a Junction Object between a Zoom Webinar and a Contact).

To set this up in a Flow:

  1. Navigate to Setup > Flows
  2. Select “New Flow” or edit an existing Flow
  3. Select the + symbol to add a new Element, select “Action”
  4. In the “Search all actions” window, locate “Send Activity to Pardot”
  5. Provide a meaningful Label and Description
  6. Set your input values
    1. Extension: Enter the name of the Marketing App Extension you created in Salesforce
    2. Prospect Email: Source the email from one of the fields/variables in your flow
    3. Type: Enter one of the activities you set up and associated with your Marketing App Extension in Salesforce
    4. Value: Enter (or source from a field/variable) the unique value to identify this Activity, event IDs work great here
  7. Click “Done”
Send activity to pardot

Test

Once all elements of your Flow are ready, testing can begin. Activate your Flow and perform the action you are using to trigger the Flow. After a couple of moments, check the Pardot prospect you are testing with, and you should now see all the information you passed through.

prospect activities

Testing is a little bit tricky, for two reasons:

  1. We are executing this functionality asynchronously, meaning a problem won’t show up in Salesforce like you are used to seeing. Debug logs will be your friend here. But don’t worry, there isn’t too much to sort through.
  2. If the Named Credential or anything else isn’t quite set up right (from step 1), Salesforce and debug logs aren’t very helpful in troubleshooting. You will have to painstakingly go through the instructions again to make sure that nothing was missed / done incorrectly.

Considerations

  • The Export Activity API call only works for known prospects, and it will not work if the email address is not already associated with a prospect in your Pardot Business Unit (this is why we have the form handler in our example).
  • If you have multiple Pardot Business Units, there is no intelligence of “choosing the right one.” You need to target the right one with your APEX solution, which assumes all prospects going through this code are from the same Pardot Business Unit. As we mentioned in the APEX section, you have the flexibility to code whatever you need to handle your business case. 

 For assistance with this or other Pardot External Activities, reach out to Sercante!

The post Implementing Pardot External Activities Natively in Salesforce appeared first on The Spot For Pardot.

Preserving Prospect Email Preferences After the New Pardot Mailability Upgrade

The Salesforce Winter ‘22 release made the Pardot Prospect Mailability upgrade permanent for all orgs. And it also introduced four new user abilities that allow for more control over which Pardot user roles can edit the new Prospect Mailability fields.

New Fields

  1. Update Opted Out Field
    • Allows the user to edit the “Opted Out” field from the Prospect Overview page
    • Replaces “Toggle Opt-In Status” 
  2. Update Do Not Email Field
    • Allows the user to edit the “Do Not Email” field from the Prospect Overview page
  3. Reset soft bounce count
    • Allows the user to reset the soft bounce count for a prospect. When soft bounces are detected, a “reset” option will appear.
  4. Reset hard bounce count
    • Allows the user to reset a hard bounce for a prospect. 

“Update Opted Out Field” will be enabled for the Pardot Administrator role by default. The other three abilities will be enabled for the Administrator role and the Marketing role by default. Users will only be able to manually toggle these abilities on and off within a Custom User Role

When should you reset soft and hard bounces?

You should reset a prospect’s soft or hard bounce if the bounce(s) only resulted from a system issue, such as:

  1. The mailbox is temporarily unavailable or busy
  2. The mailbox is full
  3. An issue similar to when Barracuda incorrectly blocked vendor IPs including Pardot 

If the bounce(s) resulted from the email address not existing, the email or sender being blocked, or due to a bad sending reputation, you should not reset the bounce(s). Continuing to email prospects who have received a hard bounce for these reasons can have a severe impact on your send reputation! You can learn more about bounce codes and meanings here

What to watch out for

Removing a user role’s permission to “Update Do Not Email Field” and/or “Update Opted Out Field” only removes the ability to update these fields on the Prospect Overview page. Users will still be able to edit these fields via Automation Rules, Completion Actions, and Engagement Studio Programs. Due to this, I would highly recommend you read the “Ensure these new features are used correctly” section of our first Mailability Upgrade post as well as Lindsey Mark’s post about how to align your data after the upgrade.

What questions do you have about the new Mailability Upgrade? Tell us in the comments!

The post Preserving Prospect Email Preferences After the New Pardot Mailability Upgrade appeared first on The Spot For Pardot.

By |2021-10-20T18:40:08+00:00October 20th, 2021|Categories: Compliance, Content Marketing, Email Marketing, Pardot Business Units, Release Notes, Salesforce|

How to Audit Dynamic Content and Variable Tag Usage with the Pardot API

By Erin Duncan & Mike Cruezer

Incorporating dynamic content and variable tags is an excellent way to personalize your emails, forms, and landing pages. But viewing where dynamic content and variable tags are in use is a proverbial black hole. 

Not knowing where these items are used makes updating or deleting dynamic content and fields risky. You don’t want to leave a big blank space in an email template or send a prospect an email that says “We would like to offer you              for a limited time.”

Completing an audit can reveal all the places Pardot Variable Tags and Dynamic Content are in use. So, where do you start?

How we completed the Pardot Dynamic Content and Variable Tag audit

To solve this issue, I teamed up with the Pardot API Wizard Mike Creuzer to see what information we can pull via the API. With the API, Creuzer pulled the asset IDs and the full HTML (and TEXT for email templates) from the assets. We then took the raw data and looked for anything containing “%%” (or “{{“ if you are using HML). The end result being a giant Excel sheet like this:

Pardot Dynamic Content and Variable Tag audit

Using skills from the Excel for Pardot Admins mini-series, we then split this list out into one master list of all Pardot Dynamic Content and Variable Tags present in any assets. This allowed us to not only view which dynamic content assets are more frequently used, but also ensure we would not break any personalization in our assets while altering or deleting fields and content.

Getting Technical with Ad Hoc Reporting in Pardot

To get the data in the format above, we used the typical computer science ETL (Extract, Transform, Load) pattern at a smaller scale.

Extract

In this scenario, we had to go beyond what a typical Pardot export would get us, so we turned to the Pardot API. Using the API we pulled the full HTML and TEXT from all unarchived email templates in the Pardot instance. 

If you are new to using the Pardot API, you can shorten your ramp-up time with the Postman Collection for the Pardot API from Sercante Labs.

Transform

We used a regular expression to pull only the HML, PML, and dynamic content merge fields. This allows us to quickly skim the HTML and TEXT of our email templates and identify where dynamic content and/or variable tags are in use. We effectively tossed away all the other ‘stuff’ in the emails to focus on just the needed bits.


Load

“Load” means getting the data to its final destination. In our case, the destination is a shareable and usable spreadsheet. 

We included useful fields within our spreadsheet for people who are doing the dynamic content and variable tag review (i.e. template name, Pardot business unit, etc.). And there are seemingly useless bits like the template ID, which anyone can easily use to create a direct link to the template for editing. 

We also built in additional features, such as flagging when a TEXT version of an email is blank or where an @ symbol was used before %%current_year)yyyy% instead of ©. Finally, we pulled this process together in a programmed script to allow us to easily re-pull the data after dynamic content and fields were deleted, thus ensuring no tags were missed.

Audit your Pardot Dynamic Content and Variable Tags, and tell us how you did

With toolsets like this at your disposal, you can quickly and accurately get more work done. It’s easy to expand this process into other use cases after you’ve completed the process once or twice. For example, you can look for variable tags within dynamic content. 

What Pardot data would you like to audit with a process like this? Tell us in the comments!And remember to reach out to the Sercante team when the challenge calls for Pardot experts.

The post How to Audit Dynamic Content and Variable Tag Usage with the Pardot API appeared first on The Spot For Pardot.

By |2021-08-24T19:39:41+00:00August 24th, 2021|Categories: Content Marketing, Design, Email Marketing, Experiments, Integration|

Four big Salesforce Winter ‘22 Pardot highlights

It’s time to prepare for the Salesforce Winter ‘22 Release and how it will affect your Pardot instance.

We get three major releases from Salesforce each year — Spring, Summer and Winter. Each Salesforce release includes upgrades and enhancements that affect Salesforce orgs in different ways. 

So, if you’re using and managing Pardot for your company or organization, then you’re in the right place. We’re going to cover everything you need to know about the Salesforce Winter ‘22 Release for Pardot admins and users.

Salesforce Winter ‘22 Release Dates

Here are the Salesforce Winter ‘22 Release dates:

  • August 12, 2021: Pre-release org signup
  • August 16, 2021: Release notes available
  • August 27, 2021: Sandbox preview starts, release site available, and release Trailhead module launches
  • August 30, 2021: Release overview deck and feature matrix available
  • September 10, 2021: Release weekend
  • October 1, 2021: Release weekend
  • October 8, 2021: Release weekend
  • September 10-17, 2021: Release Readiness Live

Salesforce Winter ’22 Release: 4 Highlights for Pardot users and admins

Pardot users and admins are getting lots of attention from the Salesforce Winter ‘22 Release. Some updates are changing the way we work to meet evolving technology demands. Others are saving us time by connecting the dots in a logical way. All we know is, this release includes big updates for people in the sales and marketing world.

Highlight 1: Salesforce My Domain requirement

A Winter ‘22 release update has the potential to create chaos for companies that want to use branded domain names.

The Salesforce Winter ‘22 release will require all orgs to have a My Domain.

That means Pardot orgs that aren’t already configured for My Domain will get a random Salesforce-picked domain name. My Domain names have to be unique, so you’re outta luck if some other Salesforce customer has yours already.

If you don’t have a My Domain yet — then register your brand name now! You don’t have to deploy My Domain right away, but you can claim your preferred domain name now and deploy later (preferably in a Sandbox).

Salesforce My Domain Example

There’s likely to be a gold rush for domains from now until the first few weeks of the Winter ‘22 release, peaking at release, as folks register My Domains before enforcement or pick new ones after being force-registered.

What you should do: Implement a My Domain if you don’t have one

Here are resources to use when implementing a Salesforce My Domain.

(Thanks to Sercante Salesforce Solution Engineer Hayley Tuller for this one!)

Highlight 2: Pardot Classic App Retirement

Pardot Classic isn’t going away completely. But, the Winter ‘22 release includes a step toward moving in that direction. Salesforce has given soft nudges to customers encouraging them to adopt Lightning for quite some time. With that in mind, the Winter ‘22 release brings the news that Salesforce is retiring the Pardot Classic App after October 17, 2021. 

Current Pardot Classic users can refrain from panicking for now. The Pardot Classic App is a Salesforce page with Pardot on top via iFrame. The Pardot Classic App experience is going away, but you can still access Pardot Classic for now. Salesforce will disable the Pardot Classic App for ALL users on October 17, 2022. After that date, Pardot Classic users will only be able to access Pardot using the standalone Pardot app (available at pi.pardot.com).

Say goodbye to the Pardot Lightning app

What you should do: Start planning for the switch to Pardot Lightning

Salesforce Lightning is here to stay, so expect more pushes toward making the switch if you’re using Pardot Classic.

Here are resources to prepare for switching to Pardot Lightning.

Highlight 3: Pardot marketing asset design capability enhancements

Marketers love drag-and-drop tools like fish love water. Salesforce is opening the doors for more drag-and-drop design functionality in Pardot through a few different enhancements.

Enhancement #1: Pardot drag-and-drop landing page editor

Pardot Lightning users now have the ability to build landing pages faster in Pardot with a user-friendly landing page editor. After you enable the feature, the Pardot drag-and-drop landing page editor allows you to create landing pages from templates or scratch. 

Enhancement #2: Custom components for the email content builder

You currently use standard components when you create emails in Pardot. These are the blocks you use to add elements, like graphics or text boxes, to your email drafts. 

Winter ‘22 brings an enhancement that will open the doors to using custom components in your emails to add fancy features and customizations. 

Enhancement #3: Push emails from Lightning Experience into Engagement Programs

We were all excited to start creating emails in the drag-and-drop editor in Salesforce Lightning Experience. But, we were limited in how we could use those emails.

After Winter ‘22, you can push those emails from Lightning Experience into Pardot Engagement Studio programs. All you have to do is create your emails and activate them for use in automations.

What you should do: Evaluate how your team creates Pardot marketing assets

All of these enhancements to the way marketers build assets in Pardot are meant to make the tool easier to use. It may make sense for your team to adopt them or look toward other options. You can figure that out by evaluating your team’s current process for building marketing assets like landing pages and emails.

Document your team’s current processes and talk to them about what works and doesn’t work well for them. Also, pay attention to how much time they are spending on these tasks so you can determine if it makes sense to invest in upgrades or external resources.

Highlight 4: Extending Pardot through integrations

Salesforce is highly customizable thanks to integrations. And new ways to extend Pardot through integrations are going live all the time.

Here are a few Salesforce Winter ‘22 Release enhancements that use integrations to extend Pardot functionality.

Enhancement #1: Send Slack notifications to Pardot users via completion actions (beta)

Interacting with prospects at the right time and in the right way is key to earning their trust. And now you can enable your sales team to capture those moments even more.

A Winter ‘22 enhancement allows you to set a completion action that notifies Pardot users in Slack when prospects interact with marketing assets. Because the Slack acquisition is still unfolding, this new feature also gives us a glimpse of what’s to come now that Slack is officially under the Salesforce umbrella.

Enhancement #2: New enablement resources and the Pardot API v5

Salesforce developers who work with Pardot will have access to the Pardot API v5 with the Winter ‘22 release. This update also includes super helpful enablement resources for Salesforce developers who are new to working with the Pardot API.

Enhancement #3: Pardot Extensibility Enhancements

You probably use third-party apps all the time for things like webinars and virtual events. But using the data from those third-party apps in Pardot can be difficult without heavy lifting. 

The Salesforce Winter ‘22 Release is opening the doors to capturing and using that third-party data in Pardot. You can now collect prospect data in third-party apps and bring it into Pardot by setting up a Marketing App Extension.  

What you should do: Integration brainstorming session

Have a brainstorming session to discover ways you can use integrations more effectively in your Pardot instance. You can kickstart the session by completing the sentence “wouldn’t it be nice if Pardot…” as many times as you can. Then, rank those sentences you created and focus on the ones that will have the greatest impact on your marketing efforts.

Implementing those integrations you identified through your brainstorming may go beyond your team’s capabilities. If that’s the case, you can reach out to Sercante Labs to find out how you can make it happen.

Pardot is getting bigger and better all the time

B2B marketers who come to Pardot are usually looking to scale their efforts and grow in a way that makes sense. These latest enhancements from the Salesforce Winter ‘22 Release get Pardot marketers closer to those goals by saving them time and resources. 

Adding more user-friendly design capabilities addresses a major pain point for many Pardot customers. And extending Pardot through integrations and feature upgrades is preparing Pardot orgs of all sizes for the future.

Contact the team at Sercante to get help implementing these enhancements in your Salesforce org and Pardot instance. And leave us a comment below to let us know what you think about the Winter ‘22 Release.

The post Four big Salesforce Winter ‘22 Pardot highlights appeared first on The Spot For Pardot.

By |2021-08-18T18:53:52+00:00August 18th, 2021|Categories: Content Marketing, Design, Email Marketing, Integration, Release Notes|

Beyond Dynamic Content: How to Create REAL Content Personalization in Pardot

Dynamic Content is the built-in way to use Pardot to personalize marketing assets like emails. You can improve your email marketing performance, including click-through rates (CTRs), by providing the right content based on known (or unknown) prospect information. 

However, throughout the process, many Pardot users run into limitations of Pardot Dynamic Content. They wonder how they can actually achieve personalization within their Pardot emails and newsletters.

This post will walk you through solutions to overcome common challenges with Pardot Dynamic Content. You’ll also get strategies to expand your personalization options far beyond what it can achieve. 

If you’d like to dive deeper into these strategies, then sign up for FeedOtter’s upcoming webinar on August 19 at 1 p.m. ET. You can ask questions, see tutorials and get free in-depth guides on the more complex strategies just for registering. We look forward to seeing you there! 

You can also catch a session on the topic at ParDreamin’ this year.

Overcoming Limitations of Pardot Dynamic Content

Limitation #1: Only one field criteria

One of the primary limitations of Pardot Dynamic Content is that the criteria can only be based on one field. This can make users feel frustrated when they need to use more complex criteria or multiple fields to determine which piece of content an audience member sees. 

One way around this is to use an automation rule (that embodies multiple criteria) and have it change one field you can then use for dynamic content. 

For example, you might want to send different content to these three audiences:

  • East Coast people who aren’t registered for your webinar (send an invite to your East Coast presentation)
  • West Coast people who aren’t registered for your webinar (send an invite to your West Coast presentation)
  • People who are registered for you webinar (send an eBook)

Because these audiences use multiple criteria (location and registration status in this example), you aren’t able to achieve the goal with dynamic content without some finesse. 

To achieve this, you would need to create a new field. Then you could use an automation rule so that everyone who is on the East Coast and is registered has that prospect field filled with a value that reflects “East Coast + Registered” and then do the same with your other variations.

At the end, you would have one prospect field that takes into account multiple criteria to base dynamic content on. 

Limitation #2: No “is empty” criteria option exists

Another limitation Pardot users run up against with Dynamic Content is the fact that there is no “is empty” option when creating criteria. 

The standard criteria include:

  • Is
  • Is between
  • Is greater than
  • “Contains” (for dropdowns)

Luckily this one is fairly easy to solve. If you go into the Admin section for that specific Dropdown field, you can make sure the blank value is also selected. This will allow you to use “blank” as a criteria option.

Keep in mind that this only works for dropdown field types, so it does not work for all prospect fields. 

Limitation #3: 25 Variation limit 

This limitation is not the most common one for users to come up against, especially when they first start using dynamic content. However, you might see this if you are regularly creating new options for one dropdown field that you then use as a base for your dynamic content.

You can only have 25 variations per dynamic content piece. 

You can work around this a bit by combining Handlebars Merge Language (HML) with your dynamic content. We will discuss HML as another tool for personalization later in the blog post, but it is an option (even if it comes with its own challenges.) 

Other Challenges with Pardot Dynamic Content

However, despite the tricks and tips to get around some of these common limitations, many users still feel that true personalization cannot actually be realized.

Even when criteria options are sufficient, Pardot Dynamic Content has other challenges, such as:

It’s time intensive. 

It takes a while to properly strategize and then set up the custom fields and automations you need to make dynamic content a success. Even once the framework exists, you’ll still need to take the time to reformat your dynamic content modules for each email. 

Once you’ve practiced editing these modules, it probably won’t take as long as it would have to create an entirely separate email, but it is still something to be mindful of.

It’s also prone to errors. 

Dynamic content can be difficult to test, especially if you have a lot of variations. Because it is harder to test, spotting errors can be tricky. 

You also have to keep diligent track of what Pardot Dynamic Content module is the correct one because you insert it with its numeric code — not as an actual block of content. 

Overall, many of the clients I’ve worked with have found Pardot Dynamic Content limiting from the start or they have outgrown it over time. But there are other ways to achieve personalization that are less time intensive, more user-friendly, and more automated. This includes Handlebars Merge Language, Pardot Snippets, and integrations with other software. 

Handlebars Merge Language (HML)

HML was originally the Salesforce version of variable tags. But in 2019, it was brought to Pardot as well. HML allows you to use conditional logic statements in emails and email templates to change what a user sees in an email based on fields. 

HML uses

The benefits to using HML over Pardot Dynamic Content are that you can write the condition you need directly in the email itself. Then you don’t have to recall which specific module you need. It is simply based on your field information, and you can change details within a block of content instead of creating a new block of content for each category.

HML language requires you to code everything, but this does open up design and style options in addition to changing text. With HML, you aren’t limited to what you can paste into Pardot’s Dynamic Content boxes.

The limitations to using HML are:

Technical coding and setup required

Email templates that use HML conditional statements need careful coding of the IF statements. Unlike Pardot Dynamic Content, there is not a simple way to insert conditionals. Everything must be written in HTML and HML code. If you aren’t experienced with writing code in these languages, then you may need outside help. 

Prone to errors

It can be easy to accidentally break the IF conditions or underlying code if you are updating content directly in the Pardot email builder. And as is true with Pardot Dynamic Content, conditional emails are difficult to test before release.

Limited logic

HML logic is not as robust as Pardot Dynamic Content. You can only use “field = true” logic. Most use cases will require the creation of new custom fields and workflows that map preferences to custom fields which you can use in the HML email. However, that is also true of complex Pardot Dynamic Content criteria. 

Pardot Snippets 

Pardot Snippets are static and reusable blocks of text, dates, or links you can use in emails, forms, and landing pages. You will need access to Salesforce (and/or Pardot Lightning) to create them. They are especially useful for helping marketers keep track of information they would normally copy/paste across multiple Pardot assets. Pardot Snippets are most helpful when it comes to updating event information or footers across your various assets. 

There are a few limitations to Pardot Snippets, such as:

They don’t support HTML/CSS

This means you can’t use Pardot Snippets to stylize your email. You can only use them as blocks of text. While this certainly has a time and place, I haven’t seen my consulting clients use this method to achieve advanced personalization. 

Criteria is very limited

The Pardot Snippet criteria is very limited. It is only based on Business Unit or Campaign Ownership. If you need any other logic (which you likely will if you really want to personalize your prospect’s email and newsletter content), then you’ll have to use a different method. 

Emailing Personalized Content Still Takes Time in 2021

No matter which of the Pardot-native personalization methods you choose, you still have to manually copy and paste content into the Pardot builder or Dynamic Content blocks. This pain point is the biggest reason companies shy away from personalizing these days.

If you’ve made it through this post and still want to pursue personalized Pardot emails, then I highly recommend looking for a Pardot add-on that can help you automate the email creation process using RSS or a curation process. Pardot automation add-ons can reduce errors, save you time, and make personalization a more realistic possibility.

You can learn more about personalization that goes beyond Pardot Dynamic Content at ParDreamin’ 2021. We’ll present a session to teach you how to overcome the limitations of dynamic content using powerful Pardot integrations.

View ParDreamin’ session description for Beyond Dynamic Content: How to Create REAL Content Personalization in Pardot

The post Beyond Dynamic Content: How to Create REAL Content Personalization in Pardot appeared first on The Spot For Pardot.

By |2021-08-11T11:06:59+00:00August 11th, 2021|Categories: Content Marketing, Email Marketing|

Work Confidently in Pardot through Quality Assurance Testing

Feel more confident as an admin or end user by kicking ass at Pardot quality assurance testing.

We’ve all been there before. Everything is set up in Pardot for an email or engagement studio program. But the fear hits before clicking the button to launch it. Is everything set up so it tracks correctly? Could there be a typo or broken link somewhere? This is where checklists and quality assurance testing are helpful.

The term ‘quality assurance testing’ makes the process seem more complicated than it needs to be. What you’re essentially doing is checking the details to be sure everything looks and behaves the way it should before you finalize and launch whatever it is you’re doing in Pardot.

While checklists give us a certain level of assurance real confidence comes from experience and learning, if you are interested in learning from our seasoned experts then why not check out these Pardot training courses Sercante offers to immerse yourself in the topics you aren’t totally confident about yet.

What types of Pardot quality assurance testing should admins do?

Lots of quality assurance testing needs to be completed to be sure that any Pardot instance works as expected. Pardot advanced users and admins can complete quality assurance in a Pardot sandbox environment. But most of the day-to-day Pardot QA testing tasks happen in production orgs. Typically, QA tasks related to the flow of data between Pardot and Salesforce are completed in a sandbox environment to prevent the potential loss of data.

You should complete quality assurance testing  in a Pardot production environment (that’s a fancy term for your regular ol’ Pardot instance) when you create or launch the following:

  • Engagement studio program
  • List email
  • Pardot form or form handler
  • Static list
  • Dynamic list
  • Social media post
  • Custom redirects
  • Page actions
  • Dynamic content
  • Email preference centers
  • Scoring
  • Grading

Seasoned Pardot admins likely have lists in their heads to double-check each of these items before sending, saving, or launching them. But admins and end users who are newer to Pardot lack the experience of knowing what can go wrong without proper QA testing. 

If you’re in the latter category, then you’re in the right place! These checklists are for Pardot admins and end-users who are in the beginning stages of learning to use Pardot.

You can find information about more advanced types of Pardot quality assurance testing & the Pardot Sandbox in this blog from Mike Fazio.

Pardot Quality Assurance Testing Checklists for Admins and End Users

As you build your confidence in Pardot, you’ll feel less apprehensive about sending your marketing efforts out into the world. You’ll also get less and less of those “please fix it” messages from your team.

Here’s a checklist of things you can double-check to feel more confident about the work you do in Pardot.

Email Templates and Drafts

You can perform basic quality assurance checks on Pardot email templates and list email drafts. But you may need to invest in a more advanced tool, like Litmus, to be sure your email will render correctly and pass through email spam filters. 

When you’ve finished building your email, click on the ‘Testing’ tab in Pardot to send yourself and any other reviewers test emails. This list may be longer depending on the complexities of the email itself. But we’re going to assume it’s a simple email for the purposes of this checklist.

  • Basic Info
    Look at the Basic Info tab in case there’s something you overlooked. Pay attention to the Campaign and Folder to be sure you selected the right ones for this particular email.
  • Subject Line & Preview Text
    Check that you remembered to add them and proofread.
  • Header Text
    Proofread the email header and adjust if necessary.
  • Email body copy
    Read through the entire email twice and fix any grammatical errors or typos. Then read it again.
  • URLs
    Click every link including linked images to ensure they are working correctly.
  • Text Email
    Make sure the text version of the email matches the HTML version.
  • Sending
    Look at the sender details and to be sure you chose the right ones. 
  • Mailing Lists
    Check your list so you know it’s going to the right email addresses. And remember to add any suppression lists you may need.
  • Completion Actions
    Make sure you successfully added completion actions if that was part of your plan.

Pardot form or form handler

  • Complete the form to test
    Using incognito mode in your browser, complete the form or form handler. You can add the word “test” as you’re completing the form so other Pardot users know your form data is from a test.
  • Find your test data
    Verify data from your test entry made it into Pardot and Salesforce, if applicable, as expected. Pay attention to every field.
  • Check completion actions
    Verify completion actions are carried out as expected.
  • Cause form errors
    Repeat testing the form by trying to “break” it. Fill out the form again, and mess up your entry (use an incomplete email address, leave required fields blank, etc.)
  • Test in other browsers
    You can use a tool like Browserling (free and paid versions) to mimic different types of browsers and operating systems for further testing.

Segmentation Lists 

Static list

  • Spot-check the list to ensure the correct prospects are present.

Dynamic list

  • Click the Preview button. Spot-check the prospects on the list to ensure the correct prospects are present.

Engagement studio program

  • Test every path
    Click on ‘Testing.’ Run the test several times until you’ve tested every possible path.
  • Check your dates
    Double check all of your dates to be sure they align with your goals and best practices.
  • Add test prospects
    Create test prospects and add them to your program first when you want to test more complex programs (make sure your test prospects fit your rules). You may have to shorten your wait times to complete the test in a reasonable amount of time.

Automation Rules 

  • Check the preview
    Preview automation rule to be sure it matches your expectations.

Social media post

  • Review post copy
    Proofread your text. Then read it again.
  • Verify @ mentions
    Go to the social media channel and search for actual profiles to verify any @ mentions you include in the post. Keep in mind that @ mentions on one social media channel probably won’t work on other channels. You’ll have to duplicate tje post and change the @ mentions for other social media channels.
  • Check hashtags
    Look up any new hashtags you want to include on the social media channel you want to use it on. This is so you know you’re using something that’s related to your post and not already in use or irrelevant.
  • Link to something
    Remember to include a call-to-action URL if applicable. Click ‘Insert Link’ if you’re sending people to something that’s in Pardot or a custom redirect.
  • Check the link
    Copy the URL and paste it into a separate tab to check the link.
  • Include a graphic
    Make sure you include a graphic (if applicable). Also, check that the graphic size is appropriate for the social media channel.
  • Check the profile
    Double check that you selected the correct social media profile for the post.
  • Proofread again
    Read the text one last time.

Custom redirects

  • Click the link
    Access the link from your usual web browser. Then, look for your prospect record in the custom redirect prospect list.
  • Test in incognito
    Test the link again from a web browser that’s in incognito mode and look for your click on the custom redirect.
  • Check completion actions
    Verify any completion actions are carried out as expected.

Page actions

You can check that your page actions are working properly after you add tracking code to your website.

  • Configure page actions
    Set up your desired page actions.
  • Go to the pages
    Visit those pages as a cookied prospect.
  • Look for results
    Verify that your page actions worked as expected.

Get a PDF checklist to use for QA testing in Pardot

You can view and download a handy PDF checklist to use every time you’re launching Pardot admin campaign materials. Fill out the form to get your Pardot QA testing PDF checklist:

Be fearless with your Pardot quality assurance testing skills

It’s totally normal to feel uneasiness before completing tasks in Pardot. I mean, you’re sending things out into the world that hundreds or thousands of people might see. Sorry to startle you. But that’s also the cool part about working in marketing. The stuff you’re marketing is going to solve problems for people. And you’re going to help them find out about it!

Confidence will come to you in time after you click around in Pardot and test all the things you’re building. 

Build confidence faster through Pardot training courses

You can fast-track yourself to feeling confident in Pardot by attending structured training sessions. There is so much to learn about Pardot with a seemingly endless list of resources. But nothing beats the real-life applications you learn through talking to people who understand Pardot and use it every day.

Check out the training courses and workshops Sercante offers for Pardot users and admins. You can find specific courses for deep-dives into a topic or beginner-level overviews for people who are new to Pardot.

Click here to view all Sercante training workshops and courses.

The post Work Confidently in Pardot through Quality Assurance Testing appeared first on The Spot For Pardot.

By |2021-07-28T15:56:19+00:00July 28th, 2021|Categories: Content Marketing, Email Marketing, Engagement Studio|