Edit Push Campaign

After you have created a campaign, there are a few restrictions on the fields that you can edit. Details are shared below.

One time Push

Single occurrence with status as scheduled.

Marketers can do the following:

  • Edit campaign name
  • Add/remove target platform
  • Change segmentation filters/type
  • Add/remove variations
  • Edit variation messages
  • Change the type of A/B testing - from static to dynamic and vice versa
  • Edit the distribution percentage of variations (for static A/B Multivariate testing) and control
  • Edit send/time
  • Edit Advanced settings

Marketers cannot edit send type, conversion goal, and attribution window.

Periodic

Status as scheduled and not even a single instance is sent in past.

Marketers can do the following:

  • Edit campaign name
  • Add/remove target platform
  • Change segmentation filters/type
  • Add/remove variations
  • Edit variation messages
  • Change the type of A/B testing - from static to dynamic and vice versa
  • Edit the distribution percentage of variations (for static A/B Multivariate testing) and control
  • Edit send time
  • Edit Advanced settings

Marketers cannot edit send type, conversion goal, and attribution window.

Status as Active but at least one instance is sent

Marketers can do the following:

  • Edit Campaign Name
  • Add/Remove Target platform
  • Edit variation messages but cannot add/remove a variation
  • Change the type of A/B testing - from static to dynamic and vice versa
  • Edit the distribution percentage of variations (for static A/B Multivariate testing) and control
  • Edit send frequency, send dates, expiry date
  • Edit Advanced settings

Marketers cannot edit segmentation filters/types, add/remove variations, send type, send time, conversion goal, and attribution window.

Event-Triggered with status as Active/Paused

Marketers can do the following:

  • Edit Campaign Name
  • Add/Remove Target platform
  • Edit variation messages but cannot add/remove a variation
  • Change the type of A/B testing - from static to dynamic and vice versa
  • Edit the distribution percentage of variations (for static A/B Multivariate testing) and control
  • Edit minimum delay between two messages
  • Change Ignore DND flag
  • Edit Advanced settings

Pausing an Event-triggered campaign 

An active event-triggered campaign can be paused by clicking the "Pause" button present at the top right corner of the campaign details page. 

Screenshot_2020-08-04_at_1.00.17_PM.png

When paused, the users who qualify to receive the campaign by performing the trigger event(s) will not be sent any message from the campaign. The users who had already qualified before the campaign was paused, will be sent the campaign.

Pausing the campaign with queuing the triggers 

In addition to pausing the campaign, you can choose to queue the triggers that qualify to receive the campaign during the period campaign is paused. You can choose to process those triggers in the queue at the time of resuming the flow or you can choose to purge the queue and resume the campaign for new triggers. 

How does this work?

Once the feature is enabled, at the time of pausing a campaign you will see the option to queue the triggers while the campaign is in the paused state. You should explicitly enable this option for queuing to start.

ETPushCamp_Pause.png

Any trigger when queued will stay in the queue for a maximum of "Queuing period", which is a configurable period for each client that applies to all types of Start trigger queuing. The queuing period can be a maximum of 24 hours. 

While resuming a paused campaign that was paused with queuing you will now have 2 options

ETPushCamp_Resume.png

  1. Process the queued triggers and send them the campaign 
      • When selected the queued triggers will be sent the latest message(if edited) in the FIFO order.
      • The campaign when resumed will adhere to the configured DND settings and the campaign will be sent out at the next available non-DND hour for the queued triggers. 
      • To identify the delay in sending the campaign from the expected time as per the campaign schedule, we have added the "was queued" attribute to the Campaign Sent event to reflect that the delay in sending was due to the trigger being queued as the campaign was paused.

    Screenshot_2020-08-13_at_1.26.24_PM.png
  2. Discard the queue and purge the triggers that are currently in the queue as per the queuing period 
    • When selected, the queued triggers not be processed and the queued triggers will be purged. The campaign will start processing the new triggers that qualify after resuming the campaign. 
    • To identify these purged triggers that will not be receiving the campaign, the "Trigger Purged" event will be added to the user profile of all such users whose triggers are purged.  

The Trigger purged event is also raised when the queuing period ends for queued triggers and is removed from the queue. Such triggers will not be sent to the campaign upon resuming the campaign. 

 

Takeaway

Trigger Purged event is generated when the notification is finally not sent to the user. It can happen in 2 cases:
(a)  after the paused campaign is resumed with the option to purge the queued triggers 
(b) the trigger has been in the queued state for more than the queuing period (max 24 hours) and the campaign has not been resumed yet.

 

mceclip0.png

Marketers are not allowed to edit segmentation filters/type, edit IF/AND events and trigger delay options, add/remove variations, send type, conversion goal, and attribution window. If you wish to edit the fields that are not allowed, we suggest you pause the existing campaign, duplicate it, make the required changes and make it live.

If you feel we have missed anything here or you are not able to edit the mentioned fields, write to us at support@moengage.com 

Was this article helpful?
2 out of 3 found this helpful