SanfordWhiteman

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.

“Best” is too subjective, there are lots of test data generators out there. I like Mockaroo myself.

I used the “in future X days” filter thinking that it would only consider date and month and not the year as the lease start date field is going to remain the same, and it successfully picked the records with the current year (2025) and the one set to 1990. No, it didn’t pick a date in 1990 as if it...

Well, please don’t post ChatGPT hallucinations here. You must test to see if they’re even close to the truth. Can’t have a community polluted by false info. In this case, even without testing, can’t see how this passes the smell test. Is the year of someone’s Date of Birth field no longer filterable...

Option 1:Create a new field called “Next Anniversary Date” and set it to the same day and month as the lease start date, but with a static year (e.g., 1990).This could exist at the opportunity level, since we’re updating the year directly from CRM—no need to make it a person-level field.Marketo woul...

@PeeyushSachdeva your suggestion will not solve the problem at all. That way, no matter how many people run through the nurture, your sales team only gets one clean alert per send instead of hundreds.This is false. Every person who runs through the nurture will request the campaign & every person wi...

This is a poor choice of architecture. It has a built-in race condition and isn’t reliable for professional use. It also cuts your sending capacity in half even when it works! If an OAuth token is required, you should send your webhook requests to an intermediate API Gateway service that manages (i....

You’d have to turn off the built-in qualification rule and let people run through every time. Then build an equivalent limitation using, for example, Program Statuses (if the person is already status Sent for a given Program, then Remove from Flow). You don’t change the status for your internal seed...

Doing some of my own tests, think I see the problem(s):“New Outlook” requires a proprietary iCalendar property X-MICROSOFT-LOCATIONSOURCE and some other properties not previously required. I should be able to add those to Agical within the next week. Even when you switch to New Outlook, Classic Outl...