Category

Marketing Automations

As part of the Winter ‘24 release, Account Engagement users gained the ability to copy assets to and from Account Engagement Sandboxes. This allows marketers to test automations and assets before pushing them to their Production Account Engagement org. It also allows them to pre-populate Sandboxes with assets so they don’t have to start from scratch. 

The Account Engagement to Sandbox-to-Production Flow currently supports seven asset types: 

  1. Email Templates
  2. Custom Redirects
  3. Custom Fields
  4. Files
  5. Engagement Studio Programs
  6. Layout Templates
  7. Form Handlers

Account Engagement Sandbox-to-Production Flow Installation Instructions

To start using the Sandbox-to-Production flow, you will need to create a Connected App and two named credentials. 

Step 1: Create the Connected App in the Sandbox Org

This provides the interface to authenticate into an org.

  1. In your source org (Production), grab the Sandbox Asset Auth Flow callback URL.
    • Go to Setup > Auth. Providers
    • Open the Sandbox Asset Flow Auth
    • Copy the Callback URL, you will need this shortly
  2. In your Sandbox org, navigate to Salesforce Setup > App Manager and then select New Connected App.
  3. Configure the Connected App as follows:
    • Connected App Name: MCAE Sandbox to Production
    • Contact Email: Email Address of the admin who will be managing the Sandbox-to-Production promotion process. 
    • Enable OAuth Settings: Checked
    • Callback URL: The Source Org Callback URL you copied in step #1
    • Selected OAuth Scopes:
      1. Access the Salesforce API Platform (sap api)
      2. Access unique user identifiers (openid)
      3. Manage Pardot services (pardot_api)
      4. Manage user data via APIs (api)
      5. Manage user data via Web browsers (web)
      6. Perform requests at any time (refresh token, offline_ access)
    • Require Secret for Web Server Flow: checked
    • Require Secret for Refresh Token Flow: checked
  4. Select Save
    • Note: It may take 10-15 minutes for the connected app to be ready for authentication.
  5. Select Manage Consumer Details
  6. Copy your Consumer Key and Consumer Secret for later use.

Step 2: Update Auth Provider in Production Org

This handles the authentication process.

  1. In your Source Org (Production), enter the Consumer Key and Consumer Secret from your Connected App
    1. Go to Setup > Auth. Providers
    2. Open the Sandbox Asset Flow Auth
    3. Select Edit
    4. Enter the Consumer Key and Consumer Secret
  2. Select Save

Step 3: Create an Account Engagement API Named Credential

This establishes access via an integration user to the Account Engagement API.

  1. In your Source Org (Production), navigate to Setup > Named Credentials
  2. Select New Legacy
    1. Note: Do not select “New”, it should be “New Legacy”!
  3. Configure the Named Credential as Follows:
    1. Label/Name: MCAE API Access
    2. URL: https://pi.demo.pardot.com
    3. Identity Type:  Named Principle
    4. Authentication Protocol: OAuth 2.0
    5. Authentication Provider:  Sandbox Asset Flow Auth
    6. Scope: Pardot_api refresh_token
      1. Make sure this says “pardot_api refresh_token”, not just “api refresh_token”
  1. Start Authentication Flow on Save: Checked
  2. Generate Authorization Headers: Checked
  1. Select Save
  2. Log back into the Sandbox org with your credentials. Doing so finalizes the authentication for the named credential.

Step 4: Salesforce Metadata API Named Credential

This establishes access via an integration user to the Metadata API to retrieve BU details.

  1. In your Source Org (Production), navigate to Setup > Named Credentials
  2. Select New Legacy
    • Note: Do not select “New”, it should be “New Legacy”!
  3. Configure the Named Credential as Follows:
    • Label/Name: Metadata API Access
    • URL: https://mydomain—sandboxname.sandbox.my.salesforce.com, but replace “mydomain” and “sandboxname” with the value from your sandbox url.
      1. ex: https://sercante–testing.sandbox.my.salesforce.com
    • Identity Type:  Named Principle
    • Authentication Protocol: OAuth 2.0
    • Authentication Provider:  Sandbox Asset Flow Auth
    • Scope: api refresh_token
    • Start Authentication Flow on Save: Checked
    • Generate Authorization Headers: Checked
  4. Select Save
  5. Log back into the Sandbox org with your credentials. Doing so finalizes the authentication for the named credential.

