Get On Board with the New Pardot and Slack Integration (Beta)

Included in the Salesforce Winter ‘22 release is a beta feature that highlights the beginning of an integration between Pardot and Slack.

Salesforce officially acquired Slack on July 21, 2021, and the company is already looking to push out new features to integrate Slack with your Salesforce instance. The newest announcement regarding the integration between the two systems went into detail about how every company should have a digital headquarters and what features will soon be available.

Here is what you need to know so you can understand how Slack will work with Pardot.

Connecting Pardot with your company Slack workspace

What does the beta service include?

This beta feature allows your marketing and sales teams to receive updates in their Slack workspace when a prospect engages with your marketing assets. Through a completion action on your marketing asset, a new post will be shared within your Slack workspace informing your team of what asset the prospect interacted with and their basic contact information. When setting up the completion action, you are able to select which Slack channel you want your team to receive the notification.

Push notifications from Pardot to Slack via Pardot completion action

How do I enable the Pardot and Slack integration?

Before enabling the Pardot Slack connector, you will need to create a Slack app that will be installed in your Slack workspace so you can connect Slack to Pardot. If you are like me and have never heard of a Slack app, that’s fine! A Slack app should be created when you need to use Slack APIs to connect your workspace with a third-party service through an integration.

It’s recommended to create an app from an app manifest when setting up the basic Slack app, but it is possible to create your own. The Salesforce documentation for this integration includes JSON code for you to use in the manifest file. 

Slack provides an easy-to-navigate article that helps you create your Slack app for whichever Slack workspace you want to integrate with Pardot. By following the steps shown through the “Create a new Slack app” button, you will be able to create your own app within a couple of minutes.

Pardot Slack Integration basic app setup

Once your app is created, you will have to install it in your Slack workspace. This is so the Pardot and Slack integration is connected and ready to be used. Finally, you will have to generate a token and scope through your Slack app to add your workspace to the Slack connector in Pardot.

Enable the Pardot Slack Connector

Now that we have everything set up on the Slack side of the integration, you should navigate to your Pardot settings through the Pardot Lightning App to enable the Pardot Slack connector. Once you have enabled this setting, Slack will be available as a Connector through your connector settings through the Pardot Settings tab.

Enable the Pardot Slack Connector
Pardot Slack Integration create connector

When you choose the Slack connector, you will be prompted to add a Slack workspace to integrate with Pardot. To connect to your workspace, you will have to use the bot token provided when you generated the token and scopes for your Slack app. Once your workspace is added to the Slack connector, you can then choose up to 10 channels from that workspace to connect to Pardot. 

You will need to copy the channel links in order to set them up through the connector. You can find these by right clicking on the designated channel within your Slack workspace.

Configure Slack Notification Completion Actions in Pardot

Now that you have your Slack workspace and channel(s) set up through the Slack connector in Pardot, you can use the “notify Slack channel” Completion Action on your marketing assets. When setting up your completion action, you are able to select which channel you want to post to as well as customize the message that is posted in the Slack channel. With each post, Pardot will also include the following fields for the prospect so your teams can easily identify them in Pardot:

  • Name
  • Job Title
  • Company
  • Email
  • Phone

These fields will show as blank values if they are not populated for the prospect who has completed the particular action you have set up.

Pardot Slack Integration sample message

Upcoming Features

Salesforce announced Slack-First Marketing in mid-September and emphasized how the initiative will enable marketing teams to be able to collaborate through a shared digital workspace in Slack. 

Pardot Automation for Slack is the newest feature available for Pardot users to integrate with Slack. Although there is not much information on this new feature yet, we know it is expected to be available with the Spring ‘22 release and provides a shared view of your customer in Slack while streamlining notifications for the sales department.

Important things to know

Here are a few considerations you should keep in mind when you enable the Slack integration in Pardot.

  • You will need to work with your Slack workspace admin to create an app for the workspace you want to integrate with Pardot.
  • The Pardot Slack Connector is a beta feature and is only available in English.
  • The Pardot Slack Connector is not available through Pardot Classic, so you will need to install the Pardot Lighting App to use this feature.
  • You can only create the completion action to notify a Slack channel through a Pardot form, form handler, file download, custom redirect, page action, and Pardot Classic emails.
  • At this time, you are only able to connect one Slack workspace to Pardot and add up to 10 Slack channels for the integration.

Learn more about the Slack integration with Pardot

Remember to reach out to Sercante if you want to know more about setting up these features in your Pardot org. Or, comment below to let us know your thoughts.

The post Get On Board with the New Pardot and Slack Integration (Beta) appeared first on The Spot For Pardot.

By |2021-10-26T17:09:41+00:00October 26th, 2021|Categories: Integration, Release Notes|

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.

How to Implement Pardot External Activities with Zapier

