List Building for Holiday Card for Marketo + SFDC Integration | Community
Skip to main content
G
gmarta
New Participant
November 27, 2023
Solved

List Building for Holiday Card for Marketo + SFDC Integration

  • November 27, 2023
  • 1 reply
  • 2372 views

We have an integration setup between Marketo and SFDC.  We need to send a Holiday card out.  Various sales teams have provided lists of recipients, email addresses, that should get the email.  All of these contacts/emails already exist in SFDC+Marketo database.  What’s the best way to use these to create email lists for the campaigns?

  1. Can I upload to Marketo as static lists and match those against the SFDC records?  I’m thinking this would create duplicates.
  2. Should I hand the lists to our SFDC admin and have her build the campaigns in SFDC?

 

Just trying to determine what a normal SOP should look like.  Thanks.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Jazmine_Moore

If you have a 1:1 bi-directional Marketo + SFDC sync, and all of the records are already in both systems, then you could:

1. Retrieve the recipient lists from the stakeholders, ensuring that the email addresses are included.

2. Consolidate the lists into 1 single Excel CSV.  The minimum required column here should be Email Address, as that is the unique identifier

3. Create a Marketo program

4. Sync to a SFDC campaign, or create a related SFDC campaign (depending on your SFDC campaign strategy)

5. Within the Marketo program, create a static list, "Recipients", and upload the recipients into the list.  Marketo will automatically deduplicate using the email address.

6. Reference this static list in your smart campaigns to update program/campaign status, send email, etc.

 

You will still need to consider the leads' privacy and communication settings.

 

 

1 reply

Jazmine_Moore
Jazmine_MooreAccepted solution
New Participant
November 27, 2023

If you have a 1:1 bi-directional Marketo + SFDC sync, and all of the records are already in both systems, then you could:

1. Retrieve the recipient lists from the stakeholders, ensuring that the email addresses are included.

2. Consolidate the lists into 1 single Excel CSV.  The minimum required column here should be Email Address, as that is the unique identifier

3. Create a Marketo program

4. Sync to a SFDC campaign, or create a related SFDC campaign (depending on your SFDC campaign strategy)

5. Within the Marketo program, create a static list, "Recipients", and upload the recipients into the list.  Marketo will automatically deduplicate using the email address.

6. Reference this static list in your smart campaigns to update program/campaign status, send email, etc.

 

You will still need to consider the leads' privacy and communication settings.

 

 

    G
    gmartaAuthor
    New Participant
    November 27, 2023

    Thank you, this is exactly what I was looking for.  That's the solution I was sort of fishing around, but I wasn't sure if it would create dupes.  So by using email address ONLY in the static list there is no confusion within Marketo.  

     

    What if I want to use a first name token?  I assume I still use a static list with email only and Marketo will automatically pull first name from the original record.  In other words, I would NOT have to have first and email in the static list, just email.

    C
    ChristianeRo1
    Community Manager
    November 27, 2023

    Marketo will dedupe on the email address, so provided that the email address already exists in Marketo, it will pull that record into your program and onto your static list -- which includes information on that record (First Name, Company, etc.), provided that information was synced from Salesforce.

     

    More info on Importing People into a List

     

    I would be very cautious on uploading additional information into Marketo (such as first name) if that information may already exist in Salesforce (and thus, Marketo). When you upload a static list, it can overwrite that information, depending on your field or import settings. I would trust your single source of truth (Salesforce) over an uploaded csv, and just be sure to have a good default value in your token. 

      Terms & ConditionsAccessibility statement

      Loading footer...