Kenny_Elkington

To an extent, yes. You will no longer be able to retrieve lead details of an anonymous lead via lead ID, since there will not be any anonymous records which have lead IDs. Promoting a lead via the inclusion of a parameter in a syncLead call will work the same. There will not be any changes to th...

Loading custom objects through a csv file is only available from the UI at this time.

The class of the known lead box is "mktoTemplateBox" so you can just apply style to it, either in the custom CSS of your form, you in your landing page. For example, if you add this to your custom CSS, the box will be red:.mktoTemplateBox{ background-color: red;}Edit the CSS of a Form Theme - M...

Mike's solution will work, but if you're API savvy, you can use the Import Lead API, and set your lookupField as 'id' then import your list with id and email columns. This will match your records against their Marketo ID instead of their email address and update them that way: Import Lead » Market...

As Jennifer noted, you can use Email Scripting for this in emails. If you're trying to use opportunity info for smart list rules, you'll want to use the "has opportunity" filter or "added to opportunity" trigger. You can then filter against individual fields on opportunities through the 'add const...

IPs are not unique identifiers, so a reverse IP lookup cannot tell you who a person is, only what network they are accessing your site from. RTP uses cookies to identify specific browser sessions which are associated to your lead record, so if you've cleared your cookies, then you will no longer be...

You've kept the setTimeout included, which is causing the 2 second delay. This is in my demo script just to show it in action so you can see the difference between pre and post-execution. Just remove the setTimeout and you should be good:This:MktoForms2.whenReady(function(form){ moveMktoField("Fi...

I've seen this occasionally. A cache refresh will clear it out every time, so ctrl+f5 on windows, cmd+shift+r on mac.

Well a backlog of 20k updates can potentially clear in less than an hour depending on the number of fields exposed and would cost only 200 API calls. For reference the formula for the number of API calls it will take to sync is given number of updates is: round up( updates / 200 ), so 200 updates c...

I can't seem to replicate this, though I'm trying to emulate from Edge and not IE11. I'll try again when I have access.