Pardot is delivering a whole new way to leverage your prospect data in the Winter ‘22 release. Similar to webhooks, the new Pardot External Activities feature allows users to receive data from third-party systems and use the data in automations and Engagement Studio Programs. For instance, you could record when a prospect registers for a webinar, completes a survey, or watches a video.

In an earlier blog post, we describe how to set up the External Activity in Salesforce so a third party can begin sending activities to Pardot via API. This post will detail how to actually send the activities with Zapier. Similar approaches can be done with other meta-services. If you want hands-on help, we’d love to work with you.

Pardot External Activities Zapier Solution

Before we get started, it is important to note that Zapier doesn’t actually support this Pardot API request. Zapier only supports four of the many API requests possible, so we will be taking advantage of the Zapier Webhook capability to build our solution.

At a high level, we need to:

  • Configure Salesforce to allow our Zap to make API requests to Salesforce and Pardot
  • Create a new Zap which listens for a third-party event (such as registering for a Webinar)
  • Enhance the Zap to submit prospect information to a Pardot Form Handler
  • Enhance the Zap to get an OAuth token from Salesforce
  • Enhance the Zap to publish the External Activity (which works well as the Form Handler has ensured the Prospect exists already)
  • Test

Now I realize this is a lot, but don’t worry, we’ll walk through it all. Once you are done building this Zap, you’ll end up with something like this:

Configure the Salesforce Connected App

Anytime we want to work with the Pardot API, we first need to “authenticate” with Salesforce to receive an Access Token that can be used with the Pardot API. To do so, create a new Salesforce Connected App for Zapier. We highly recommend creating and testing this new Connected App by following the steps in our earlier blog post, Pardot API and Getting Ready with Salesforce SSO Users.

Once you have created your new Connected App, you should have a new Salesforce and Pardot User for the Zapier connection. Keep the user’s username, password, and security token handy for later.

In our example, we will be creating a Zap for a Zoom Webinar Registration. Due to the way Zoom Webinars are integrated with Zapier, you will need to create a Zap for each webinar, as well as creating automations in Pardot for each webinar. This may vary depending on which App you are using in Zapier.

Create a new Zap in Zapier

  1. Log in to your Zapier Account
  2. Create a new Zap and give it a name
  3. Find the third-party app that will trigger this Zap. For our example, we’ve chosen Zoom.
  4. Select your Trigger event. For our example, we have chosen “New Registrant”.
  5. Choose the Zoom account for your connection. If you haven’t already connected the app, now will be your chance!
  6. Next, (and this might differ based on your app), select the upcoming webinar you wish to integrate.
  7. Click “Test trigger”
    1. This often works best if you have a recent “event.” For Zoom webinars, it helps if you have at least 1 person who has already registered for the webinar via the Zoom registration page. In doing so, you will see sample fields and values, making the process a bit easier. 
  8. Finally, click “Continue” and you should have a nice clean “trigger.” Zapier will prompt you to make your first Action.

Enhance Zap to submit the Pardot Form Handler

Zapier now has a handle on prospects registering for the selected webinar, now we need to send this information to Pardot. 

In this first Action, we are going to send details about the person who registered for the Zoom webinar to a Pardot Form Handler. This allows us to create/update a Pardot prospect with the right field values.

Why are we using a Form Handler instead of API calls? 

  1. This approach greatly simplifies the integration by natively handling new prospect creation.
    1. Reduces sync errors for new prospects who have not interacted with a Pardot form yet
    2. More cost effective and efficient than using the Read API to create new prospects
    3. Ensures duplicates are not accidentally created
  2. The action that the person took will actually show up as Prospect Activity. This is good since they took real action and submitted a form.
  3. You can apply Completion Actions, which are not available in the API.

Make sure you have the Pardot Form Handler created and that you have the field names and the https URL handy.

  1. Continuing from the previous section, create a new Webhook Action by selecting “Webhooks by Zapier.”
    1. This step is important to establish who is registering and to make sure we associate the External Activity with a prospect. 
  1. For the Action Event, choose POST.
  2. Set up the action by filling in the following fields:
    1. URL: The https URL of your Pardot Form Handler
    2. Payload Type: form
    3. Data: Enter the Pardot Form Handler field name, and the values coming from the trigger setup earlier. Add new “rows” for each field you wish to populate in the Pardot Form Handler based on your trigger data available.
  3. Once you have finished setting up the Action, test the action, check that the Pardot Form Handler was called, and verify that the data is where it should be.
  4. Rename the Action to “Send Registration Info to Form Handler” so that it’s clear what this Action is accomplishing. 

Enhance Zap to get OAuth token from Salesforce