Running the Flow

Before you run the flow, ensure the destination org has at least one Folder, Campaign, and Tracker Domain. If your destination does not have these assets, you will run into issues with the flow.

  1. In your Source Org (Production), navigate to Setup > Flow
  2. Open the Account Engagement Sandbox-Production Bulk Asset Copy Flow
  3. Select Run
  4. For “Named Credential for Salesforce API Access” select the Metadata API Access (step 4 above)
  5. For “Named Credential for Account Engagement API Access” select the MCAE API Access (step 3 above)
  1. Select Next
  2. Select your direction of Copy
    • From a Sandbox to Production
    • From Production to a Sandbox
  3. Select your Production and Sandbox Business Units
  1. Select Next
  2. Select assets to copy over, select Next
  1. Confirm the Assets, select Next
  2. Select your Folder, Campaign, and Tracker Domain for your new assets
  3. Select Copy Assets
  4. The final screen will provide details regarding the copied assets as well as let you know if there were any errors.

Considerations for Using the Sandbox to Production Flow

Since this is a new capability for Account Engagement, there are some details and settings that do not come over when copied. I thoroughly tested each asset type and below are the considerations that I found.

Tracker Domain

You must verify the Tracker Domain in your Sandbox. Otherwise, Email Templates, Custom Redirects, and Files will fail when the unverified Tracker Domain is selected. You can use the default tracker domain (go.pardot.com) but this will cause issues when copying over any Custom Redirects with a Vanity URL.

Email Templates

  • When copied, the email sender will be replaced by a General User with the email [email protected]. This applies even if you have a sender hierarchy specified using “Assigned User” and ‘Account Owner.”
  • Email Templates containing Dynamic Content will not copy over. This is because dynamic content is unique to the Business Unit. Even if you have the same Dynamic Content in each Business Unit, they will have a different asset ID and merge tag.
  • If the Email Template contains a merge tag for a field that is not in the destination org, the flow will fail. Ensure all needed fields are copied to the destination org before copying over any assets that use custom field merge tags.

Custom Redirects

A Custom Redirect’s Completion Action(s) will not copy over, however, the Google Analytics Parameter values do.

Files

During my testing, I tested PNG, JS, JPG, GIF, SVG, CSS, and PDF file types, and all successfully copied over!

Custom Fields

When you copy custom fields, only the following information comes over:

  • Field Name
  • Field API Name
  • Field Type

Engagement Programs

  • When you copy an Engagement Studio Program (ESP) only the ESP structure is copied. The Recipient List, Suppression lists, Send days/times, and “Allow prospects to enter more than once” settings do not come over and will need to be reconfigured.
  • The assets specified in a Trigger or Action node, such as email templates, landing pages, and forms, will need to be reselected in the new ESP. However, the number of wait days specified in the node will copy over. 



  • If an Action node looks at a Prospect field (i.e. Prospect default field “Job Title” is not blank) and that field is in both Production and Sandbox, then the node will be copied to the new ESP with the field and value/settings specified. If the field does not exist in both Production and Sandbox, then the Action node will still be in the ESP but the field and value/settings will need to be reconfigured. 

Layout Templates

If you use Dynamic Content within your Layout Templates, keep in mind that the Dynamic Content will not come over when the Layout Template is copied. You can copy the Dynamic Content over as a separate asset, but you will still need to edit the Layout Template in your destination Business Unit to make sure it has the correct Dynamic Content ID.

