Aaron_Dear

Hey Marissa, I did this using Skuid​ a while ago. It acts as a configurable data source platform and drag-and-drop UX builder on top of SFDC. Here's what I think you'll need based on my memory: Asset API - Browse Files (of a parent folder)​ this is the browsing endpoint for assets in a parent folder. Marketo Program Id associated with your Salesforce Campaign - throw that value into a SFDC campaign field so that you can query for the right assets ID = your SFDC Campaign's syncing Program ID Type = Folder I think I had people put the Marketo Program ID into the SFDC campaign as part of a process, not automated. Sanford Whiteman​ - is there an endpoint that lets you query a Program based on a SFDC Campaign ID? I trust your eidetic API knowledge. The end result is that, when you navigate to your SFDC Campaign Detail page, the Asset API is pinged for child assets of the given Marketo Program ID. Also, take this with a grain of salt since it's been a while! Best, Aaron PS: If Sanford says anything I said is wrong, listen to him. Hahaha. And if you wanna walk through this together, I'm down. It'd probably take about 20 minutes. ... View more

Hey Sarah, So... Yes, I do notice the SFDC Is Deleted flag going from TRUE to FALSE I haven't noticed. It's been a long time since I've looked at this - I haven't run into the issue since. Hope you find an answer as well. ... View more

I've no repro steps, but I do have 2 smartlists you could glean if you can access my instance: SmartList 1: Created after December 1-15, 2017, Marketo ID under 50000 (which shouldn't happen if IDs are never recycled - since it would have incremented beyond this number) #SL6076547B2 SmartList 2: Created between December 1-15, 2017, Marketo IDs over 100000 (has tons more people - expected behavior) #SL6076575A1 If you've access to the instance, take a peek if you'd like. ... View more

I thought so, too, but the test I did yesterday allowed a "Sync to SFDC" flowstep to a lead in the recycle bin. I've copy-pasted those steps below: First, I deleted my test lead in Salesforce (the lead sits in the recycle bin now) SFDCisDeleted=TRUE now... Then, I ran a batch campaign to Sync to SFDC SFDCisDeleted=FALSE now... Syncing occurred without a problem It's a pretty fringe case, and I'm not too worried for now. Appreciate your help and digging Steven! ... View more

Solid decision - much more intelligent design than my recurring batch campaigns. Thanks Grégoire! I left a comment below with some screenshots and an "ENTITY_IS_DELETED" error. Have you seen anything about that? ... View more

Hey Steven, I ran your test scenario through - I expected this might be the case as well! I also wanted to test conditions with the recycle bin... First, I deleted my test lead in Salesforce SFDCisDeleted=TRUE now... Then, I ran a batch campaign to Sync to SFDC SFDCisDeleted=FALSE now... Syncing occurred without a problem I deleted my test lead in Salesforce, then deleted him from the recycle bin SFDCisDeleted=TRUE I ran a batch campaign to Sync to SFDC SFDCisDeleted=FALSE again Syncing occurred without a problem I opened a SmartCampaign to filter for "Lead was deleted from SFDC" Filter: email is my lead's email, and "Lead was Deleted from SFDC" in last day. The lead shows up, and is simultaneously in SFDC. You're right! There's still a weird message I was seeing yesterday though... Below are screenshots I took showing a lead who was not deleted, but was getting a strange error message. This person had "SFDC IS Deleted = FALSE", but "Lead was Deleted from SFDC". I highlighted that below. In the Activity Log, that person gets these activity records (ENTITY_IS_DELETED) whenever I attempt a sync to SFDC. Note: I didn't notice at the time. A while later, subsequent sync attempts still occur - but Marketo continually lets us know the person is deleted from CRM because - I imagine - that SFDC ID no longer existed. Are you acquainted with this issue? ... View more

Yep. https://nation.marketo.com/apps/d9b4f216bee951f7b28f437fedacd55d?page=detail&caseid=5003800000tu6RN ... View more

