Andy_Varshneya1

We're using it on longer videos, where we're adding the form after a preview of the video so that they're also able to get a sense of the subject since a title alone isn't enough to judge a 45 minute webinar.

I would probably add one more trigger - Data Value Changes: Inferred Postal CodeThat will take care of leads that may not get an inferred postal code till later on for one reason or another.

This I strongly disagree with. Anonymous functionality should be binary - either fully functional or not at all functional. Having them be partially or retroactively functional greatly compromises the integrity of most trigger campaigns as they can start triggering off activities that occurred days ...

So the way we're doing it is actually via Courtney Grimes​'s guide Integrating Google Analytics with Marketo That integration relies on the Marketo User ID, so that's why I'm trying to understand if this change to anonymous leads will impact that. From my understanding of it, it will.

Seconding this.Our digital marketing team that is responsible for all top of the funnel lead generation will be 1/2 as productive and helpful without the access to anonymous lead data. Marketing Ops and demand gen will not be as good either.This is a huge step backwards for Marketo and marketing tea...

Thanks Dan, hard to keep track of all the comments as the questions and answers are flying back and forth in this thread.

What about the data that's stored about an anonymous lead and then later on associated with its known lead counterpart? Is that gone too now?

Hi Arjun,Our most powerful and insightful reports rely on anonymous lead data as we're able to populate the anonymous lead's ID into GA and do TRUE end to end reporting from anonymous user behavior all the way to Closed Won.Sounds like that functionality will be removed as well, crippling our digita...

I've just had good luck avoiding most of those then! I think I've gotten the missing mandatory field very rarely but also because we don't even try to sync them over unless all of the minimum requirements have been fulfilled.

In that case the two you'll see most frequently areWarning: Salesforce Sync Changewhen a field's picklist values are changed or adjusted in SFDC and the field is used in Marketo,Error: UNABLE_TO_LOCK_ROWWhen Marketo is trying to edit a lead at the same time as a user is in SFDCOccasionally, you'll s...