Why doesn't Smart Campaigns react to opportunity trigger constraints | Community
Skip to main content
A
Anonymous
September 20, 2016
Question

Why doesn't Smart Campaigns react to opportunity trigger constraints

  • September 20, 2016
  • 2 replies
  • 2080 views

Hi!

We are sending lead and opportunity data to Marketo through the REST API.

Our flow is the following:

Create lead

Add to opportunity

Update opportunity

Our smart campaigns trigger nicely on Opportunity updated with Old value and New value. However, it fails to trigger we add a constraint to the Smart list on e.g. "name" IS NOT EMPTY.  Even though I know that name on the opportunity contains the text string "RFQ". I have tried with other constraints than name but with the same result.

I have searched through the documentation and a ton of other threads on the forum without success so I really hope you guys can help me.

Thanks!

Best regards, Nikolaj

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

Josh_Hill13
Josh_Hill13
Level 10
September 20, 2016

Do you mean your trigger looks like

  • Lead is Created
  • Added to Opp
  • Opp is Updated

?

Any of those conditions will work.

Why do you need Old Value and New Value on Opp is Updated? What is changing there? Do you need those specific values or can you just make it a blanket condition?

A
Anonymous
September 20, 2016

Hi Josh (and Kenny),

Thanks a lot for your swift response!

I'll just try to elaborate a bit on the issue. Basically I have a Smart campaign with this Smart List:

Looking at the API requests in the activity log for the lead I am testing I can see that the new person is created correctly and the TEST_RFQ opportunity added:

Details on the "Add to Opportunity" activity says that Lead Application Status starts out as pending_review and Name is TEST_RFQ: (The screenshot doesn't show, but the Oppty ID is 3714)

A few minutes later the Lead Application Status is updated from "pending_review" to "open_for_offers". Nothing else changes between these two updates on the opportunity. I would assume that this would trigger the Smart Campaign - but it doesn't.

However, if I remove the 'Name is "TEST_RFQ"' from my Smart Campaign it triggers correctly. But this is really not a feasible solution for me as that would risk triggering the Smart Campaign on the wrong conditions.

Hope this helps clarifying my issue.

Best regards, Nikolaj

Kenny_Elkington
Adobe Employee
Kenny_ElkingtonAdobe Employee
Adobe Employee
September 20, 2016

My first guess would be that the name in the SL doesn't strictly match the name in the Opportunity.  I would check these things:

  • Make sure that you're using the same type of underscore in both places.  Possibly try a test name that only has alphanumeric characters to ensure you're looking at the same exact string.
  • Make sure that there are no spaces at the beginning or end of the Opp name you're submitting.  The UI trims these in most places, so they may not appear when looking at the Opp data.
Kenny_Elkington
Adobe Employee
Kenny_ElkingtonAdobe Employee
Adobe Employee
September 20, 2016

Are you creating the corresponding opportunity role to link the Lead and the Opp?  The Added trigger looks for the creation of a role linked to a lead, while Updated looks for updates made to linked opportunities.

Terms & ConditionsAccessibility statement

Loading footer...