Form Handler

  • Ensure all the fields on the Form Handler exist in the environment you are copying to before copying the Form Handler.
  • If your Form Handler only uses Default Prospect Fields, then all of the fields will come over when the Form Handler is copied. However, if your Form Handler uses any Custom Prospect Fields, the custom field needs to be in the destination org before you copy the Form Handler.
  • When copied, the Success Location and Error Location details will copy over to the new asset. Completion Actions do not copy over.

Now it’s even easier to work with Account Engagement Sandboxes!

This new Flow is a huge step toward making Account Engagement Sandboxes user-friendly for testing and staging. What other capabilities would you like to see in this Flow? Let us know in the comments!

Engagement Studio Programs (ESPs) are key for nurturing prospects until they are ready to send over to your sales team. But have you ever thought about A/B testing in ESPs?

ESPs allow you to automatically send your cold prospects awareness content and consistently stay top of mind so they can gradually warm up to a sales-ready stage. Although ESPs can be used for everything from basic email sends to complex process automations, one feature it lacks is native functionality for A/B testing. The feature exists natively (and wonderfully) for list emails, but in the realm of automated emails and ESPs, this is something marketers are chomping at the bit for. 

Let’s dig into some of the creative workarounds that make A/B testing possible in ESPs as well as the pros and cons of each option.

How does native A/B Testing work?

Within the native functionality of list emails, A/B testing is very user-friendly. You can:

  • Create and edit two versions of your email (Version A & B) via the WYSIWYG editor or by editing the HTML
  • Specify if the email versions should be measured by email opens or email clicks (we prefer clicks)
  • Determine the length of the A/B testing period (1 hour to 30 days)
  • Determine the percentage of your audience that is tested

Automating the A/B testing process

The beauty of A/B testing with list emails is that so much of the process is automated. 

Once the criteria have been set, Account Engagement automatically and randomly splits the test recipients from the intended recipient lists, sends the email variations to the test group, and, once a winner has been selected, automatically sends the winning version of the email to the remaining recipients on the list. 

This native functionality allows marketers to fine-tune their marketing content by testing which subject lines, CTAs, and even images best resonate with their target audience. 

A/B Testing in an ESP

To A/B Test in an ESP, you have a few options:

  1. Split your recipient list before starting the ESP
  2. Split recipients by last name
  3. Split recipient by a random number from Salesforce
  4. Split recipient lists using Prospect Updater

Using Native Split List Functionality

All Account Engagement Static and Dynamic lists can be split into smaller lists. While viewing your list, the split option will be available in the top right-hand corner. This allows you to split lists evenly, or specify the percentage on each list. 

It’s important to remember that when splitting a dynamic list, the resulting lists will be static. 

When using this option in an ESP, add an Action node before your email send that checks if the recipient is on split list 1. If they are a member of this list, they receive version A of your email. If they are not, they receive version B.

This option works best when your ESP has a static recipient list that you are not adding to later, for example, an event follow-up nurture. If you intend on gradually adding more prospects to this ESP, there isn’t a way to easily and automatically split the new prospects between the two lists. 

Splitting by Last Name

Another strategy is to split the recipients by last name. This allows you to split recipients with dynamic lists so you can continually add new recipients to the ESP. To do so, you’ll need two dynamic lists. 

Your first list will capture prospects with last names starting with A-M:  

Your second list will capture any prospects with last names beginning with N-Z, as well as any prospects with last names that start with characters, non-English letters, or numbers. 

Finally, use these lists to split ESP recipients between your email variations. 

Things to keep in mind

The drawback to this solution is that splitting by last name is not likely to evenly split your recipients. S, B, H, M, and C are the most common initials for last names, so if you split your recipients by “last name begins with A-M” and “last name begins with N-Z”, the “A-M” list is likely to be larger and can skew your data.

Generate a Random Number in Salesforce 