Hey Josh - answers below! 1) Not as far as I know. I didn't check the Recycle Bin before running the batch campaign. 2) Yes - the goal was to remove any deleted persons from Marketo. I left the "remove from CRM = true" comamnd because... well, I didn't see a reason not to. Logically, if a person had been deleted in SFDC, I didn't see why would that make a difference. But, in the offshoot that it did, I could use the chance to learn more about the system (aka - this topic). 3)  I did check the list before I ran it - a question of you, what specifically did you want to inquire about on that list? 4) The records were deleted from system - it says nothing. After returning them from the Recycle Bin, it seems as if they are brand new records (new ID, new Marketo Created Date). They do have the correct SFDC ID. ... View more

Sorry for necro'ing this thread - was digging for "Lead was Deleted from SFDC" info -  but I read that in Liam Neeson's voice. ... View more

Hah, literally the same issue here! ... View more

Story of my life. GTW is infamous for 403 errors. A launchpoint re-auth is all it takes to "fix" it until a week later. ... View more

Hey Amanda! Answers below: Did the leads exist in SFDC before being associated to the program/event? Nope. They were sourced from a form fill out in Marketo. I have come across the scenario that if sync fails on the first attempt (the attempt to create a lead in SFDC), it won't try again, and you have to put them through a flow step of sync to salesforce, when all validation errors are solved. I believe you should set up a batch campaign to run daily/weekly to sync to SFDC all the leads that have been created that don't have a SFDC ID (don't exist in SFDC). Ah! So my hypothesis is (maybe) right! A batch-campaign to sync everything sounds like a great plan. Let us know what you find out from support. Will do. Appreciate your thoughts. ... View more

Support person's quotation: I would once again like to refer you to another article I found about this subject. It is actually written by one of our TSEs. The ruleset for which record is considered to be the winner, actually depends on the activity being performed, and this article goes over a lot of the questions you have. https://marketoemployee.jiveon.com/docs/DOC-10512 (Aaron's Note: this is a Marketo Employee internal link I think - can't access) The article does say that for email batches, it uses the lowest Marketo ID (smallest number). My support case is closed - but my testing shows that the smallest ID gets the send. Here, there are 3 leads in a flow with 2 steps: Step 1 - Change Program Status Step 2 - Send Email All 3 receive a change in status. Only the youngest ID'd receives the email (and corresponding activity). This test just got me thinking -  I did not have a way to control for youngest Marketo record versus lowest ID. For example, if the records with higher ID were younger, would they get the email instead? So I ran this one more time, just with an email send step. Sure enough - smallest ID wins (and others receive nothing). Hope this helps! EDIT: The plot thickens. My AE also noted that someone told him... In the case of duplicate leads, the question of *which* lead gets selected for a  campaign (or gets an activity assigned or updated by a form/list) is best viewed from a user perspective as non deterministic. While often the case, the product does not guarantee lowest id or Last updated etc is the one that is used. Which is a little concerning and a little interesting. Haha ... View more

Agreed. In our instance, we have tested using the API to surface Marketo activities into our CRM. While it works, the potential of ID swapping concerns me. We might just need some logic to refresh IDs every so often. Here's the exact response I got from support: Sorry for the misunderstanding, a lead ID can be reused if a lead is deleted and then purged from the instance. A purge occurs about 30 days after a lead has been deleted which is the window for support to be able to restore a deleted lead. So most likely which ever lead had the value of 46460 was deleted and then purged which left a hole that was filled by the next lead to be created. Keep me updated if you have interesting workflows/flows/processes/etc to get around it - or ways to guarantee ID matching to SFDC IDs! ... View more

I am led to believe there is a pool of available IDs from previously deleted leads that "frees up" after a certain period of time. As for confirmation: I noticed it myself a while ago. I had 3 leads, with the older 2 (both in SFDC and Marketo age) having a high ID (6 figs), and the newer one having a lower ID (in the 40k's). Then, just recently, I noticed another set of leads with a similar M.O. I assumed that the ID was immutable. When I asked support (who then asked product) they noted that IDs begin from the lowest number after a certain period of time. ... View more

Been doing some testing around this - my support guy pointed me here. To clarify, email sends will go to Marketo's smallest ID. That is NOT always the one created earlier. After a lead record has been deleted from database, Marketo will eventually start associating newer IDs to older records. For example: 1) A lead fills out a form. ID#100 is created. 2) ID#100 is manually deleted 3) ID#200 is created - same email address as ID#100. 4) 3 months later, a lead is created from a Salesforce list upload - same email address. When it syncs over, Marketo assigns that lead ID#100. This lead is younger, but has a smaller ID. 5) An email send goes out - both leads meet the criteria. ID#100 gets it. Just a PSA! ... View more

Ah, excellent. So I could absolutely do this then. Thanks Sanford! ... View more

Would be quite nice to see how people are implementing this directly into a Salesforce view - without the use of MSI. ... View more

+1 to this idea. It was important before... but it's extra important with GDPR coming! ... View more

True - perhaps the log line for the error is all that it's displaying. That said, it's still blocking the sync to Salesforce. I looked in a bit more, and only got more questions. For others who run into this issue and are frantically Googling to get through it: We currently update this custom lead source field (an SFDC picklist) via the UI, through a Change Data Value flowstep. The field itself in Marketo shows the correct value. But we get this restricted picklist error (and a subsequent inability to sync back) regardless. The Salesforce lead record does not have the added field values, so we've confirmed that it has not been syncing. No clue what the solution is. C'est la vie! ... View more

Are you still getting this error? We are too! The Salesforce record doesn't have the "\n". The Marketo record doesn't have the "\n". But the error message notes that the field's value has an "\n". So odd. I'm about to delve into a related Salesforce flow that might be culprit. This link talking about the uses of "\n" can help explain why this appears technologically. ... View more

The syncing had been almost a black box for me, until I read through Edward Unthank's amazing breakdown. There's one paragraph that's pertinent to your exact situation here. Long delay between Marketo and SFDC? "Timeliness of sync between Marketo and Salesforce "Sync lead to SFDC" and "Add lead to SFDC Campaign" is immediate, without a queue. When a lead runs through that flow step, the sync to SFDC happens. Marketo program/SFDC campaign sync happens through a queue every 7 (or so) minutes. That's the one that you see in the Admin section of Marketo, where "Last time Salesforce was synced" is. While this happens every 7 (or so) minutes, there's a set limit of campaign syncs happening with each call, and extra campaign syncs will be queued, waiting for a later program/campaign sync opportunity if there's room next time. SO, Marketo program/SFDC campaign syncs are more API-call efficient, but you run into queueing bottlenecks faster. I don't remember exact throughput numbers, but when I was doing a huge sync, the leads-synced-per-hour was around 8,000. Lead updates also happen every 7 (or so) minutes. That is, when you update a field value on a lead in Marketo, it's checked against SFDC every time to see if the value is different, then if it's different, Marketo updates the new value in SFDC (or vice versa). This faces the same lead-value-change queueing problem as Marketo programs/SFDC campaigns." ... View more

Yep, I've got that same question. It's unfortunate, but I'm OK with a custom service if it means getting my data corrected! ... View more

If you look at his screenshot, there's a smartcampaign named after its function: it stamps date/time for MAL. I'm sure this process is repeated for other stages. ... View more

Hey Malik, You ever find the ideal solution for your problem? I have a similar one - but instead of knowing all the form fillouts, I know all the SFDC campaigns associated. I've inherited a newer Marketo instance recently with a lot of unassigned leads/contacts from SFDC campaigns. We use Marketo RCE to do attribution now, so I need to retroactively assign Acquisition Program and create some placeholder programs that I can sync a SFDC campaign to. Figuring this out sounds similar to your "my lead has multiple forms, but I want to assign an Acquisition Program based on the first form", except replace "form" with "SFDC campaign". ... View more