See a customer's BigCommerce orders and Drip status together

**Objective:** Build a combined purchase and email-marketing profile for the customer with email `{email}`, looking at orders from the last `{lookback-days}` days (default 365).

**Step 1: Find the customer in BigCommerce**

Call `bigcommerce-get-customer` (bigcommerce server) with `email` set to `{email}`. If nothing matches, report that the customer is not in BigCommerce and stop. Keep `id`, name, `company` and `customer-group-id`.

**Step 2: Get their orders**

Call `bigcommerce-get-order` (bigcommerce server) with `customer-id` set to the customer id and `date-created.from` set to the start of the lookback window. Total the order count and `total-including-tax`, and note the latest `date-created`.

**Step 3: Find them in Drip**

Call `drip-get-subscriber` (drip server) with `email` set to `{email}`. If nothing comes back, report the customer as present in BigCommerce and absent from Drip, and skip to Step 5. Keep `status`, `tags`, `lead-score`, `lifetime-value` and `created-date`.

**Step 4: Get their campaigns**

Call `drip-get-campaign-subscriber` (drip server) with `email` set to `{email}`. List each `campaign-name` with its `campaign-status`.

**Step 5: Report**

Show three short blocks: BigCommerce (customer id, group, order count, total spend, last order date), Drip (status, lead score, lifetime value, tags, campaigns) and Observations. In Observations flag: a Drip status other than active while orders exist, spend with no campaigns, and a Drip `lifetime-value` that differs widely from BigCommerce spend.

**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 the email matches several BigCommerce customers, list them and stop.
* If there are no orders in the window, say so and still report the Drip side.