Executable Campaign with Requested Campaigns | Community
Skip to main content
D
dtrosky
New Participant
April 29, 2022
Solved

Executable Campaign with Requested Campaigns

  • April 29, 2022
  • 2 replies
  • 3603 views

I'd like to move one of our lifecycle smart campaigns to be executable to speed the process a bit.

 

The way the program is currently set up is based on a person being created in the system (trigger). The flow then points to requested campaigns based on the persons interaction. Example, they score 100 points, go through the smart campaign to pass to sales. The trigger campaign is set up with wait steps at the moment to make sure they go through the individual requested campaigns, then we have a sync to SF step.

 

I created a new trigger campaign (not activated yet) for when a person is created and changed "request campaign" to "execute campaign," pointing to the same (live) smart campaigns. Will this work if the existing campaigns that are in the flow were not marked as executable? Or do I need to create all new smart campaigns for everything? Also, I'm still a little unclear what "Use Parent Campaign Token Content" means- can someone please explain this?

 

 

 

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

The execute campaign flow step is designed to work only with the executable campaigns - i.e., you would need to re-create the campaigns as executable campaign and then use them in the pilot campaign's execute campaign flow step. Also, existing campaigns cannot be converted to Executable campaigns, you would need to clone them (after removing any triggers, or illegal flow step(s) - wait and call webhook from the campaign)

 

Also, parent campaign will essentially be in a program / campaign folder and when you check mark the "Use Parent Campaign Token Context" the token context from the parent campaign will be passed to be referenced in the executable campaign's flow (which are essentially the child level campaigns executed by the parent level campaign) - i.e. in simple words your child level executable campaigns would be able to use the program / folder level token values that the parent campaign has access to. This POC doc does a good job of explaining the concept of passing the parent campaign token context to executable campaign. Additionally, the product documentation has also some good content with examples on how token inheritance in the executable campaign works, if you would like to refer.

 

2 replies

A
ajavinash
New Participant
April 29, 2022

Thats really well explained, @darshil_shah1 

@dtrosky 
In Addition to Darshil’s note.

  • If you are converting all Lifecycle campaigns into Executable campaigns, then please make sure to have one Pilot campaign from where you can call/request your all Executable campaigns. There might be chances that Executable campaigns requested for every data value changes depending on how you setup your triggers and filters in your Pilot campaign so define your smart list according to your each lifecycle stage requirement.
  • Don’t forget to define your filters for each respective Executable campaign; if its left blank then it will qualify to all the other Executable campaigns defined in the flow.
  • As you already know you still cannot use a Wait Steps in Executable campaign!
  • Please don’t forget to test each use cases before going live as there might be a possibilities of missing something when using Executable campaign for the first time.

Thanks,
Avinash Jadhav

Darshil_Shah1
Darshil_Shah1Accepted solution
Community Manager
April 29, 2022

The execute campaign flow step is designed to work only with the executable campaigns - i.e., you would need to re-create the campaigns as executable campaign and then use them in the pilot campaign's execute campaign flow step. Also, existing campaigns cannot be converted to Executable campaigns, you would need to clone them (after removing any triggers, or illegal flow step(s) - wait and call webhook from the campaign)

 

Also, parent campaign will essentially be in a program / campaign folder and when you check mark the "Use Parent Campaign Token Context" the token context from the parent campaign will be passed to be referenced in the executable campaign's flow (which are essentially the child level campaigns executed by the parent level campaign) - i.e. in simple words your child level executable campaigns would be able to use the program / folder level token values that the parent campaign has access to. This POC doc does a good job of explaining the concept of passing the parent campaign token context to executable campaign. Additionally, the product documentation has also some good content with examples on how token inheritance in the executable campaign works, if you would like to refer.

 

D
dtroskyAuthor
New Participant
May 2, 2022

Thank you so much for this!

 

I'm going to recreate campaigns to be executable. I noticed that triggers are not available in executable campaigns- since we're sending them to executable campaigns based on criteria from the first campaign- can the smart list flow be empty here?

Darshil_Shah1
Darshil_Shah1
Community Manager
May 2, 2022

Yes, triggers are not allowed in the executable campaigns. You can choose to leave the exec campaign's smart list empty but that would let anybody sent by the parent campaign through the execute campaign flow step in the executable campaign's flow w/o any checks / filters, of course given that they qualify for the qualification rules set in the campaign's schedule tab (which is probably okay for your use-case given that you do apt checks before sending people to the executable campaign and there probably isn't any other parent level campaign from which you're gonna execute this child executable campaign). But I personally prefer adding at least some base line filters to my executable campaigns just as a secondary check to not let anyone flow through the campaign's flow who shouldn't ideally.

 

Terms & ConditionsAccessibility statement

Loading footer...