Now things start to get a bit tricky. Since we can’t leverage the Pardot app in Zapier, we need to do things manually. This is where we will use the Salesforce and Pardot User we set up with the Connected app in the first section.

  1. Create a new Webhook Action by selecting “Webhooks by Zapier”
  2. For the Action Event, choose POST
  3. Set up the action by filling in the fields:
    1. URL: https://login.salesforce.com/services/oauth2/token
    2. Payload Type: form
    3. Data -> grant_type: password
    4. Data -> client_id: Enter the Consumer Key from your Connected App
    5. Data -> client_secret: Enter the Consumer Secret from your Connected App
    6. Data -> username: Enter the Salesforce Username of the Pardot user we will use for API calls
    7. Data -> password:  Enter your Salesforce user’s password followed by the Security Token
  4. Once you’ve provided all the values above, Test and Review. A successful request should show values like access_token and instance_url for your Salesforce org.
  5. Rename this Action to “Get Salesforce OAuth Token” so that it’s clear what this Action is accomplishing. 

Enhance Zap to publish Pardot External Activity

Finally, we will send the External Activity to Pardot

  1. Create a new Webhook Action by selecting “Webhooks by Zapier”
  2. For the Action Event, choose POST
  3. Set up the action by filling in the fields:
    1. URL: https://pi.pardot.com/api/v5/external-activities
    2. Payload Type: json
    3. Data -> extension: Enter the name of the Marketing App Extension you created in Salesforce
    4. Data -> type: Enter one of the Activities you set up and associated with your Marketing App Extension in Salesforce
    5. Data -> value: Enter a unique value to identify this Activity, event IDs work great here
    6. Data -> email: Enter the email address that was used in step 3 of the “Enhance Zap to submit the Pardot Form Handler” section
    7. Headers -> Authorization: This one is a bit tricky to fill out. First, when you click in the text box, type “Bearer “ (with the space) and then select the Access Token.
    8. Headers -> Pardot-Business-Unit-Id: Enter the ID of the Pardot Business Unit that is associated with the Marketing App Extension. You can find the Pardot Business Unit ID by navigating to Salesforce Setup >Pardot Account Setup. (Detailed instructions here).
  4. Once you’ve provided all the values above, Test and Review. Check the Pardot Prospect for the new Activity record. This activity will appear between the Prospect Activities and Custom Fields section of the prospect page.
  1. Rename this Action to “Send External Activity” so that it’s clear what this Action is accomplishing. 

Test

Now it’s time to test our Zap end-to-end. 

Activate your Zap and perform the action that you are capturing in the Zap’s Trigger (i.e. register for the Zoom webinar). After a couple of moments, check the Pardot prospect that you are testing with. You should now see all the information you passed through the Zap!

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 Zap, which assumes all prospects going through this trigger are from the same Business Unit. Proceed with caution and test rigorously when attempting more advanced solutions with business units.
  • Salesforce only allows five access tokens to be issued at a time. With high volumes of a triggering event, it is possible that Zaps may fail due to Salesforce Access tokens getting recycled before they can be used in the following actions (this is due to us manually getting an Access Token with the second Action).
  • Any time the user’s password and/or security token changes in Salesforce, each ZAP that uses it will also need to be updated.

These considerations are best addressed by writing your own code, which can properly address the edge cases, etc. For assistance with this or other Pardot External Activities, reach out to Sercante!

The post How to Implement Pardot External Activities with Zapier appeared first on The Spot For Pardot.

By |2021-10-15T18:27:46+00:00October 15th, 2021|Categories: Data Management, Integration, Pardot Business Units, Release Notes, Salesforce|

Pardot External Activity: What it is and how to use it

Pardot is delivering a whole new way to leverage your prospect data in the Salesforce Winter ‘22 release. Similar to webhooks, the new Pardot External Activities feature allows users to receive data from third-party systems and use the data in automations and Engagement Studio Programs. For instance, you could record when a prospect registers for a webinar, completes a survey, or watches a video, and then trigger automations from those actions.

Pardot external activities

There are 3 main steps we will be guiding you through in this post. 

  1. Register the Pardot External Activity types in Salesforce
  2. Integrate third-party systems with Pardot External Activity (we use the API here)
  3. Leverage the new External Activities inside Pardot

To use External Activities, you must have a Plus, Advanced, or Premium Pardot Account and be using the Pardot Lightning App (remember, the Pardot Classic app is being retired).

Register the External Activity types in Salesforce

Similar to how a Salesforce Custom Object needs to be defined before you can start creating records, we need to set up an Extension and the Extension’s Types before we can record External Activity on Prospect records. A Salesforce Administrator or a Marketing Setup Administrator will need to perform these steps. 

  1. Create a Marketing App Extension.
    1. Navigate to Setup > Marketing App Extensions.
    2. Select “New.”
marketing app extensions
  1. Name your new Extension.
  2. Select “Active in Automations.” This is what allows the extension to show up within Pardot.
  3. Select “Save.”
new marketing app extension
  1. Create an associated Activity.
    1. Select the “Related” tab.
    2. Select “New” next to Activity Types.
      • This will be an action your prospects perform, such as registering, attending, or being absent from a webinar.
      • Activity types cannot be shared across extensions, so make sure you create these activities for each extension!
      • Choose activity type names that make sense to your users.
