Custom Activity like (Flow Control Wait by Attribute) before Email Send - Answers - Salesforce Trailblazer Community
Trailblazer Community
Ask Search:
JAYESH TEJWANIJAYESH TEJWANI 

Custom Activity like (Flow Control Wait by Attribute) before Email Send

I am looking for help regarding Journey Builder activities for a specific use case

Example: Person is hosting an event, she/he wants to send an email when there are last 100 tickets remaining for an event to all the contacts(who haven't bought one) in DE. Since the activity "Wait by Attribute" takes the only Date as a parameter but I am looking for a custom field as a parameter so can we create a custom activity Wait Until Specific Value if its possible to build one or use any other elements from the activities to accomplish this use case.

Please help me out. Thank you in advance.


 

Best Answer chosen by JAYESH TEJWANI
Nick KroehlNick Kroehl
Hi Jayesh, you've got some good options above, but I'll offer up one more in case  you are tracking ticket sales in a data extension, and need to run a query to determine if you're down to 100 tickets. In this scenario, you use an hourly automation in Automation Studio that contains 2-3 steps:

[1] A Verification activity to determine if the count of remaining tickets in your data extension is <=100. You may need a query step before this to do this calculation. If the count is >100 then stop the automation.

[2] A Fire Event to kick off your journey. Your journey should run only one time since you'll have an hourly automation and you don't want to run the journey every time the automation runs. This step will not run until you are down to fewer than 100 tickets.

Finally, schedule your automation to run hourly. Better yet, copy the automation and stagger each copy so that they’re 30 minutes apart—say, at :15 and :45.

Best,
Nick

All Answers

Mira ShahMira Shah
Hello Jayesh,
My suggestion is, create a custom field and it's calcualte ticekts according your requirement, after that create a process builder to send an email alert.
 
Simone LuiseSimone Luise

Hi Jayesh,

custom activity is a solution for external processing of some needed.
I think you can create a workaround to do what you need, i suggest you a simple wait by Attribute (if you use same Journey for each event, or wait until in other case) that "block" the contacts since "some days before the event date" and than a "decision split" that move how didn't buy a ticket to a branch with an email activity and the other to a brench without.

You need to link this information to all envolved contact in an attribute group to make the solutilon above.

- Event Date (for wait by atttibute)
- Event Ticket acquisition or registration (for decision split after wait)

Wait and declision split after is the solution of the common problem in Joureny design.

Simone

Nick KroehlNick Kroehl
Hi Jayesh, you've got some good options above, but I'll offer up one more in case  you are tracking ticket sales in a data extension, and need to run a query to determine if you're down to 100 tickets. In this scenario, you use an hourly automation in Automation Studio that contains 2-3 steps:

[1] A Verification activity to determine if the count of remaining tickets in your data extension is <=100. You may need a query step before this to do this calculation. If the count is >100 then stop the automation.

[2] A Fire Event to kick off your journey. Your journey should run only one time since you'll have an hourly automation and you don't want to run the journey every time the automation runs. This step will not run until you are down to fewer than 100 tickets.

Finally, schedule your automation to run hourly. Better yet, copy the automation and stagger each copy so that they’re 30 minutes apart—say, at :15 and :45.

Best,
Nick
This was selected as the best answer
JAYESH TEJWANIJAYESH TEJWANI

Hi Nick,

Thank you for the above suggestion, the above solution worked for me. Reiterating what I did, I created automation with 3 activities,

  1. SQL Activity to query the dataset for the registration count and if it exists then pushing that data to a new DE,
  2. Verification activity checks if the record count is greater than 0 in the new DE if yes then send email and go to Step 3
  3. Fire Event which has the Data Extension which is passed as Input in the Journey Builder and it triggers the Journey.
  4. Verified the Journey it was fired and the email was sent.
Nick KroehlNick Kroehl
Hi Jayesh, I'm glad it worked for you. Thanks for following back up here!