marketoGUID | Community
Skip to main content
Samantha_Cossum
Samantha_Cossum
New Participant
September 21, 2018
Solved

marketoGUID

  • September 21, 2018
  • 1 reply
  • 5793 views

Hi all,

This may be a silly question but I'm just getting into learning API call as my company may no longer be using a middleware to connect our Marketo and Netsuite instance. One of the challenges I'm facing is trying to figure out how to expose the Marketo GUID without have to pull it out from an API call. Is it stored someone where in Marketo that I can find it and I've just been missing it.

I appreciate any direction anyone can give me!

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 SanfordWhiteman

It's overly general, really, to talk about "Opportunities" alone.

Opportunities are one level away from leads in Marketo (as in most CRMs): they have a many-to-many relationship with leads and will not show up at the lead level unless there is at least one row in the Opportunity Role cross-reference (junction) table to bind the Lead table and Opportunity table together. Oppty Roles and Oppties have separate REST API endpoints. When you view an Opportunity via the Marketo UI or via Velocity, you're seeing a synthetic view that comprises both tables, with some fields taken from each table (for example, the Role is in the Opportunity Role table, while the Description is in the Opportunity table).

What I think you're driving at w/r/t the marketoGUID not being "exposed" is that you don't see it in the Marketo UI (nor, sometimes just as important, do you see it in the Velocity scripting context). This is unfortunately true, but what I've done to work around it is append the externalOpportunityId to the name of the Opportunity, so it shows in the UI:

You could do the same with the marketoGUID upon Opportunity creation, but it takes an extra API call that way.

I don't know what you mean by "sync everything through our SQL database" but you're going to be writing your own middleware, i.e. integration tier, to get this done. And that's a fine and often advisable project, but you shouldn't confuse it with not having middleware.

1 reply

SanfordWhiteman
SanfordWhiteman
New Participant
September 21, 2018

The GUID for what record? Activity or Custom Object?

Please explain exactly what you're trying to accomplish.

Samantha_Cossum
Samantha_CossumAuthor
New Participant
September 21, 2018

I'm specifically looking at Opportunities. We use Marketo and Netsuite and currently have Vertify as our middleware. We've had a lot of issues with Vertify and our CTO is trying to have us move away from the technology and sync everything through our SQL database. We have a dev team but they are not familiar with Marketo at all and they asked me to explore what was needed to create and update opportunity records through a REST API call. While digging around for a lot of the API stuff I've been seeing references to the GUID but haven't had much luck with exposing it unless I used a GET API call and used a different filter to pull up the record.

SanfordWhiteman
SanfordWhitemanAccepted solution
New Participant
September 22, 2018

It's overly general, really, to talk about "Opportunities" alone.

Opportunities are one level away from leads in Marketo (as in most CRMs): they have a many-to-many relationship with leads and will not show up at the lead level unless there is at least one row in the Opportunity Role cross-reference (junction) table to bind the Lead table and Opportunity table together. Oppty Roles and Oppties have separate REST API endpoints. When you view an Opportunity via the Marketo UI or via Velocity, you're seeing a synthetic view that comprises both tables, with some fields taken from each table (for example, the Role is in the Opportunity Role table, while the Description is in the Opportunity table).

What I think you're driving at w/r/t the marketoGUID not being "exposed" is that you don't see it in the Marketo UI (nor, sometimes just as important, do you see it in the Velocity scripting context). This is unfortunately true, but what I've done to work around it is append the externalOpportunityId to the name of the Opportunity, so it shows in the UI:

You could do the same with the marketoGUID upon Opportunity creation, but it takes an extra API call that way.

I don't know what you mean by "sync everything through our SQL database" but you're going to be writing your own middleware, i.e. integration tier, to get this done. And that's a fine and often advisable project, but you shouldn't confuse it with not having middleware.

Terms & ConditionsAccessibility statement

Loading footer...