new activity type
  1. Select “Active in Automations.”
  2. Select “Save.”
  3. Assign the extension to your Pardot Business Unit(s). 

You’ll need to perform this step even if you only have one Business Unit. Extensions can be assigned to multiple Business Units. 

  1. Within the Related tab, select “New” next to Business unit Assignments.
  2. Select the first Business Unit.
  3. Select “Save.”
  4. Repeat if you’re using multiple Business Units.
new business unit assignment

Before you build/set up this external activity, check to make sure the solution you are looking to integrate doesn’t have an existing solution built. They may handle this whole side of the process for you, or you may only need to assign the extension to your Pardot Business Unit(s).

Integrate third-party systems with Pardot External Activity

This step is where we’ll connect the third-party system that is collecting the prospect’s activities and extension we built above. This step will use the Pardot API and should be included in any vendor’s solution that supports External Activity. Given this is a brand new feature, odds are External Activity is not yet supported by existing integrations.

If it is not included, you should be able to glue things together yourself. Below are three guides that will help: 

Leveraging the new External Activities inside Pardot

Now that you’ve created an External Activity and have a solution to send the prospect’s activities to Pardot, “Prospect External Activity” will be available within Automations:

rules prospect external activity

And “External Activity” will be an available Trigger in Engagement Studio:

trigger external activity

The value for the External Activity refers to the individual event, webinar, etc. These values will change for each activity and will NOT be pre-populated, so you’ll want to ensure your users know the exact values to look for when using the External Activities in Pardot. You can use the semicolon operator for a list of values.

rule match all

Keep in mind

External Activities do not update the prospect’s last activity time stamp. That means external activities will not trigger a sync between SFDC and Pardot, and they should not be used to indicate the last time the prospect took an action.

rules match all

Finally, Automations will process External Activity data even if the external activity is inactive within Salesforce. So, if you deactivate an extension, you’ll want to review the Automations and Engagement Studio Programs that are using the External Activity. Consider using tags on your Pardot Automations to help you easily find and administer them.

Requirements

  • Plus, Advanced, or Premium editions of Pardot
  • Requires the Pardot Lightning App
  • Work with your Salesforce Admin or Marketing Setup Admin to configure this. 

External Activity helps Pardot customers send information to Pardot from external systems. While many things are possible with the Pardot API, this feature does not send information from Pardot to other systems. If this is a critical capability for your org, you can help impact the Pardot Roadmap by sharing your Product and feature ideas on the  Salesforce Idea Exchange

Want to keep learning about External Activity? Check out these two additional blog posts:

The post Pardot External Activity: What it is and how to use it appeared first on The Spot For Pardot.

By |2021-10-15T17:38:10+00:00October 15th, 2021|Categories: Campaigns, Data Management, Email Marketing, Integration, Pardot Business Units, Salesforce|

Using the Pardot Integration from Zoom App Marketplace

Integrating Pardot with Zoom webinars allows you to not only collect prospect activity in real time, but also track attendance, handle communications, and send sales new leads quickly and easily. Using the Zoom-native Pardot App simplifies sharing data between these two systems by allowing you to capture Zoom webinar registrants, attendees, and absentees within Pardot lists. 

In this post we’ll cover the pros and cons of this integration as well as walk you through the setup process for a webinar. 

At a high level, to integrate Zoom and Pardot you will need to:

  1. Install and set up the Pardot App from the Zoom App Marketplace.
  2. (Optional) Configure Custom Zoom Registration Fields to go to Pardot.
  3. Start creating Zoom webinars.
  4. Prepare your email notifications.

Considerations for Using the Pardot App from Zoom App Marketplace

Before we dig in, there are a few things to consider when using this native integration:

  • The integration works best when using the Zoom registration form. 
    • There is an option to use a Zoom Post URL (similar to how we think about Pardot Form Handlers). However, this option relies on the Thank You page of the Pardot Form having an additional hidden form that changes per webinar. This hidden form must be completed and requires JavaScript for a behind-the-scenes submission. That makes this option prone to human error and/or browser issues. 
  • Both email solutions leave something to be desired. You can choose between: 
    • Emails styled in Zoom with prospect-specific URLs to join the webinar. With this option you’ll lose out on Pardot tracking and personalization capabilities.
    • Your beautiful Pardot email templates with all the benefits of Pardot data, tracking, and personalization, but no Zoom webinar details or prospect-specific URLs to join the webinar. 
  • This process will not connect prospects with the associated Salesforce campaign. You’ll need additional automations if that’s part of your strategy. 
  • Each webinar requires its own setup and configuration. These take between 1-3 hours each, depending on how granular you get with automations. As a result, this integration is better suited for companies that have a low volume of webinars.
  • There is no mechanism to pull in questions and answers from webinar polls.

