SanfordWhiteman

Each email client has it's own quirks like this so you can't really rely on downloading HTML once it hits your inbox b/c it's truly not an accurate reflection of the actual code you sent in the first place. Well, if you download the original source from the mail client, that’s truly the HTML that we...

You accidentally cropped the part of of their docs that shows you've made a category error. See red arrow below: They’re returning stale data and lastCalculatedAt shows you how stale it is. That’s not a real-time reflection of database at the point you hit the API endpoint, because it’s not recalc...

Much as I adore Velocity, I’d also wonder exactly why Velocity is being used here. You can concatenate/interpolate {{my.tokens}} into URLs outside of Velocity, and it doesn’t look like you’re really manipulating the values (which would require Velocity)?

SFDC Sharing Rules determine which records Marketo’s SFDC User* can see. So you’d exclude anyone with Confidential=true from Sharing Rules. *technically, Marketo’s SFDC User’s Profile

One of your competitor company was providing it through a direct REST API and we were using it (through a programmatic approach). As because your systems couldn't provide, it doesn't mean that the entire world couldn't. There’s no app that doesn’t run a query to get the real-time count of a Smart Li...

Also, I'm not sure why these threads are marked as "Answered" or "Correct Answer"Because a correct answer was provided! You can get the count using the REST API (that’s what programmatic approach means). There’s another method mentioned which is also correct. There’s no “more correct” answer than th...

If you set SFDC sharing rules to include a Boolean like Hide from Marketo then yes, you can change that field from the Marketo side and immediately break the sync (and all future syncs) for that SFDC record. However, I wouldn’t recommend you do it that way because it’s less than graceful (itinterrup...

The filter field is expected to be a Boolean. You can manage that field with SFDC Flow/Apex to have it be the result of multiple contributing fields.

the native sync creates a new Salesforce Lead instead of linking to the existing record. This is causing a lot of duplicates in SFDC.This is expected behavior. Marketo has no choice if there’s no existing record in Marketo and you choose to sync the person to SFDC. I also assume you’re stopping Mark...

That's typical.