Erik_Heldebro2

No problem! Exactly, since there are a few fields (for example marketoGUID) that need to be referenced for the correct custom object to be updated.

Replied above to my previous comment.The data structure needs to be defined in order to update a custom object since the whole point is to create a small data model that you filter entries.If you were to be creating completely new definitions of Custom Objects via the API, you would probably risk a ...

Looking back at your post, it seems like you are trying to update a custom object that doesn't exist. The data structure needs to be defined in order to sync a custom object to a lead.The relationship is one-to-many/many-to-many meaning you can push multiple entries to a custom object on a lead and ...

Hmm, what does your post look like?Are you adding a custom object to the lead or are you trying to actually define a "whole new" custom object that has not been defined/approved in the Marketo Admin area?Edit: Have you created and approved a Custom Object in Admin like this? Create Marketo Custom Ob...

Hi Danielle,I think what you're looking for is more along the lines of syncing custom objects, /rest/v1/customobjects/{customObjectName}.json > check this one out. (Inserts, updates, or upserts custom object records to the target instance. Required Permissions: Read-Write Custom Object)As you can se...

I'm interested!

No problem, just giving my two cents on the topic Although, to be fair I think Episerver is great overall, but in terms of their Marketo connector it does not seem like anyone has done much with it since releasing it because it simply offers basic API integration.

Similar to Sanford's comments, I worked with this one with a client at my previous job.I sent over some recommendations to their dev support of how they can improve it. My issue with it was that it was not scalable with an example of a simple gated content form:Using one form block for multiple piec...

Hey Sanford!I tried looking for your blog post you mentioned was in the works, did you end up posting one?

Thanks Amy!For the product usage based emails part you can use a default program within the nurturing stream that would make sure to include all members of the stream (to avoid endless loop of nothingness) and in the flow have a choice to send out emails based on product usage and otherwise do nothi...