Justin_Norris1

@Elizabeth_Down3 Any pointers would be hugely appreciated. Would also love leads on folks who teach velocity in the context of Marketo.Regarding velocity training, you could do no better than @SanfordWhiteman who has already responded to your post. Velocity in the context of Marketo is a very niche...

For future reference, just wanted to update this thread to note that if you click on the email subject line in MSI, it opens a preview window where the tokens DO resolve correctly (both subject line and body). I don't think I had noticed it before. It's still a poor UX to not have it render in the...

Hey Sanford Whiteman- If I'm understanding you correctly, this seems to be another example of multiple tiers of the database having inconsistent information (as you discussed in this related thread: Trigger fires due to Data Value Change but Filter for the same field doesn't reflect the change - for...

Hey lorie witmer‌, How is adding the formula field to the Bizible Person object different from using a combined Bizible Touchpoint and SFDC fields report? (not sure if you have enough context here, I can pull in the Lifecycle MQL date and the Bizible Touchpoints) The main advantage of using Bizible ...

Hey lorie witmer‌ - sorry for the delayed reply. I just noticed your comment. So there's probably a few ways you can set this up, but what we do is the following: 1) Ensure you have date stamps for each lifecycle stage on your lead and contact objects in SFDC. (E.g., MQL Date, SAL date, SQL Date, et...

Can you expand Sandy? Is it because the values from the CDV flow step are not guaranteed to be written to the database by the time they are referenced in the subsequent requested campaign?

The work-around I would use in this scenario is to stamp the program-specific data values to person fields using Change Data Value then request the global smart campaign and reference those person fields in your subsequent actions. At least this still allows you to centralize the repetitive actions ...

Sean Richards‌, I think you'd be fine with a counter or simple date-stamp. From a reporting perspective, the benefit to a separate stage in your model is if you use Revenue Explorer and want to see first-time MQL transitions discretely from repeat MQL transitions in the Model Analysis area. Beyond r...

Hey Sean Richards‌,It depends on what your specific requirements are. If it's just about knowing whether someone is a first / repeat MQL, then a simple date field (e.g., "Last MQL Date") could do it. If you need to know how many times someone MQL'd on their way to being a customer, the score counter...

Sanford Whiteman‌Yes...if only there was a webhook-based service that could accept the date-stamp, parse it in JS and return a flag to indicate whether it was business hours or not. So to be fair, there weren't a lot of webhook-based services readily available in 2014 when I first did this. If I had...