Should I use Opportunity Object or Custom Object?

[Anonymous]

Hi there. I have a B2C client in the professional sports industry and have the opportunity to import individual ticket purchase transactions (via API) into Marketo. Since it's not a typical B2B sales pipeline scenario, I've considered using a custom object to store all the transactions of each member on our database. However I'm not clear whether that would exclude us from using the Marketo Revenue Cycle analysis tools. Does revenue data, by definition, need to come from the Opportunities object?  If so, should I be looking to import these transactions into the Opportunity Object instead.  Trouble is, that I would need to introduce custom fields to include the metadata of the various sports events on offer. Is it possible to do that without using SFDC?  Any assistance on this would be very welcome.

[Grégoire_Miche2 · Accepted solution]

Hi Paul,

First thing, you should not post your questions to the "Champions" group as you are less likely to get and answer. See Getting the most of the community when you have a Marketo question

Now:

• Yes, the revenue have to come from the opportunity object in order to be used in all the Revenu cycle reporting.
• There is an opportunity REST API. See http://developers.marketo.com/documentation/opportunity-api/ ​ The key point is that it will be accessible ONLY if you have not sync'ed Marketo with SFDC nor Dynamics.
• The second hard point is that, for the moment, you cannot add fields to the opportunity object. AFAIK, you can ask support to add some.
• And vote here:

So I do not think there is really a solution that can encompasses all your requirements.

-Greg

[Anonymous]

Thanks Gregoire. Confirmed my suspicions. Yep will post into "Products" from now on and ignore Marketo's "suggested" places to post.