Marketo <> SFDC Post Sync Issue. | Community
Skip to main content
A
Anonymous
December 13, 2015
Question

Marketo <> SFDC Post Sync Issue.

  • December 13, 2015
  • 3 replies
  • 1912 views

Hi All,

We have identified an issue related to multiple deals (opportunities) associated with one contact. For example if prabashr@babajob.com has 3 jobs (Job1, Job2, Job3) currently active in SFDC instance, Marketo is creating three different records for each job with the  same email id. So it will be like:

prabashr@babajob.com     J1    

prabashr@babajob.com     J2    

prabashr@babajob.com      J3   

We would like to have merge these 3 separate records into one record with email id. So it should be like

prabashr@babajob.com   J1            J2               J3

Could you please suggest a solution for this?

Will there be any involvement of Marketo Custom Objects for this issue to be resolved ? This issue is kind of urgent for our company to resolve and get going with the operations.

Awaiting quick help form you people !

Thanks a lot !

-Prabash Rath

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

3 replies

Grégoire_Miche2
Grégoire_Miche2
Level 10
December 13, 2015

Hi Prabash,

What are you calling a Job ? Is this the opportunity object that you have renamed (#1) ? Is this a custom object linked to one of the 3 (#2) ? Is this a Field in the contact, account or lead (#3) ? 

  • The #1 is seamless. If it's an opportunity, when you will have merged the 3 contacts, the resulting one will be linked to the 3 opportuntities
  • The #2 is a quite seamless : you just have to map the custom object in Marketo and merge the 3 contacts
  • The #3 is more complex : if you do a simple merge, you will keep only one value. The solution depends on how solid vs simple you want the solution to be:
    • You could create a "Job" custom object in SFDC and map it to Marketo. in this case, you will be back to case #2. In order to populate the custom objects, you will have to export the database before merge, the reimport the custom objects in SFDC, using the email address as a mapping field
    • Or you can export the database, merge the 3 values in one column outside the database (excel...) merge in SFDC and reimport the 3 values.

-Greg

    A
    Anonymous
    December 13, 2015

    Hi Gregoire,

    Our company deals with recruiters posting available jobs/vacancies with them and we then connect these recruiters and probable appropriate job seekers according to the job posted details. One recruiter can have multiple job postings on our website.

    So basically, this 'Job' is a custom field in our SFDC instance which has the job and other relevant details and statuses and is linked to the contact role. Since, one recruiter can have multiple job postings, there are more than One Job with the same contact (i.e., the same email ID) in SFDC.

    We synced this Salesforce Custom Object with our Marketo instance, and found out that there are multiple lead records (with the same email ID) in our Marketo DB like the example I have listed above. Having these multiple records with the same contact details, will create problems for us to run programs and removing duplicates in Marketo going further down the stage.

    Hence, I am looking for a solution in such a way that, the multiple jobs linked to one contact OR email ID in SFDC come in as only lead record in Marketo with its multiple job posted details.

    How do you suggest I go about to achieve the same  ?

    Thanks again !

    -Prabash Rath

    Grégoire_Miche2
    Grégoire_Miche2
    Level 10
    December 13, 2015

    Hi Prabash,

    Your post is not clear : you are talking first about a custom field and then about a custom objects. These are 2 very different things in SFDC.

    Provided you are not running Marketo Spark, as explained in my earlier post, if this is a field in SFDC, you should replace it with a "Job" custom object in SFDC.

    If this is already a custom object, just let it as is.

    IMPORTANT : You just need to make sure that the Job custom object has a relationship to the contact, which has to take the form of a lookup or master detail field in the JOB custom object and targeting the contact. This will enable a 1-n relations ship. Pay attention that it is not the other way around (a field in contact that links to the job), in which case it will not work.

    This custom object itself may have other fields (for relevant details and statuses).

    Finally, you will have to map the Job custom object in Marketo. This is done in Admin->Salesforce object sync. The docs ought to be here SFDC Sync: Custom Object Sync - Marketo Docs - Product Docs  but the page is empty . Nevertheless, it is quite straightforward and if you search the community, I already wrote about how to do this.

    The Marketo mapping will create a few filters (such as "was added to a Job", "has Job") and triggers ("added to a Job") in Marketo and you will be able to use custom object fields as constraint.

    Once all this is done and you have populated the custom object with all the jobs in SFDC, you can merge the contacts in SFDC. If you merge 2 contacts with 1 linked job each, you will end up with 1 contact with 2 linked jobs. And this will reflect to Marketo perfectly well and automatically.

    -Greg

      Josh_Hill13
      Josh_Hill13
      Level 10
      December 13, 2015

      Greg has been very detailed with the help here. However, I suggest that this is a complex issue that if you cannot resolve on the basis of Greg's suggestions, you may want to seek out an SFDC developer and hire that person for this resolution.

        A
        Anonymous
        December 14, 2015

        Hi Prabash,

        Your question is 2 fold (as I understand).

        1> How to set up the SFDC -  Marketo framework so it will work as you intended.

        and

        2> How to get the existing 'duplicates' data in the new framework you set up in 1.

        Let's talk about 1> first. From my understanding Gregorie explained it very well in his reply on Dec 13, 2015 6:42 AM .

        SFDC Contact

        id, email address, first name, last name ........

        You have a SFDC custom object 'Job'.

        SFDC Jobs

        Job_id (unique), SFDC_contact_id (reference to SFDC contact table), job title, job open date ........

        SFDC Jobs object can have 'n' number of jobs having same contact id.

        If in SFDC's custom object 'Jobs', two separate jobs get created; namely Software Engineer with jobid 123 and Product Architect with jobid 999 for example. These two job objects have contact details as prabashr@babajob.com separately for both of them. Thus both of these 'jobs' object entries have the 'contact id' of SFDC contact 'prabashr@babajob.com'

        Then you need to 'replicate' similar setup in Marketo too. Let's say you setup a custom object 'Mkto_Jobs' in Marketo. Lets say, you will have a lead with email address 'prabashr@babajob.com' lets say with id xxxxx.

        Once you set up the 'custom object sync', these 2 'Jobs' entries will make it to Marketo and be stored in 'Mkto_Jobs' as 2 separate entries. Each of these 'Mkto_Jobs' entries will have 'Marketo lead id' value of xxxxx linking both of them to the 'same' Marketo lead xxxxx.

        Thus, if you want to send email for any of these jobs, you will use 'send email' to lead xxxxx. In the email, instead of merging {{lead.Job1}} OR {{lead.Job2}}, you will have to write Velocity Email script and get the correct job_id record and print the custom object token as ${Mkto_Jobs.get(0).Job_title}

        or

        $!{TriggerObject.Job_title}

        Which gets the 'triggering' object record. I.e. when a new job record is added or modified etc.

        A couple of months back we did exact similar kind of work and related workflows and there are some other gotcha's you might need to consider. Please feel free to reach out.

        Once you setup the framework, the merging of the existing data can be taken care of.

        Hope this helps

        Rajesh

        Terms & ConditionsAccessibility statement

        Loading footer...