Newsletter imports (add-on)

The recent runs of the CSV importer, newest first, with the file each one read, the list it wrote to, where the run got to and the four counters that say what it did: how many addresses were new, how many were already here, how many were skipped and how many ended in a suppression rather than a subscriber. The four add up to the total, so a merchant asking why twelve thousand addresses became eleven thousand four hundred reads across rather than guessing. Start here when somebody asks where a subscriber came from: every address an import wrote carries the file name.

One import run with its counters, its status, the reason it failed if it did, and how far through the file it is as a fraction — which is null until it has read its first chunk, because a run that has not started knows nothing and reporting zero would be reporting something. Poll this while a run is going; the counters are written every five hundred rows.

How many of the store's own customers match a filter and what would happen to each of them, without writing anything. Answers five numbers that add up: how many customers matched, how many of those would be added, how many are already subscribers, how many are suppressed or have bounced, and how many were skipped because they have no usable address. Filters combine with AND and are all optional — bought at least once, bought a given product, bought anything in a category, in a customer group, ordered within so many days or since a date, has an account or is a guest checkout. Use this to answer "how many of my customers are on the mailing list", which needs no write permission at all.

Put the store's own customers on a list, as one import run with the same counters and the same history as a CSV import. Takes the same filter preview_customer_import takes, and a mode — invite, which writes each customer pending and emails them a confirmation so only the ones who click are subscribed, or subscribed, which writes them subscribed and confirmed straight away. Invite is the default and needs a list to name in the confirmation. Everybody written is tagged, customer unless another tag is given, and is linked to their customer record so purchase segments answer for them immediately. A suppressed address is never written and a bounce or a complaint is never revived, whichever mode is chosen.

Upload a CSV file as multipart/form-data in a field named file and read back what is in it: the columns, the first rows, and which column the importer thinks holds the address, the name and the lists. Nothing is written. No tool: a multipart upload is not something the manifest format describes.