Another strategy for randomly splitting your recipient list is by using Salesforce’s Auto Number functionality. This allows you to auto-generate a random number for each Lead or Contact and push this data down to Account Engagement.

  1. In Salesforce Setup, select Object Manager then Lead
  2. Select Fields & Relationships
  3. Select New
  4. Select Auto Number then Next
  5. Enter the following details
    1. Field Label: Lead Random Number
    2. Display Format: {00}
    3. Starting Number: 0
    4. Generate Auto Number for existing records: Selected
  1. Select Next
  2. Select which profiles have access to view this field.
  3. Select Next
  4. Select any Lead pages where this field should appear. I recommend leaving this field off your page layouts. Select Save.
  5. Next, create a Formula field. While still in the Fields & Relationships tab of the Lead object, select New
  6. Select Formula, then Next
  7. Enter the following details
    • Field Label: Email Random Number
    • Formula Return Type: Number
    • Options – Decimal Places: 0
  8. Select Next
  9. Enter the formula MOD(VALUE({! Lead_Random_Number__c}) ,9)
  10. Select Next
  11. Select which profiles have access to view this field. Ensure the B2BMA Integration User profile, or your connector user’s profile, has access so Account Engagement can map to this field. 
  12. Select Next
  13. Select any Lead pages where this field should appear. I recommend leaving this field off your page layouts. Select Save.

This formula field will auto-generate a random number between 1-9 for each Lead. Optionally, repeat the steps above for the Contact object. Finally, map the “Email Random Number” field to Account Engagement so this new field can be used to randomly split ESP recipients for an A/B Test. 

Now, the only downside of this approach is that all your Account Engagement prospects must be synced to Salesforce before they will get an Email Random Number value. If you regularly nurture prospects in Account Engagement before syncing them over to Salesforce, you could use a combination of the Random Number and Last Name methods, or you can move to our last option.

Use Prospect Updater

Sercante’s Prospect Updater is a Swiss army knife for advanced data updates, cleansing, and manipulation within Account Engagement. This solution allows you to work with your prospect data in more streamlined ways and enables you to create a truly random recipient list split without your data being in Salesforce. 

With Prospect Updater, you can use a RANDBETWEEN function to auto-generate a random number and stamp the number on new prospect records within minutes of them being added to Account Engagement. Then, use an Action node in an ESP to split your prospects into your A/B test groups. 

If you want to learn more about Prospect Updater, check out our Supercharge sales ‘speed to lead’ with clean Pardot data and Creating a Pardot Spam Identification Process with Prospect Updater blog posts or contact us!

Selecting a Winner

After you’ve selected your method of A/B testing and let your ESP run, it’s time to choose a winner and, optionally, consolidate your ESP down to 1 email version. The best way to compare the data between your A and B email versions is by using the ESP reporting tooltips. While on the Reporting tab of your ESP, select the email send node to view the metrics for that particular send. 

The tooltips allow you to easily view the number of sends and opens as well as your click-through rate. If you want to dive deeper into each template’s metrics, select the name of the template from within the tooltip view to open the full email template report. 

Start A/B testing in Engagement Studio Programs

It’s clear that Engagement Studio Programs (ESPs) are the backbone of effective prospect nurturing, guiding them along the journey until they’re ripe for the sales pitch. 

So, let’s embrace the challenge, get creative, and make the most of our ESPs. With a bit of ingenuity and a keen eye on the metrics, we can craft killer campaigns that resonate with our audience and drive those all-important conversions. Here’s to pushing the boundaries and unleashing the full potential of our ESPs.

Remember, you can always reach out to the team at Sercante for help setting up your Account Engagement (Pardot) Engagement Studio Programs and configuring your A/B tests within them.

Salesforce tasks are one of the unsung heroes of Account Engagement. You can use Salesforce tasks to let the sales team know there’s work to be done, and using tasks can eliminate one of the common arguments for creating duplicate leads.

Yet, many are unhappy with the rigid options for creating tasks through Account Engagement. That leads us to our solution. We can make tasks even better, perfectly better in fact! We can make Salesforce tasks that are set up exactly how we want through Account Engagement using an External Action.

