SanfordWhiteman

That isn’t so surprising. See also https://nation.marketo.com/t5/product-blogs/sfdc-campaign-members-can-still-sync-to-marketo-even-if-the/m-p/355672

Did you create a trigger campaign and activate it after the event occurred? That won't work, you gave to use a batch campaign and filter. Trigger campaigns don't play catch-up.* * with one exception that's not relevant here

As Darshil says, you need to make sure the person's Munchkin session is associated on every device. This can be done via tracked link click, form fill, or even browser sync when it syncs cookies. But it won't happen automatically – there's no way for 2 devices that happen to be owned by the same per...

You cannot set this value via API. Doesn't matter whether it's empty or not to begin with.

Start by getting an extract from SFDC of all the people with at least one CO record. Compare that to the Marketo people with at least one SFDC CO, and hopefully you'll see low-hanging fruit of people who should have a CO but don't. Then see what those people have in common in SFDC: permissions, reco...

Here's an example of a Referral Form that supports multiple emails in a single field (technically, all input[type=email] can support multiple). This can easily be refactored to have multiple email fields: MktoForms2 :: Referral v2.1.2 (supports multiple referrals) As for the question about opt-in, t...

This is the standard Referral Form pattern. Search my past posts for links to examples.

You can’t access SFDC Custom Objects via the Marketo API. Only Marketo Custom Objects.

That ID is the event provider’s unique ID. It wouldn’t make sense to be able to arbitrarily change it. Remember, reading a property via API doesn’t have anything to do with whether you can write it.