Install and Set Up the Zoom Integration App 

  1. Navigate to the Pardot App on the Zoom App Marketplace and sign into your Zoom account. 
  2. Select “Install” from the top right of the Pardot App listing page.
  3. Once installed, you’ll see a prompt to enter your Pardot credentials. If you are not redirected to this screen, click “Manage” from the left-side navigation, scroll down, and click “Configure”). Select “Use Salesforce SSO.”
    Use Salesforce SSO
  4. Next, install a very tiny managed package provided by Zoom. This package creates a connected app to allow Zoom to connect to your org. Click “Install Package” and install this for Admins only.
  1. While the package is installing, create a Salesforce and Pardot user for your Zoom integration. Having one user per integration helps in the event that you need to troubleshoot your Pardot org and/or integrations. Once the user is set up, log in as this user to authorize and approve the app.  
  2. Next, provide Zoom with the Pardot Business Unit ID. You can find the Pardot Business Unit ID by navigating to Salesforce Setup > Pardot Account Setup (you can access detailed instructions here).
    Enter credentials
  3. Select “Save”

Zoom and Pardot are now connected, and they are ready to work together!

(Optional) Configure Custom Zoom Registration Fields Sync to Pardot

Zoom automatically passes most of the common fields directly into Pardot. This includes: 

  • Email
  • First Name
  • Last Name
  • City
  • State/Province
  • Zip/Postal Code
  • Country
  • Phone
  • Job Title
  • Organization
  • Industry
  • Questions & Comments
  • Employees

You can also create new fields in Pardot to sync Purchasing Time Frame and Role in Purchase Process from Zoom. 

Depending on what information you are looking to capture in Pardot, you may decide you want to have Zoom pass more fields into the prospect record. A good example of a field you may wish to connect is “Join URL.” This field is a prospect-specific URL that will allow the prospect to join the webinar. 

To add this field, simply:

  1. Navigate to Pardot Settings > Object and Field Configuration > Prospect Fields. Select “+Add Custom Field.”
  2. Complete the required info and select “Create Custom Field.”
  3. Once created, go back to the Pardot App in the Zoom Marketplace and select the “Custom Field Mappings” tab.
  4. Map the Zoom Registration Field “webinar_join_link” to the Pardot Custom Field that you created. Click “Add.”

Your new custom field is now connected. Future registration captured by Zoom will pass the Zoom Webinar Join URL to your Pardot prospects. But please note, the prospect record will only have values from the latest registration.

Start Creating Zoom Webinars

You will need to configure the Pardot integration for every webinar you create in Zoom. 

  1. First, create three static lists in Pardot so Zoom knows where to send the data. You will need a:
    • Registration List
    • Attendee List
    • Absentee List

Make sure you use naming conventions so these lists are easy to find in Zoom and any Pardot automations. 

  1. Next, create or locate the webinar in Zoom. Select the webinar name to view details. 
  2. Select the “More” tab and then select “Configure” within the Integration section.
    create a zoom webinar
  3. Provide Zoom with the static lists you created in Pardot. All three lists are required.
    Provide zoom with pardot static lists
  4. Click Save

Now your lists will be kept current with the right prospects!

Prepare Your Zoom Webinar Email Notifications

Getting prospects to register for a webinar is only half the battle. Now we need to get them to attend! Registration and reminder emails are key here, and getting the right message delivered at the right time will make all the difference.

Both Zoom and Pardot can be used to send these emails, each having their own considerations.

Considerations for Using Zoom Email Notifications

Zoom email settings can be configured at a Zoom Account level (i.e. for your entire company) and at a webinar level. You can customize email templates only at the Account level, and you can’t have webinar-specific templates.

  • Registration emails can include the prospect-specific Join URL and are sent immediately after registration.
  • Reminder emails can include the prospect-specific Join URL and can be sent 1 hour, 1 day, and/or 1 week prior to the webinar.
  • Follow-up emails can be sent 1-7 days after the webinar ends.

Considerations for Using Pardot Email Notifications

With Pardot, create an Engagement Studio program or Automation Rules to automatically send out your registration, reminder, “thank you for attending” and “Sorry we missed you” emails. These automations should look for Prospect that join the webinar’s three static lists.

  • If you configured your integration to send the Zoom Webinar Join URL to Pardot, this value can be included in registration emails sent from Pardot. 
  • Reminder emails can also include the Zoom Webinar Join URL, however if the prospect registered for multiple webinars in close proximity, the Zoom Webinar Join URL on the Prospect’s record may not match the webinar you are reminding the prospect about!
  • Follow-up emails can be sent whenever you like. You can even choose to send a different email template to those who register and attend versus those who register and are absent.

Try the Sercante Connector for Zoom Webinars and Pardot

As mentioned above, if you have a low volume of webinars, this process may not be an issue, especially since the integration is the low-low price of free. However, if you’re hosting one webinar per week (or more), then this process is pretty daunting. 

If you need to scale up your Zoom-Pardot integration, check out the Sercante Connector for Zoom Webinars and Pardot

What other tools or webinar platforms are you looking to integrate with Pardot? Tell us in the comments!

