Skip to main content
TyronPr
Adobe Champion and User Group Leader
Adobe Champion and User Group Leader
Apr 30, 2021 3:54 PM UTC
Solved

Bug with Activity Log

Does any else have this bug where change data value actions from SFDC are incorrectly being associated with a previous campaign?

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
SanfordWhiteman
SanfordWhitemanAccepted solution
User Group Leader
Apr 30, 2021 11:59 PM UTC

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.)

4 replies

SanfordWhiteman
User Group Leader
User Group Leader
Apr 30, 2021 5:40 PM UTC

Is the sync (or sync-implying) Flow step not part of that campaign?

Translate
TyronPr
Adobe Champion and User Group Leader
TyronPrAdobe Champion and User Group LeaderAuthor
Adobe Champion and User Group Leader
Apr 30, 2021 9:39 PM UTC

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

Translate
SanfordWhiteman
User Group Leader
SanfordWhitemanUser Group LeaderAccepted solution
User Group Leader
Apr 30, 2021 11:59 PM UTC

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.)

Translate