External Actions are a way to make things happen outside Account Engagement via Salesforce CRM Flow and APEX code.  We can create an External Action that creates a task with what we want in it and our merge fields in the body of the task comment so we can capture exactly what was on a form fill.

Process Overview: Creating custom Salesforce tasks with Account Engagement External Actions

Normally we would add a completion action to a form called “Create Salesforce Task,” which prompts us for a few rigid text fields that don’t support merge fields. 


Now we can add an ‘External Action’ for creating a task that has as few or as many fields as we want and allows us to add merge fields. 

Building this new Create Salesforce Task external action

There are a few steps we need to follow to build this. We start in the CRM and work backwards, toward Account Engagement.

Here’s the order you’ll complete the steps:

  1. Create a flow.
  2. Create an External Activity.
  3. Create the completion action.

Creating the Flow

First, we want to create an Autolaunched Flow.

Create variables

Next, let’s create some variables. The RecordID is the only required variable. (We need to attach the task to something). The rest of the variables are optional, but having them will give us more flexibility when we create the completion action.  All variables should have the ‘Available for Input’ checkbox checked. 

VariableData TypeRequired
RecordIDTextYES
Product_InterestTextNO
Task_InstructionsTextNO
Form_CommentsTextNO
Task_SubjectTextNO

Build the Flow

After creating the variables, we can get build the Flow. Start with the Decision Element to create a different path for Leads vs. Contacts. We’ll need to look up the record owner in the CRM, as Account Engagement doesn’t give us access to that as a merge field. To do this, we need to know whether to look up a Lead or Contact record. Use the table below to set up your lead path filter.

FieldOperatorValue
RecordIDStarts withOOQ

Update the label for the default path to “Contact”.

Add a ‘Get Records’ element

For each path, we will need to add a ‘Get Records’ element.  Select the correct object and then set the following filter:

FieldOperatorValue
IDEQUALSRecord ID

Create task details

Next, let’s create the task details. Start by creating another variable using the details below. Do not check the “available for input” box for this variable. 

Variable NameData TypeObject
NewTaskRecordRecordTask

Add an Assignment element

Then, add an Assignment element for each path to fill in the details. The Assigned To ID for the new task is the record owner from the object we looked up. Lead owner ID if it was a lead, Contact OwnerID if it was a contact.

Optional Step: Description formula

For the description, we can use a formula to put together the description that we want using a combination of our other variables.  To do this, create another variable with the type “formula”. Name it “FormattedText” and input this as the formula: “{!Task_Instructions}BR(){!Form_Comments}”

This will update the description field on the task to display the information inputted from Task Instructions and Form Comments. You can input a formula to include the variable values that are important to you. See another example in the screenshot below.

Create task record

Our last step in the flow will be to create the task record. Use the “Create record” element and add the variable “NewTaskRecord” under the “record” drop-down. Leave the other settings as is.

Flow is complete

When you are complete, your flow should look like this:

Your flow is complete. You can debug using an existing record. You will need to activate the flow before moving on to the next step.  

Marketing Extensions External Action

Next we want to create the External Action. Be careful with these,  we can’t currently delete any we make by mistake. If you have access to an Account Engagement Sandbox, this could be a good time to use it when building your first External Action.

Create a new Extension

In Marketing Setup> Marketing App Extensions, we will want to create a new Extension.  Name it “Create Task” and select the box “Active in Automation”.  

Create a new Action Type

Once it’s created, go to the Related Tab, and create a new “Action Type”.

Name it “Create Task” and Search for the flow we just created under “Invocable Action”. The flow must be activated.  Check the box for “active in automations” . 

The Action Type will write an Action Schema for us. We can simply click save, and we are done.

Optional Step: Adjust default details

We can also adjust the default details, providing Account Engagement default merge fields, and reordering the fields in the ‘view’ section, and even making fields required, such as our RecordID field. These adjustments can make our new tool easier to use! In the screenshot below, we’ve added in the merge field for RecordID so that we do not have to have our end users do this in Account Engagement.

