Sync Custom Object Fields with Revenue Explorer? | Community
Skip to main content
March 13, 2017
Solved

Sync Custom Object Fields with Revenue Explorer?

  • March 13, 2017
  • 1 reply
  • 2416 views

I saw a thread on the community from last year (Custom Objects and Revenue Cycle Explorer ) that confirmed you can't integrate Custom Object fields in Revenue Explore, but that it might be an upcoming feature. Does anyone know if its still the case that you cant or if this can now be done?

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 Grégoire_Miche2

Hi Selene,

No, this is still not possible.

-Greg

1 reply

Grégoire_Miche2
Grégoire_Miche2Accepted solution
New Participant
March 13, 2017

Hi Selene,

No, this is still not possible.

-Greg

Grégoire_Miche2
New Participant
March 13, 2017

Hi again Selene Regan ,

to provide you with some details;

  • Simply put, custom objects are cannot be sent to the revenue explorer. They are useful for quite a few things such as being in included in emails using velocity scripts, but not for adding dimensions to the reporting
  • Opportunity is therefore a better choice, excepted that you will not be able to add opportunity fields to the Marketo schema (and not to the Rev Exp data schema neither) if you are not using SFDC or Dynamics CRM. Adding custom oppy fields to Marketo is only possible when the fields are created in the CRM and mapped to Marketo using the corresponding CRM conector. But it is impossible to add opportunity fields to Marketo schema through the admin, neither it is through the API.

-Greg

March 13, 2017

Greg, Many thanks for this, much appreciated. To confirm, they are using Sugar and the Sugar connector allows custom fields in Sugar to exist in MKTO on Lead and Contact. So is it the case that the Sugar Integration to MKTO also allows custom Opportunity fields to be synched to MKTO as well as Standard opp fields, as you only mentioned SFDC & Dynamics CRM as being able to do this in your response