Standard Integration Design Pattern using App / API?

[Anonymous]

Hi,

I am currently working on a project to design and build an integration between Marketo and our Webcast platform.

I have successfully integrated Marketo Forms with our Webinar Registration process using Webhooks.

I now need to design an integration solution to get our Contact and Event data in to Marketo after the Webcast event.

I am looking for some advice on the best / most common way to integrate our type of product.

Below are a few questions I have:-

Do we need to have a connector App in order to appear in the Marketo App store? If so, what do these Apps normally do (e.g. some kind of Auth or Field Mapping)?

Do most solutions push data in to Marketo via the API after some initial setup via the App or does the App itself perform the passing of data. If the App passes the data is this normally setup as an automatic timed event or as a manual process.

Any help would be greatly appreciated.

Thanks

[Josh_Hill13]

You should visit developers.marketo.com for API information. This would be the most efficient method. Yes, you could potentially use a third party data routing tool, but that will slow you down.

Why are you building a custom integration? Is this something you plan to sell?

[Kenny_Elkington]

Hey Stewart,

You can get the partnership process started here: Launchpoint - Become a Partner  As far as your other questions:

• It's typical for time-based events to push or pull data based on the relevant time frame
• Many solutions have specific custom field requirements to push data to in an instance if that data is provider-specific, in other cases it may be to standard fields or a user-defined mapping.

Not sure what you mean by this though, care to clarify?

>If so, what do these Apps normally do (e.g. some kind of Auth or Field Mapping)?