browse

6/2024

Bug Fixes

  • Update to Incoming Event Campaigns - JIRA Ticket
    An incoming event campaign was triggered when any data was received as an incoming events, which caused problems in case of backdated order data (for which the event data is in the past). For example, orders received inside 360 Marketing on 27-04-2024 but the event date for the order was 08-02-2023. We have update the Incoming Event Logic as such:

    • If the event date for the order is before the campaign creation date, ignore that order

    • If the event date for the order is same as the campaign creation date, it will be processed further based on campaign conditions

    • If the event date is after the campaign creation date, it will be processed further based on campaign conditions


5/2024

  • Redirect Campaign
    Released a new campaign with 5 Flyer locations called Redirect. This campaign intends to “redirect” customers' ordering habits from ‘busy days’ to ‘down days’.

    • Busy Days = Days the system will look for repeat orders (customizable)
      Friday, Saturday, Sunday

    • Down Days = Days the system will send campaigns (customizable)
      Monday, Tuesday, Wednesday, Thursday

    • Ordering Period = How long the system will look for repeat orders (customizable)

Our system will look for customers who have placed 2 orders on the designated busy day inside the ordering period. These do not have to be on the same day (ex. Fri & Sat). Once we recognize this we will trigger the campaign that will start sending email/sms on the designated down days with the intention of 'redirecting' customer's ordering habits to the down days. Discounts will be established that can only be redeemed on the down days.

Additionally, if an order is placed on a down day our system will recognize the timestamp and stop any further email/sms from sending, but if the order was placed on a busy day, then the campaign will continue.

  • Insights Report - Order Count -
    Released an internal report inside of 360 Marketing that provided 360M teams access to order count across unique locations. The report provides the following three options:

    • Lifetime Order Value: Individual consumers order value based on the date range (i.e. amount spent within the designated timeframe compared to the same backdated timeframe)

    • Lifetime Order Count: Individual consumers' order count based on the date range (i.e. total order count within the designated timeframe compared to the same backdated timeframe)

    • Increased Order Volume: Month-to-month comparison of order counts for the store

  • Auto Responder Implementation -
    Released an update to the logic of Auto Responder to make sure that the rule is executed only once per customer, and should allow customers to fall into separate rules inside the auto responder. When a customer completed a Positive survey they would receive the positive response, but would be unable to receive this response again if/when additional surveys are completed. The customer above would be able to fall in negative or passive just once if they submitted the required survey, but also once per campaign.

3/2024

Bug Fixes

  • HungerRush Orders Not Importing
    Released an update to 360 Marketing production environment on March 1st that impacted registrations of HungerRush Orders causing missing orders from March 1-5. A solution was put in place that resolved registration issues, while also having HungerRush Devs manually push missing orders back into 360 Marketing.

Previous
Next

Comments

0 comments

Article is closed for comments.

Was this article helpful?

0 out of 0 found this helpful
Powered by Zendesk