FanPulse

What is FanPulse?

FanPulse keeps an artist's own fan list with the consent each person gave, per channel. A fan can be contacted only on a channel whose latest consent record is a grant; a withdrawal is a new record rather than a deletion, so the history of what someone agreed to survives. Segments filter only on a fixed set of stated fields — location, tags, interests, VIP or membership, purchase and attendance counts, recency — and there are no inferred traits such as age, gender, ethnicity, income, health or politics to filter on. A fan list imported as CSV, for example a Mailchimp audience export, needs a consent column; rows without affirmative consent arrive without email consent. Audience geography and tour demand are shown as counts, never as individuals. Campaigns are planned and approved here and sent from your mailing provider; FanPulse records the provider's counts. Erasure and access requests are handled per fan.

Problems it solves

• Know who agreed to be contacted, and on which channel
• Honour a withdrawal without losing the history
• Build segments without inferring anything about a person
• See where fans are, as counts, to inform tour planning
• Answer an access or erasure request for one fan

Key capabilities

Consent Records

Contact a person only on a channel with a current recorded consent; a withdrawal is a new record, and segments filter only on stated fields.

Campaign Planning

Plan, brief and sequence campaign work across channels from one place.

Human Approval Gates

Anything with an outside consequence — a pitch sent, a product published, a campaign sent, a booking committed — waits for a person with the named permission.

Cost-Ceilinged AI Drafts

Drafts and summaries go through the AI Model Matrix under a per-call cost ceiling. Figures are computed by code, never by a model.

How it is built

Consent per channel

The latest consent record decides; withdrawal is appended, never a delete.

Stated-field segments

Location, tags, interests, membership, purchases, attendance and recency — and nothing inferred.

Consent-checked imports

A CSV import requires a consent column; rows without affirmative consent are not emailable.

Counts, not people

Audience geography and demand signals for cities without a show are aggregate counts.

Privacy requests

Export everything held about one fan, or erase their personal fields while keeping aggregate history.

How it works

How the work is structured, and what each step's output rests on.

1. 1

   Collect with consent

   Source

   Sign-ups, merch orders, ticketing and imports, each with the consent given.

2. 2

   Segment on stated fields

   Observed

   Rules on fixed fields; anything else is refused.

3. 3

   Plan and approve

   Human-verified

   A campaign plan is drafted and approved by a person with permission to send.

4. 4

   Send and record

   Source

   The mailing provider sends; FanPulse records its counts.

Example use cases

Each example has its own page you can read and share.

Ask FanPulse

Illustrative examples. Results depend on your own data.

• “How many fans in Manchester can we email?”
• “Which cities have at least 200 consenting fans and no show booked?”
• “Draft a campaign plan for the tour announcement.”
• “Export everything we hold about this fan.”

Questions

Does FanPulse send email itself?

No. Campaigns are planned and approved here and sent from your mailing provider, such as Mailchimp; the Mailchimp API is not connected in this release, so you import its audience export and record the results.

Can I segment by age or gender?

No. FanPulse holds no inferred traits — age, gender, ethnicity, income, health or politics — and refuses segment rules on anything outside its stated fields.

Is fan data sent to an AI model?

Never in identifiable form. Campaign drafts work from aggregate counts.