# Campaign actions and triggers suggestions

**URL:** <https://forum.mautic.org/t/campaign-actions-and-triggers-suggestions/2905>\
**Category:** Ideas and Feature Requests\
**Created:** [December 3, 2015, 6:41pm UTC](https://forum.mautic.org/t/campaign-actions-and-triggers-suggestions/2905 "2015-12-03T18:41:32Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![CedricH](https://avatars.discourse-cdn.com/v4/letter/c/c5a1d2/32.png) [@CedricH](https://forum.mautic.org/u/CedricH)\
**Post date:** [December 3, 2015, 6:41pm UTC](https://forum.mautic.org/t/campaign-actions-and-triggers-suggestions/2905/1 "2015-12-03T18:41:32Z")

</div>

I’m playing more and more with campaigns and feel a lot of small “limits”

- duplicating - cloning conditions, triggers, events and actions would be great instead of having to recreate for the fifth time the same “trigger”  
- creating bridges from different “triggers” to the same “result” ie sending a welcome mail to all people who have done another action, whatever that action was. If I have to re-ask an action, even at the 5th time, I may want to send the same mail in the end.  
- creating triggers on specific urls in a mail. ie I’d love to be able to know who goes to which appstore to add tags to my prospects. And I don’t think I’ll be able to place a Mautic tracking pixel on Google or Apple stores … just want to track specific clicks as I have to include all appstores in my mails.  
  
  
  
Certainly more to come later …

---

<div class="post-metadata">

**Author:** ![CedricH](https://avatars.discourse-cdn.com/v4/letter/c/c5a1d2/32.png) [@CedricH](https://forum.mautic.org/u/CedricH)\
**Post date:** [December 3, 2015, 6:41pm UTC](https://forum.mautic.org/t/campaign-actions-and-triggers-suggestions/2905/2 "2015-12-03T18:41:32Z")

</div>

I’m playing more and more with campaigns and feel a lot of small “limits”

- duplicating - cloning conditions, triggers, events and actions would be great instead of having to recreate for the fifth time the same “trigger”
- creating bridges from different “triggers” to the same “result” ie sending a welcome mail to all people who have done another action, whatever that action was. If I have to re-ask an action, even at the 5th time, I may want to send the same mail in the end.
- creating triggers on specific urls in a mail. ie I’d love to be able to know who goes to which appstore to add tags to my prospects. And I don’t think I’ll be able to place a Mautic tracking pixel on Google or Apple stores … just want to track specific clicks as I have to include all appstores in my mails.

Certainly more to come later …

---

<div class="post-metadata">

**Author:** ![eric](https://avatars.discourse-cdn.com/v4/letter/e/898d66/32.png) [@eric](https://forum.mautic.org/u/eric)\
**Post date:** [December 3, 2015, 8:53pm UTC](https://forum.mautic.org/t/campaign-actions-and-triggers-suggestions/2905/3 "2015-12-03T20:53:14Z")

</div>

Creating triggers based on specific urls could be accomplished by creating a landing page that has a redirect to the Google or Apple stores (for example). I was just trying to figure out how to do the same thing.

---

<div class="post-metadata">

**Author:** ![CedricH](https://avatars.discourse-cdn.com/v4/letter/c/c5a1d2/32.png) [@CedricH](https://forum.mautic.org/u/CedricH)\
**Post date:** [December 4, 2015, 8:43am UTC](https://forum.mautic.org/t/campaign-actions-and-triggers-suggestions/2905/4 "2015-12-04T08:43:52Z")

</div>

Thanks Eric for this alternative solution, therefore, as I’m trying, like many others, to be as straightforward and seamless as possible … I don’t want to loose my prospects along a multi-step path.

---

<div class="post-metadata">

**Author:** ![silavapi](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/silavapi/32/7424_2.png) [@silavapi](https://forum.mautic.org/u/silavapi)\
**Post date:** [February 2, 2020, 10:56pm UTC](https://forum.mautic.org/t/campaign-actions-and-triggers-suggestions/2905/5 "2020-02-02T22:56:40Z")

</div>

Closed on February 2, 2020, 10:56pm UTC


