Erik_Heldebro2

Hey Chandru,Seems like you have the variables in place:${border_left} for Border Color${background_1} for Table BackgroundIf these are placed within a module you would want to define the scope for them as local (meaning unique for each module they are placed in).This is achieved with defining mktoMo...

Hmm for program success date you can basically trigger on the Program Status updating and Success is true with a Flow Step for Change Data Value with a datestamp, i.e {{system.dateTime}} or {{sysem.date}}, although you would probably need to apply this kind of logic manually as there's a risk it wil...

Aside from setting up SSO, you can also just achieve this with a "+something" in after your name and before the @ symbol. So if you have login to instance 1 set up as first.last@company.com you can add another login to instance 2 as first.last+two@company.com (of course you can put + anything you wa...

Hi Avinash!I wrote up this post at the beginning of the year detailing this kind of setup, you can find it here: First, Last and Multi Touch attribution for UTM parameters and auto tagging emails Also if you check the comments Dan Stevens​ had some good additions to clearing the fields for more accu...

I didn't have a chance to watch the webinar although I was pleased to see this guide they posted which, although not fully encompassing all requirements, does address some examples of hands-on processes for GDPR in Marketo: The GDPR and The Marketer: A Practical Guide for the Marketo Customer

Hi Macarena,This is an interesting topic, if you think about it there are more data fields aside from hidden fields on a form, such as lead score fields which are constantly updated in the background. I see it more as a data processing optin on a form. You will need to do a clear documentation of th...

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...