Triggering Smart Campaign of Updated At value | Community
Skip to main content
Jo_Pitts1
Jo_Pitts1
Community Manager
July 3, 2020
Question

Triggering Smart Campaign of Updated At value

  • July 3, 2020
  • 2 replies
  • 4984 views

Hi there.

I have a need to update a field (let's call it API_Trigger) based on the values that may or may not change in other fields.  This is so I can trigger an API call (see one of my earlier posts).  I'd like this done universally as the 'other fields' can get changed in all kinds of locations (both internal to and external to Marketo).

 

I had a thought that I could create a smart campaign triggered on a change in Updated At that would update API_Trigger

However this doesn't seem to work. 

 

Any thoughts on how to do a 'universal trigger'?  If not, I've got to remember to put in a request campaign call on every form fill, etc etc. where a person may have details changed to make sure API_trigger gets updated. 

 

My other thought was to add every record to a 'universal program' on creation, and then use the program member data is changed trigger, but that seems clunky (and risky if someone gets removed from the program accidentally).

 

My Webhook call is based on a second campaign that triggers whenever API_trigger changes it's value. This works just fine (as you'd expect).

 

Cheers

Jo

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

2 replies

SanfordWhiteman
SanfordWhiteman
New Participant
July 3, 2020

Must it be a trigger? Can it not be an hourly batch for people whose Updated At is within the past hour?

 

R
robhyland
New Participant
April 1, 2021

I like this idea, but it doesn't appear to be working for me either. Have you confirmed that this works?

. . . 

I just tweaked some filters and this is working. I think this will be a good solution for me. Thanks!

 

Victor_Herrero
Victor_Herrero
New Participant
April 20, 2021

@robhyland regarding this thread, I think Marketo's next quarterly release will include a new super interesting flow step called "execute campaign" which differs from request campaign in precisely that it will finish executing the campaign before moving on to the next flow step. 

Perhaps it will be useful for you, it certainly will be for me 🙂

Victor_Herrero
Victor_Herrero
New Participant
July 3, 2020

Hi there! 

 

Maybe I'm not seeing something obvious, but I think you could probably create a smart campaign that uses "Change data value" as a flow step. 

 

The triggers could be a "Data value changes" on each of the fields you are expecting updates on, coupled perhaps by the right filters so that it doesn't trigger in the wrong occasions. 

Something like this: 

 

 

 

 

 

Victor_Herrero
Victor_Herrero
New Participant
July 3, 2020

Reading your earlier post, it seems you are already doing something like that. Aside from Sanford's suggestion to aggregate all updates on a custom field and listen for changes on that one... 

 

If you don't want to remember to add a "Request campaign" step to all your campaigns, maybe you can create a central campaign that triggers on "Fills out form" / "Person is created" (maybe forms that contain a specific string in their name) and "requests" your API call campaign. 

 

Creation and modification scenarios would need to be treated separately like this: 

Created AND field1, field2, field3 are not empty

Data value changes field1, Data value changes field2, Data value changes field3 AND (other filers you may need)

    Jo_Pitts1
    Jo_Pitts1Author
    Community Manager
    July 4, 2020

    @victor_herrero ,

    The notion of a central campaign is exactly what I am talking about here.  

     

    I am aggregating the fields I care about as per @sanfordwhiteman and the triggering my API call for integration purposes off the back of a change to the aggregated field.  The key is to come up with a super robust way to update the aggregated field.

     

    The notion of using the updated at date seemed perfect, but oddly doesn't work (possibly by design on Marketo's part).  As per your suggestion, I probably will end up using a smart campaign containing series of triggers based on form fills, score changes etc. (without any constraints) to achieve the same end.  The rate of updates will be moderately low, so it won't be overly burdensome on the system.  

     

    Creation is easy to manage as you can just use the 'created' trigger event.

     

    @sanfordwhiteman , to your point about running it as an hourly batch; if I could get it down to 15 minutes, that probably would be acceptable.  

     

    Cheers

    Jo

    Terms & ConditionsAccessibility statement

    Loading footer...