Select business unit

Under the related tab, select “New” under Business Unit Assignments. Search for your business unit name and select it.  If you are unsure of your business unit name, go to Marketing Setup > Business UnitSetup.

Completion Action

Now we can use our shiny new Task!

Finalize with completion action option

When our Marketing App Extensions have all the bits ‘Active’ and we have assigned our business unit, we will get a new Completion Action option on forms and Engagement Studio Programs.

Fill in all the fields

This is where we can fill in all the fields we created as flow variables. We can use Account Engagement merge fields to fill them in, or just start typing text. Or a bit of both!

If you look at the ‘Task_Instructions’ in this example, you can see we can fill in text with a bunch of merge fields. Those merge fields are other completion actions on a form.

Start Creating Custom Tasks!

We used to be able to create a task and only have a generic “Follow up with this Contact” in the description. With custom tasks, the descriptions can now be populated dynamically with the exact information that prospects input on a form.  

Tasks can hold custom information like support questions or product interests, which can help streamline the next steps for the users receiving the task. So if your sales team is getting the tasks sent to them, then they can check the task to understand the best route to take.

Need help understanding how external actions and Salesforce tasks fit into your overall business strategy? Reach out to the team at Sercante to start a conversation.

Thank you to Mike Creuzer for contributing his expertise to write this post!

Are you ready to ignite your digital marketing efforts? The collaboration between Marketing Cloud Account Engagement and Advertising Audiences, both powerful tools in their own right, will skyrocket your success in digital marketing. In this blog post, we’ll show you how Account Engagement and Advertising are powerful tools when they’re coupled with one another.

Marketing Cloud Account Engagement

Account Engagement is the Salesforce B2B marketing automation software. Its main uses are account-based marketing, cross-channel campaigns, and lead generation. And though it does so much more than that to optimize your marketing efforts and provide out-of-this-world analytics, it cannot help you run your digital advertising campaigns. 

Marketing Cloud Advertising

Advertising Audiences, powered by Marketing Cloud Advertising, seamlessly integrates with online advertising platforms, including social media, Google Ads, and more, to target your Prospects specifically. It enables marketers to easily reach existing customers, generate new leads, suppress a subset of Prospects, and re-engage. 

This all sounds great, right? Absolutely! But wouldn’t it be cool if your advertising efforts were linked to your marketing automation efforts? 

Why should I connect Account Engagement with Advertising Audiences?

That’s easy! Pairing these tools can help you to automate your processes, improve cross-channel campaigns, and expand your footprint. Who doesn’t want this for their business?

Automate Processes

Getting leads from social media campaigns is often a manual process of exporting and importing. Bleh! Who has time for that? With this integration,  you can automate lead transfers directly from your social media and paid ad campaigns to Account Engagement. This also lessens the chance of human error and ensures that you are staying within legal guidelines at a global level.

Improve Campaigns

There are many digital touchpoints: email, Facebook, LinkedIn, Instagram, Google Ads, etc. With Account Engagement and Advertising Audiences, you can unite all of these touch points into a centralized hub and be able to track and report on them seamlessly. This combo gives you a more accurate preview of sources and measures of what is and isn’t working for your company. It also allows you to use first-party data to create and target lookalike audiences, improving your chances of getting new leads.

Expand Your Footprint

When running campaigns via media buys and email, you can now target and re-engage inactive Prospects, target Prospects based on behavior, and enable exclusions based on data, demographics, or purchase history. And this is all done in real time. Does this not seem like a great return on investment?

I’m ready to launch Advertising and Account Engagement. How do I make this happen?

The setup can be cumbersome and often requires work with a Salesforce Partner, but it’s quite straightforward if you are comfortable in the Salesforce ecosystem. 

The good news is that it’s done once it is in place. It’s all about building new audiences or tweaking existing audiences from then on. 

You will need access to Sales Cloud, Marketing Cloud Account Engagement, and Marketing Cloud Advertising to get started. You will also need to ensure that all connectors are active. 