Special thanks to Erin Duncan for contributing to this post.

The post Using the Pardot Integration from Zoom App Marketplace appeared first on The Spot For Pardot.

By |2021-09-23T16:49:58+00:00September 23rd, 2021|Categories: Email Marketing, Event Management, Events, Integration, Zoom|

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|

Watch the Data Flow into Pardot with Zapier

If you’re like me, then you often work with marketing tools that do not integrate nicely with Pardot forms.

Maybe they claim to have a ‘direct’ integration with the tool. However, we all know it’s nothing more than a Salesforce integration.

#annoying 

Don’t give up! There is a way around this common frustration. 

Enter Zapier webhooks, which you can use to bring data into Pardot.

This handy little-known feature is the solution to all your Pardot integration problems!

Dramatic maybe. But it’s still a game changer. 

How to use Zapier webhooks with Pardot

With Zapier Webhooks, we can capture data from nearly any place and push it to Pardot as a form handler submission.

You read that correctly — a form handler submission. 

Prerequisites for using Zapier webhooks with Pardot

You’ll need to do the following before we get into the setup: 

  1. Create a Zapier account. (they have a free account that allows for 100 zaps a month)
  1. Set up a Pardot form handler.

    Here are two rules to follow when you configure your form handler:

  • ONLY have email as ‘required.’ You can add other fields. But do not mark them with ‘required.’
  • Set the form in kiosk mode.
    Pardot FH - kiosk mode
  1. Identify how you’ll bring data into Zapier.

    This can look like using one of Zapier’s native integrations or using a Zapier webhook to get data. Whichever method you use, the most important thing to do is to get the data triggering the Zap. 

Use cases for Zapier with Pardot

Here are common examples of ways to use Zapier with Pardot to bring data into the platform via a form submission.

LinkedIn Lead Generation

In this example, a company is using LinkedIn Lead Generation forms to capture new leads.

There is no direct way to tie LinkedIn submissions to Pardot. So, the company sets up a zap to trigger when a new response is received. Their zap is configured to push the data to Pardot via a form handler post.
LinkedIn Form Response Zapier

Google Form Submission

For this example, our company is using Google Forms to send out a survey to their customers.

The survey itself has data they don’t want within Pardot. So, they chose to send it using Google Forms.

Still, the company wants to see the name and email address of everyone who completes the survey within Pardot.

They can trigger a new workflow (zap) using Zapier when a survey submission comes in. That’s because Zapier integrates directly with Google. Their zap is configured to push the data to Pardot via a form handler.

Drift Lead

In this case, a company captures a new lead via a drift chat. They leverage Zapier’s ability to receive those leads to route the data to Pardot via a form handler. 

Setting Up a Zap with a Pardot Form Handler

Follow these steps to set up a Zapier ‘zap’ to bring data into Pardot as a form handler submission.

Step 1

Create a new zap and select the Google Sheets integration (the app selection will change based on where your data comes from).  

The trigger is ‘New Spreadsheet Row,’ and then select the correct sheet from your drive.

Zapier for Pardot Forms - New Spreadsheet Row Google Sheets

Pro Tip: Test the data capture to ensure it’s working. This will only work if there is data in the app triggering your zap. 

In our example, I submitted example data to the form, and Zapier successfully pulled it in as a test.

Zapier for Pardot Forms - Zap Trigger - Test

Step 2

Now move to select the Webhook as the Action step. Select the POST option on the setup page.

Zapier for Pardot Forms - Zapier Action - Post 1

Step 3

Paste your HTTPS encoded Form Handler url into the URL box.

Zapier for Pardot Forms - Zapier Action - Post 2

Step 4

If we were to activate it now, the zap would trigger and post to the Form Handler URL. But, no data would pass through. 

We need to set up the data pass.

We’ll take this step by step below:

  1. Add a ? to the end of your URL
    Pardot forms Zapier Action - Post 3
  2. For each field you want to pass to Pardot:
    • Right after the question mark, add the external field name.
      Zapier for Pardot Forms - Pardot FH - Fields
    • Immediately after the external field name, add an equal sign.
      Zapier Action - Equal Sign
    • Immediately after the equal sign, add in the data source. This can be done via the dropdown in the URL field.

      Scroll until you find the field that contains the data you want to pass. Then, click on it.
      Zapier Action - Select Data

    • Your URL will now look like this. The underlined portion is the part that you’ve added to send over a single field.
      Zapier Action - Final URL
    • If you want to add another field, then add a “&” to the end of your URL and then repeat steps I – V for each field.
      Zapier Add Another Field

Step 5

Test your action and make sure the submission comes through in Pardot. The final URL will contain all the fields you’d like to pass. On the testing screen, you’ll see what the final URL will look like with your test data.

Click test. Then, ensure you captured the data in Pardot.

Zapier Action - Testing

Now, turn on your Zap, and watch the leads flow into Pardot! 

