pastedImage_1.png

Special Salesforce Fields/Tokens in Marketo Deep Dive

Brian_Law_MKTO
Marketo Employee
Marketo Employee

Here are some Salesforce-related system fields/tokens that will be available in Marketo automatically when you setup the sync.

 

Field

Description

Available in Marketo as a Filter in a Smart List

Marketo Token

SFDC Id

The 18-character Salesforce Id

No. The token also can't be used in a Change Data Value flow step. The token can only be used in an email.

{{lead.SFDC Id}}

SFDC Type

Lead or Contact. If empty, the record only exists in Marketo.

Yes

{{lead.SFDC Type}}

SFDC Created Date

Date created in SFDC (Value is different than “Created” in Marketo).

Yes

{{lead.SFDC Created Date}}

SFDC is Deleted

SFDC Lead or Contact used to be in SFDC but was deleted and now only lives in Marketo

Yes

{{lead.SFDC Is Deleted}}

Email Bounced Date

Date record bounced in SFDC Yes {{lead.Email Bounced Date}}

Email Bounced Reason

Reason record bounced in SFDC Yes {{lead.Email Bounced Reason}}

 

SFDC Type: Marketo will automatically change the SFDC Type of a record from Lead to Contact when a record is converted in SFDC.

 

 

You can use the Lead was Converted filter to search for records which have been converted during a specific time frame.

 

pastedImage_1.png

 

 

SFDC Created Date: If you see a record where the SFDC Created Date is before the Created date in Marketo it means the record was created first in SFDC and then synced to Marketo. During your initial sync the Created date of the records syncing will be around the date you started the sync. If you have a custom sync rule in place and only insert records from SFDC once they qualify based on your rules, the SFDC Created Date can be weeks, months or years different than the Created date in Marketo.

 

 

Since the SFDC Created Date and the Created date in Marketo are both date/time fields, I recommend always creating date/time vs a date field so you have the option of using the {{lead.SFDC Created Date}} or {{lead.Created At}} tokens along with the {{system.dateTime}} token in a Change Data Value flow step. You can't use a token from a date field in a date/time field.

 

 

The Created At field is the date the record was created in Marketo. This field is called "Created" in a smart list view or when you view the actual record.

 

 

SFDC is Deleted: Records deleted in SFDC are not automatically deleted in Marketo. There’s a field in Marketo called SFDC is Deleted and it is set as false until the record is deleted in SFDC.  You can run regular batch campaigns to delete these records from Marketo.

 

 

If you later attempt to resync the lead to SFDC using for example the Sync to SFDC flow step, a new lead record will be created there and the "SFDC is Deleted" flag will be set back to false. Since this record is new all previous SFDC information such as activities, tasks, campaigns will no longer be included. The SFDC Created Date in Marketo will be updated to the new date.

 

 

There are two filters in Marketo for finding SFDC Deleted Records:

  • SFDC is Deleted - True/False: I recommend including this boolean field when running reports on SFDC records to get a more accurate count of the number of SFDC records you have in Marketo.
  • Lead Was Deleted from SFDC: Allows you to add the constraint of a date and/or a minimum number of times the record was deleted.

 

Additional resources for learning about the Marketo integration with SFDC.

2274
8
8 Comments
Anonymous
Not applicable

Great post, must read for every admin.

I've been trying to tackle the SFDC ID in Smart List/Filter with some sort of workaround. No such luck yet...

The ask from sales enablement was to copy the original SFDC ID to a new field where as to make further connections to leads/contacts after conversion inside a data warehouse.

As of now I've stated this should just be taken care of in SFDC, but do you have any thoughts around how this might be possible in Marketo? Webhook maybe?

Brian_Law_MKTO
Marketo Employee

Hi Tim, great question. I clarified in my article how the SFDC ID tokens can be used. The tokens can be used in an email. The tokens can't be used in a Change Data Value flow step so I am unaware of solution to your question.

Grégoire_Miche2
Level 10

HI Tim,

In SFDC, even converted leads can be accessed through API or reporting, with, for each converted lead, the possibility to retrieve the converted contact and converted account. IMHO, your data warehouse should leverage this functionality, and not rely on Marketo to provide the info.

Otherwise, you could use a formula field on SFDC and free text field on contact. The formula field will just be a replica of the ID (15 characters only, but this is enough to retrieve records). then you map these 2 fields. On conversion, the lead IS will be visible in the contact.

-Greg

Anonymous
Not applicable

Thanks Greg, as of today we are doing option two of formula field inside SFDC for what were trying to accomplish reporting wise.

Anonymous
Not applicable

Great post!

And I think this Marketo token is very useful too when you want to insert SFDC links to marketo email.(mainly used in internal alert email)

{{SP_Send_Alert_Info}}

Anonymous
Not applicable

Hi Brian, great post! I have one question regarding the {{lead.SFDC Created Date}} - do you know if you can use this field in a wait step? We are setting up a series of emails and want to send out the email based on the lead's SFDC created date + X number of days. Thanks!

Brian_Law_MKTO
Marketo Employee

Hi, I haven't tried it in the advanced wait step but it will probably work. Remember the advanced wait step with a token needs to be in a triggered campaign, not batch.

Anonymous
Not applicable

Thanks, we actually just tried it in a trigger campaign and it works for us.