Campaign Triggers are set but no record generated
Hello, if an automated campaign trigger was set but the record did not generate (a Third Party DDQ), should I open a Support Case or attribute it to a job engine fluke? The other DDQs generated.
I could set up a new criteria specific to this Third Party tracking ID to try to get it triggered, or alter the navigation option to allow creating a record. I'm concerned doing that will negate the effectiveness of a support case in resolving the issue.
What are reasons that a campaign with triggers clearly in place does not create a record?
-
Can you share your current triggers?
0 -
-
0 -
We checked and the logic should have triggered based on either case. We tried adding the tracking ID to force it to trigger, but that did not work. Finally we created a DDQ manually and scoped it ourselves.
0 -
Joan Stiller Can you share your current triggers?
0 -
-
They are shown in the image above
0 -
Joan Stiller - odd, I don't see the image. I wonder if it's the new community not showing it.
0 -
-
It is pending approval. Thanks for trying to help.
0 -
Joan Stiller - Is this set as a recurring or scheduled campaign?
If recurring, are you relying on a calculation scheduled to change the values in these fields? Per the Archer Help documentation:
- Automatic campaigns can be recurring or scheduled. A recurring campaign triggers when a user saves or updates a record and modifies at least one field referenced by the campaign’s target generation rules. A scheduled campaign creates a campaign that is run on a schedule.
0 -
-
Thanks, possibly that is the issue, the fields didn't change when I tried adding the trigger of the tracking ID. We'll experiment more.
0
Please sign in to leave a comment.
Comments
9 comments