Go forth and let the data flow into Pardot

Now you know how to bring in data from third party tools into a Pardot form handler. 

This unlocks the ability to score, grade, assign, add to Salesforce campaigns and more! The sky’s the limit with how you can use this setup. 

Happy building!

Learn More About Pardot Forms

The post Watch the Data Flow into Pardot with Zapier appeared first on The Spot For Pardot.

By |2021-05-21T20:02:36+00:00May 21st, 2021|Categories: Content Marketing, Data, Integration, Integrations|

How to address Pardot issues related to the Salesforce outage

On May 11, 2021, Salesforce and Pardot users experienced a Salesforce outage related to a domain name service (DNS) issue. Salesforce was down for about four hours because of an “emergency break fix” that wasn’t successful.

The Salesforce outage affected Pardot. However, Pardot remained up and running even if marketers couldn’t log in to their specific instances.

As always, you can check https://status.salesforce.com/ to find information about ongoing issues that could potentially affect your Salesforce org.

Around 5 p.m. Eastern Standard Time, marketers noticed they couldn’t log into the CRM or Pardot. Salesforce was actively restoring services at 8:30 p.m. EST, and the team restored many services that were impacted by that time.

Resolved-Multiple Salesforce Applications Disrupted

Were Pardot end users affected by the Salesforce outage?

Pardot end users likely did not experience the effects of the outage.

It is currently looking like the outage may have caused a few delayed emails and delayed sales people callbacks. However, we’re expecting these small delays to be all end users will experience during this outage event. 

How did the Salesforce outage affect Pardot?

Salesforce co-founder and chief technology officer Parker Harris commented on the outage via Tweet. He said the base issue causing the Salesforce outage was related to the domain name system (DNS). 

The DNS issue affected Pardot by restricting access to the CRM, which caused the Pardot-Salesforce connector to become unavailable. 

In addition, Pardot sends emails using Marketing Cloud send services (at least as far as DNS naming organizes them). So, Pardot was most likely unable to send emails during the outage.

Pardot authentication happens on Saleforce.com services, so Pardot users were not able to to log in during the outage. This login unavailability impacted both marketers trying to log in as well as API authentications. 

Next steps for Pardot users now that service is restored

The core of Pardot was unaffected. But we do have some things to check around the edges of Pardot where it interacts with other Salesforce services. 

Here’s how you can stay ahead of potential issues that may have been caused by the Salesforce outage:

Check new leads or prospects

Spot-check any leads that came in on form fills during the connectivity outage. Make sure new leads made their way into the CRM correctly. 

Look at your busiest forms and form handlers that have completion actions to sync to Salesforce. Make sure all prospects have the Salesforce cloud icons you expect. If they do not appear to be syncing, open the prospect record and click “Sync with CRM.”

Verify Pardot successfully delivered emails during Salesforce outage

The Salesforce outage may have delayed email delivery. It appears as though Pardot couldn’t communicate with outbound email servers. Look at reporting for any email campaigns or you scheduled for delivery on May 11, 2021. Also, check any autoresponders that may be connected to form fills to ensure everything was delivered as expected. 

Verifying Pardot sent your emails can give you assurance that the outage didn’t affect your campaigns. But remember, email is a fault-tolerant service, and any sending issues will fix itself automatically. Or, the Pardot team will push the buttons to make this right for us.

Monitor API integrations

Third-party integrations likely lost the ability to sync with Pardot during the outage event. However, the ways in which the outage affected APIs depends on how the integration was built to deal with these situations. 

Here are three ways your APIs may respond to outages.

The API:

  • Will automatically retry to connect, and the data should have made its way into Pardot with no issues. 
  • May have retried and stopped after too many unsuccessful attempts, so we don’t have the data in Pardot. 
  • May not retry to connect, so we don’t have the data in Pardot. 

You will need to check your Pardot tool integrations and figure out how to sync any missing data. You can likely sync missing data by manually pushing ‘retry’ in each tool. Or, you can use the normal export process to import data into Pardot just like we do when we don’t have the tools integrated. 

What is DNS?

DNS or Domain Name System is effectively the computers ‘phone book’. This is the system that translates ‘TheSpotForPardot.com’ to the IP address (kinda like a phone number) that computers use to talk to each other. So with a DNS issue, the computer’s phone books to each other don’t work right. They can’t correctly talk to each other. 

Pardot and the Pardot services didn’t have any DNS issues during this time, but rather the Saleforce platform infrastructure had DNS issues. So, the world could interact with Pardot services just fine — it continued to collect forms, deliver whitepapers, etc. 

Pardot just couldn’t talk to Salesforce services, which includes authentication for logging in.

If you’re seeing connector issues, check out this resource to troubleshoot for common Pardot-Salesforce connector issues.

Get help from Pardot consultants

If all else fails and you’re completely lost in Salesforce outage freakout mode, then we’d love to talk to you. 

