Skip to content

Latest commit

 

History

History

tag-and-segment-customers-by-days-since-last-order

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 

Tag and segment customers by days since last order

Tags: Customers, Loyalty, Segment, Tag

This task will run daily to query all customers in your shop who have placed an order, tagging each with whichever configured tag is paired with the closest "days since last order" threshold. This is great way to keep tabs on who is active in your store, and who you might need to reconnect with.

Default options

{
  "customer_tags_and_days_since_last_order__keyval_number_required": {
    "Burn": "365",
    "Churn": "180",
    "At Risk": "90",
    "Active": "0"
  },
  "create_customer_segments_by_tag__boolean": true
}

Learn about task options in Mechanic

Subscriptions

mechanic/scheduler/daily
mechanic/user/trigger

Learn about event subscriptions in Mechanic

Documentation

This task will run daily to query all customers in your shop who have placed an order, tagging each with whichever configured tag is paired with the closest "days since last order" threshold. This is great way to keep tabs on who is active in your store, and who you might need to reconnect with.

Optionally, you can select "Create customer segments by tag" to have the task create new customer segments for each tag configured in this task.

The task comes preconfigured with a "Burn" tag set at 365 or more days since last order, a "Churn" tag set at 180 days or but less than 365 days since last order, an "At Risk" tag set at 90 days or more but less than 180 days since last order, and an "Active" tag for anyone who has placed an order more recently than 90 days. Change these configuration values to whatever makes the most sense for your business.

Note: the order in which you enter the tags and days since pairs does not matter; at run time, the task will first sort by the largest days since value, and then make tagging decisions accordingly.

Installing this task

Find this task in the library at tasks.mechanic.dev, and use the "Try this task" button. Or, import this task's JSON export – see Importing and exporting tasks to learn how imports work.

Contributions

Found a bug? Got an improvement to add? Start here: ../../CONTRIBUTING.md.

Task requests

Submit your task requests for consideration by the Mechanic community, and they may be chosen for development and inclusion in the task library!