Hi everyone. I’m new to the team and we’re using iboss, Marketo, and Salesforce. I’m in customer support and we want to see exactly where leads fall out of our nurture sequences.
I’ve heard iboss can connect data between them, but I’m not sure how to set it up for tracking drop-offs. Has anyone done this? I’m looking for a clear view of the customer journey from first touch in Marketo to opportunity in Salesforce.
What’s the best way to configure iboss to highlight the specific stages where we lose people? Any gotchas or tips would be really helpful.
Welcome to the team. Yes, we did exactly this last quarter. The key is mapping your Marketo program statuses and Salesforce opportunity stages as discrete events in iboss, then creating a funnel report.
Start by defining what a "drop-off" actually means in your process. Is it failure to open an email, or a lead sitting in MQL status for too long without progressing? In our setup, we created custom alerts in iboss for when a lead's program membership status in Marketo didn't sync to a corresponding stage change in Salesforce within 5 business days. That pinpointed a big gap in our sales handoff.
One gotcha - watch your timestamps. Make sure the sync time between Marketo and Salesforce is accounted for in your iboss journey timeline, or you'll see false drop-offs. Good luck
automate everything
That's a good foundational question for visibility. While the previous answer covers the alerting logic, I'd focus first on the data mapping foundation. The biggest hurdle isn't the iboss configuration itself, it's establishing a common key and event taxonomy across the platforms before you even build the funnel.
You'll need to audit and likely standardize the field values synced between Marketo program statuses and Salesforce opportunity stages. For instance, if Marketo uses "Nurture Stage 3" but Salesforce shows "Nurturing - Lead Review," iboss will treat them as separate events, creating artificial breakpoints. I recommend creating a staging table in iboss to normalize these status labels into a single journey stage identifier before building your funnel visualization.
Also, consider tracking system actions as negative events. A drop-off isn't always the absence of a stage change, it can be a positive but undesired action like "Unsubscribed" or "Marked as Not a Fit" in Salesforce. Those should be configured as terminal events in your journey to give you a true attrition point.