The Sercante Pardot consultant team knows a thing or two about Salesforce outages and how they affect Pardot orgs. Contact us to chat.

The post How to address Pardot issues related to the Salesforce outage appeared first on The Spot For Pardot.

Upgrading to the Salesforce-Pardot V2 Connector

Did you know there are actually two versions of the Pardot to Salesforce connector? If you purchased your Pardot account after February 2019, you’ve likely always had the newer V2 Connector, however, if you purchased before February 2019 and haven’t upgraded, you will still be on the V1 Connector. Pardot released a path to upgrade from V1 to V2 in the 2020 Summer release, but I’ve found that a lot of Pardot admins are still hesitant to upgrade. In this post I’ll cover all the considerations and options you have when upgrading your connector and help you squash those “this upgrade is irreversible” anxieties. 

If you don’t know which connector version your Pardot instance is currently using, follow these steps to check.

Salesforce-Pardot Connector V1 vs V2, What’s the Difference?

The V2 connector has improved security and instant metadata sync, but the feature that catches the attention of most day to day admins is you can pause the sync! Gone are the days where you have to disconnect the Salesforce connector completely and then fear something will go wrong when you try to connect it again. Now you have a simple “Pause” and “Resume” button to use to your heart’s content. Wait, am I the only one who got super anxious about disconnecting the Salesforce connector? Ok fine, moving on…

With the V2 Connector you also have the option to use the B2BMA Integration user instead of a connector user. This is fantastic because

  • The B2BMA Integration user does not require a paid Salesforce license
  • Since no one can log into Salesforce as the B2BMA Integration User you can give this user all the access and permissions Pardot needs 

Connecting via the integration user also gives you access to Marketing Data Sharing, which allows you to get more granular about which records are eligible to sync from Salesforce to Pardot. 

Finally, for multiple Pardot Business Units, the V2 connector gives you access to the Business Unit Switcher which allows you to seamlessly switch between Pardot Business Units without needing a unique login to each Unit. 

Considerations For The Salesforce-Pardot V2 Connector

  • Upgrading to the V2 Connector is irreversible! I know, “irreversible” is not my favorite word when it comes to new features, but take a deep breath, change is good.
  • You can’t change the Salesforce instance that your Pardot account is connected to after the upgrade. If you are thinking about moving Salesforce instances or creating a new Salesforce instance in the near future, do not upgrade.
  • If you continue to use the existing connector user rather than the B2B Integration User, make sure your connector user has access to the Pardot_to_SF_Integration_Secure_Connected_App connected app before you upgrade.
  • If you need to restrict which records are eligible to sync from Salesforce to Pardot and do not have access to Marketing Data Sharing, stick to using a connector user with the V2 Connector.
  • The V2 Connector will be created in a paused state, so don’t forget to resume the connection after the upgrade!

Let’s do this!

How to Upgrade to the Salesforce-Pardot V2 Connector

If you’re ready to upgrade to the V2 Connector, you can either dive in by upgrading and moving to the integration user at the same time, or you can take a more gradual approach in order to upgrade and then later move to the integration user.

To dive in:

  1. Open your connectors in Pardot
    1. Classic: Admin > Connectors
    2. Lightning: Pardot Settings > Connectors
  2. Select the Action Wheel next to your Salesforce Connector and click Upgrade
  1. Select the “I have read the documentation. I understand how the upgrade changes my account, and I understand that this change is permanent” checkbox and select Next
  2. Next, select the Integration User and select Choose User
  1. Your upgrade will likely take 10-15 minutes to complete. The connector will be created in a paused state, so make sure you resume the connection!

If you’d prefer a more gradual approach:

  1. Ensure your connector user has access to the Pardot_to_SF_Integration_Secure_Connected_App connected app in Salesforce
  2. Follow the steps above, but choose “Current connector user” when you are at step 4

When you are ready to move from the Connector User to the Integration User later

  1. Open your connectors in Pardot
    1. Classic: Admin > Connectors
    2. Lightning: Pardot Settings > Connectors
  2. Select the Action Wheel next to your Salesforce Connector and click Pause Sync
  3. Select the Action Wheel again and click Edit Settings
  4. Enter the B2BMA integration username in the connector user box and click “Change Trusted Connection User”.
  1. The B2BMA Integration username is unique for each Salesforce instance so make sure you grab the correct username from your Salesforce users table.
  2. Resume the connector

Conclusion

And easy-peasy-lemon-squeezy, your Salesforce-Pardot connector is upgraded to the V2 Connector. Hopefully this post has squashed your “this upgrade is irreversible” anxieties and you are ready to take steps to the upgrade.  If you still have questions or concerns after reviewing all the considerations and options for upgrading to the V2 connector, leave a comment below and we can help you through it.

The post Upgrading to the Salesforce-Pardot V2 Connector appeared first on The Spot For Pardot.

By |2021-03-19T13:57:43+00:00March 19th, 2021|Categories: Integration, Pardot Editions|