SanfordWhiteman

A record can have unlimited associated cookies. Wouldn't make sense otherwise: you couldn't even click a link on desktop and mobile!

The database API requires passing a folder ID or program ID where the lists should be created. However, in the Database section of Marketo, there are only folders and lists, no programs. Also, folders in the Database don’t display any ID in the UI.You don’t get Folder and Program IDs from the UI. Yo...

This can’t be known directly. It may only be simulated by calling a webhook right after the send that reads the Custom Object list and writes a Custom Activity with the data at that point in time.

Sent Email logs are only kept for 90 days. Opens can occur far later, either by humans or by mail scanners.

The only part you do in Marketo is add UTM params to links, and that’s simple. Step back from Looker Studio as that’s a deeper part of the process. Are you able to see the UTM params in Google Analytics at a basic level? Are you able to see the UTMs on the link in the Location bar? [using auto-trans...

Unfortunately, that report still shows deactivated assets so doesn’t meet the requirement. I’m not aware of anything you can generate via the UI that includes only active assets. And the API hardly knows about Engagement Programs at all (that is, it can find emails that are within the EP hierarchica...

Pardot used to provide an option for conflicts, where the value in SF (or Pardot) could be chosen to overwrite the other, but I'm not aware of any such thing with Marketo. 🤔Marketo uses the SFDC systemmodstamp during reconciliation. Individual fields don’t have conflict resolution. So if you have a...

Like I said, there’s no honeypot that can’t be neatly skipped over by a well-written bot. Why would anyone claim otherwise? For example, how would a bot that can simulate form.submit() with valid fields + checksum (the bot can’t simply populate fields and send a native POST, it must either automate ...

Huh, your exact code worked fine for me in my lab. Not sure what else you could be doing differently.

Additionally, I recommend separating Lead Status from Lead Lifecycle. , you can still map or translate those values to reflect the appropriate stage in your Lead Lifecycle model. This approach allows you to maintain alignment between systems also give better visibility person can stay as "MQL" in li...