Does any else have this bug where change data value actions from SFDC are incorrectly being associated with a previous campaign?
Solved! Go to Solution.
So would you say this is expected behavior?
Yes, Marketo attributes a change to a Smart Campaign whenever it can, even if the data involved in the change comes from a remote service. (Remember it's not SFDC is "changing" the fields in Marketo, Marketo is still processing the change request into its database.)
Is the sync (or sync-implying) Flow step not part of that campaign?
Hey Sanford,
Yes, there is an SFDC sync step in the "02a MQL Request with Routing campaign".
So would you say this is expected behavior?
It seems odd to me because SFDC is changing these fields as opposed to a flow action within the campaign, which is what this insinuated to me initially
So would you say this is expected behavior?
Yes, Marketo attributes a change to a Smart Campaign whenever it can, even if the data involved in the change comes from a remote service. (Remember it's not SFDC is "changing" the fields in Marketo, Marketo is still processing the change request into its database.)
Thanks Sanford!