Here’s a high-level look at what it takes to get this launched:

Sales Cloud

  1. Create a Salesforce Campaign
  2. Build a Salesforce Report

Account Engagement

  1. Build automation(s) to populate your audience(s):
    • Automation Rule
    • Page Actions
    • Completion Actions
    • Engagement Studio

Advertising Audiences

  1. Generate a Data Import
  2. Create an Automation
  3. Build your Audience

If you are ready to expand your digital footprint, the obvious next step is having all the tools you need at your fingertips. The power of Account Engagement combined with Advertising Audiences is among the most effective tools. 

To learn more about the implementation process, click here. Need help? Contact Sercante to learn more.

Recently I was perusing the Salesforce IdeaExchange for interesting features to upvote and came across a common issue with over 4k upvotes, “Automate contact owner update when account owner changes.” 

Now, I would LOVE for this to be a native Salesforce feature of course, but there is a simple solution to this that I couldn’t find documented anywhere. 

So let’s get to it!

The problem with Account and Contact Owner mismatches 

Depending on how your sales team manages Account and Contacts, Account and Contact Owner mismatches can cause a lot of headaches. 

In most Salesforce orgs I’ve worked with, the Account Owner is responsible for nurturing all Contacts within the Account, but if Sales Rep A owns the Account and Sales Rep B owns half of the Contacts under the Account it can cause issues.

Those issues include:

  • Sales Rep A missing Contacts when viewing reports
  • Account Engagement “Create Salesforce Task” completion actions get assigned to the wrong user
  • Contact Activities get missed by the Salesperson who needs to act on them
  • Multiple Sales reps nurturing the same Contact at the same time

To solve for this common issue we’re going to build two items:

  1. Formula Field on the Contact
  2. Schedule-Triggered Flow for Contacts

Identify Owner Mismatches

The first step is identifying records with an Account and Contact Owner mismatch. To do so, we want to build a Formula Checkbox field.

  1. Navigate to Setup > Object Manager > Contact > Fields & Relationships
  2. Select New
  3. Choose Formula, then Next
  4. Name the field “Owner Mismatch”
  5. Select Checkbox, then Next
  6. For the Formula, enter “IF((Account.OwnerId = OwnerId), FALSE,TRUE)”
    • If you are not familiar with Salesforce formulas, what this essentially says is if the Account Owner’s ID equals the Contact Owner’s ID the checkbox should be False, or unchecked. If the two Owner IDs do not match, the checkbox should be True, or checked. 
  7. Enter an Description so other users know what this field is for, and select Next
  8. Select the users who should have access to this field and the page layouts you’d like the fields added to, then select Save

Automatically Update Contact Owners

Next, we’ll create a flow to automatically update your Contact Owner to match your Account Owner. This flow is very simple, so don’t abandon ship if you are not yet a Flow super user!

  1. Navigate to Setup > Flows
  2. Select New Flow
  3. Select Schedule-Triggered Flow
  4. Fill in the “Set a Schedule” details as below
    • Start Date: Today’s date
    • Start Time: I recommend you set this flow to run outside of business hours. For my flow, I chose 12:00 AM
    • Frequency: Daily
  1. Next, select + Choose Object
  2. Fill in the Configure Start details outlined below
  3. Select Contact
  4. Enter the condition as below
    • Field: Owner_Mismatch__c
    • Operator: Equals
    • Value: True
  1. Under your Start element, select the plus symbol to add a new element
  2. Select Update Records
  3. Label the Element “Update Contact Owner”
  4. Under “Set Field Values for the Contact Record” set the Field to OwnerID and set the Value to {!$Record.Account.OwnerId}
  1. Select Done
  2. Select Save from the top right hand corner and name your Flow “Contact – Update Owner to Match Account”
  1. Select Save
  2. Finally, Debug your Flow to ensure it works as expected, then Activate it! 

Now sit back and let everyone marvel at how clean Account and Contact owners are in the org. 

