Find BigCommerce subscribers who are missing from Drip

**Objective:** Compare the BigCommerce newsletter subscribers added in the last `{lookback-days}` days (default 90) with Drip, and report where the two lists disagree.

**Step 1: List BigCommerce subscribers**

Call `bigcommerce-get-subscriber` (bigcommerce server) with `date-created.from` set to the start of the window and `max-records` set to `{max-people}` (default 100). Keep `email`, `first-name`, `last-name`, `source` and `date-created`.

**Step 2: Look each one up in Drip**

Call `drip-get-subscriber` (drip server) with `email`. Record `status` and `tags`, or that no person exists.

**Step 3: Report**

Three lists: in BigCommerce but not in Drip; in both but Drip `status` is not active (for example unsubscribed); in both and active. Give counts, and for the first two lists show email, name, source and date added. Do not treat an active Drip person as an error.

**Rules & Guidelines:**

* `bigcommerce-get-customer`, `bigcommerce-get-order`, `bigcommerce-get-subscriber` are on the bigcommerce server. `drip-get-subscriber`, `drip-get-campaign-subscriber` are on the drip server.
* This prompt only reads. Never call any `bigcommerce-customer-add`, `bigcommerce-customer-update`, `bigcommerce-subscriber-add` or other bigcommerce add, update or delete tool, and never call `drip-add-subscriber`, `drip-update-subscriber`, `drip-add-subscriber-tag`, `drip-remove-subscriber-tag`, `drip-unsubscribe-subscriber` or any other Drip write tool.
* Match people across the two systems on email address, compared case-insensitively after trimming spaces. Drip `person-id` and BigCommerce `id` are unrelated and must not be compared.
* If the user supplied a Drip account, pass it as `company` on every Drip call; otherwise omit `company`.

**Validation:**

* If BigCommerce returns no subscribers, say so and stop.
* Never copy a person from one system to the other; only report.