Change the unique identifier from email address to a custom field.

[Anonymous]

Hi Sanford

You can insert/update leads based on another dedupe key, not Email Address, if you use the API.

To confirm, you are saying that we can insert or update Leads in Marketo, and they could have the same email address, as long as we identify another dedupe key.

Is that right ?

For example we want to have

Lead Id Con ID Email Name Interest

001 1 freshwjj@gmail.com<mailto:freshwjj@gmail.com> Jen Health

002 2 freshwjj@gmail.com<mailto:freshwjj@gmail.com> Rob Poverty

And be able to update the records Lead 001 or 002 independently

We have something called a ‘CON ID” which is unique to each record in our CRM. If we made that the dedupe key, could we use the REST API

Can we make that change – change the dedupe key now, with a populated Lead table ?

Cheers

Jen

Jennifer Freshwater | Project Co-ordinator | Oxfam Australia

132-138 Leicester Street, Carlton VIC 3053

Tel: +613 9289 951 | Fax: +613 9347 1725 | www.oxfam.org.au<http://www.oxfam.org.au/>

[SanfordWhiteman]

To confirm, you are saying that we can insert or update Leads in Marketo, and they could have the same email address, as long as we identify another dedupe key.

We have something called a ‘CON ID” which is unique to each record in our CRM. If we made that the dedupe key, could we use the REST API

Can we make that change – change the dedupe key now, with a populated Lead table ?

It's not a persistent change to the database, it's only a parameter of a REST API call. Marketo won't retain any memory of what you use for deduping in different scenarios, and you can use different dedupe keys for different tasks. There are restrictions on eligible data types but your String key will be fine.

[Anonymous]

Hi Sanford

I am following up on the first part of the question - above, with some information on that.

We are currently using POST /rest/v1/leads.json with ‘email’ as the lookup field and a ‘createOnly’ action.

Would it be possible to create new leads in Marketo by using a custom field like ‘oxConId’ as a lookup field?

Thanks

Jen

[SanfordWhiteman]

Why don't you test using a different lookup field, which currently has no matching leads, and see?

[Anonymous]

Sanford - Testing would be the trick here yes, but Developer time is scarce, it needs JSON knowledge & access to test environment to do that test.

Jennifer Freshwater | Project Co-ordinator | Oxfam Australia

132-138 Leicester Street, Carlton VIC 3053

Tel: +613 9289 951 | Fax: +613 9347 1725 | www.oxfam.org.au<http://www.oxfam.org.au/>

[SanfordWhiteman]

Well, it'll work as described, but obvs. should be tested internally as well. Shouldn't need a whole test environment to test insertion of a single lead (of course it's better to test things in a sandbox, but you're putting your instance in the same place day-to-day just by having lead forms).

[David_Everly]

Yes, here is an example of using a custom field as lookup field:

REQUEST

POST /rest/v1/leads.json

{

    "input": [

        {

        "oxConId": "2",

        "company":"Oxfam Australia",

        "title":"Project Co-ordinator",

        "firstName":"Jennifer",

        "lastName":"Freshwater"

        }

    ],

    "action":"createOnly",

    "lookupField":"oxConId"

}

RESPONSE

{

    "requestId": "6b77#15f4f9500ac",

    "result": [

        {

            "id": 318999,

            "status": "created"

        }

    ],

    "success": true

}