Get more solutions like this from Sercante

Need help figuring it all out? Reach out to the team at Sercante to get a conversation going.

If you’re new to Marketing Cloud Engagement, you may be feeling overwhelmed. Salesforce’s powerful marketing platform can do a lot. And that comes with a steep learning curve.

I’ve been on my Marketing Cloud Engagement journey for a while now and still feel the sense of having so much to learn. My learning journey has consisted of hands-on experience, boot camp-style training courses, and of course, all the Trailheads. 

Florida Dreamin’ Session – How to Write like a Marketer: Intro to AMPscript for Salesforce Marketing Cloud

I knew when I was given the opportunity to attend this year’s Florida Dreamin’, finding Marketing Cloud Engagement sessions was at the top of my event bucket list. That’s why I was super excited to attend Tatiana Romanko’s presentation, How to Write like a Marketer: Intro to AMPscript for Salesforce Marketing Cloud.  

Romanko took a complex topic and simplified it, making her content easy to understand by providing real-world use cases every marketer could relate to. This session was a great introduction to AMPSprcipt for Marketing Cloud Engagement users who are still on that learning curve, and even seasoned veterans took away a thing or two. 

What I especially loved about her session is that, like me, Romanko doesn’t have a coding background. Her message really resonated with me: with hard work and hands-on experience, you too can learn the technical intricacies of Salesforce Marketing Cloud. 

What is AMPScript? 

Before jumping right into a complex topic, Romanko set the stage with a quick introduction to AMPscript. “AMPscript is Marketing Cloud’s proprietary scripting language for advanced dynamic content in emails, landing pages, SMS, and push messages.”

“AMPscript expands Marketing Cloud functionality to help you create the one-to-one, personalized communications that are so coveted by digital marketers. https://trailhead.salesforce.com/content/learn/modules/ampscript-for-nondevelopers/get-to-know-ampscript) 

AMPscript is used to:

  • Personalize emails using subscriber or contact data.
  • Create complex, highly dynamic emails using conditional logic.
  • Clean and format data.
  • Add real-time information to emails such as date or time.
  • Track impressions.”

(source: https://trailhead.salesforce.com/content/learn/modules/ampscript-for-nondevelopers/get-to-know-ampscript) 

What is AMPScript used for in Marketing Cloud Engagement?

AMPScript does a lot. At Sercante, we use it to help our clients with personalizing their emails, creating dynamic content, and much more. What I liked about Romanko’s session is that she really honed in on three common use cases that every marketer can relate to. 

Personalization

If you’re a marketer, you already know the power of personalization. One study found that emails featuring personalized subjects are 50% more likely to be opened. AMPScript in Marketing Cloud Engagement allows you to use your subscriber data to personalize your marketing. 

Creating a personalized greeting in Marketing Cloud Engagement through a personalization string isn’t complicated. What I liked about Romanko’s use case is she focused on something I often times see clients overlook: what happens when you don’t have a subscriber’s first name? In this case, we could use AMPscript to set a generic value (Customer) as our greeting if we don’t have this data. 

Formatting Your Data

As a marketer, I’ve seen customers input their data in every way imaginable. Romanko gave the example of asking someone to provide their favorite color. In this instance, we could get a few different variations: 

  • Pink
  • pink
  • PINK

So what happens when we go to pull this data into an email? It could end up looking like we either don’t know our basic grammar, or come across like we are YELLING at our reader. 

Romanko highlighted AMPScript’s ProperCase function here, “which capitalizes the first letter in the specified string and any other letters in the string that follow any character other than a letter. It converts all other letters into lowercase.”

AMPScript Resources

As you can see, Romanko gave some great use cases for using AMPScript. She also provided her audience with some really great resources on where to go to learn more:

Soak in all the lessons learned at Florida Dreamin’

Be sure to check out these other posts from my fellow dragons who attended Florida Dreamin’ with me and shared details about their favorite sessions there.

No more posts to show