Sean_Richards

I think both our methods are similar mate. They both abstract the trigger logic into a single field, and use that field to spawn the re-roll to occur once 🙂 I'm a big SF dude, so using the SF process step to check for any changes and flag a boolean seems like the easiest and cleanest way for me. Th...

I had an idea. I could puish this back to Salesforce to handle the triggers and abstract it into a single boolean instead. So basically, have salesforce calculate if one or more of those fields are changed, update a checkbox to true to tell marketo to rerun the demographic score recalculation. Then ...

So this would help you all understand the issue better: https://youtu.be/Id1xfYvIiJE?t=1907 We modelled this off Edward's architecture. When you see the "Gating ReRoll" Campaign, you will see he also has multiple triggers, but I can't figure out how this would not also result in a CRM sync firing of...

Exactly!

Hi Amit, Here is the flow and also the daisy chain. Essentially, it resets person score back to behaviour score, then kicks off a chain of request campaigns. The issue is that if this chain is started 3 times from 3 data value changes, yes, it tends to double the end result, or not quite double as t...

Hi Chris,Yeah, we do sync our lifecycle program into SFDC and I agree with having a single MQL lifecycle status. I went ahead and solved this with the counter and timestamps. Here are screenshots from the dashboard and report I created to support us seeing MQL's over time, grouped by lead source. Wh...

Hi Chris,In my previous statement though I am suggesting/questioning that even Marketo themselves is taking a position that they would be OK to find a person (let's say CMO of X company) who has not "requested information about one of your products" and could qualify based on their role and the comp...

So, I may be coming around on this legitimate interest thing.This is from Marketo's policy... Privacy Notice » Marketo Documents Our legal basis for collecting and using the Personal Data described above will depend on the Personal Data concerned and the specific context in which we collect it. We ...

This is still an issue right? I am still seeing "{{my.Event_Title}} {{my.Event_Type:default=Webinar}}! " in the subject line under the email tab in MSI. Pretty dismal that's not fixed.