The supporter record, field by field

Contact fields

Field	Notes
firstName / lastName	Resolved contact name. Empty when resolution returns no confident name.
email	Primary match key. Normalized to lowercase before hashing.
phone	Present does not mean textable. See the consent fields.
addressLine1, city, state, zip	Postal address where resolved. Used as the third dedupe fallback.

Consent fields

Field	Notes
consentTimestamp	ISO 8601, UTC. When the affirmative act occurred.
consentVersion	The version string of the consent language in force at that moment.
consentSource	The exact page URL where consent was captured.
consentCategories	The categories granted, normalized from your consent management platform.

These four are the audit trail. They are included in every export and every push, by default, and there is no configuration that strips them.

Intent and behavior

Field	Notes
pagesViewed	Ordered list of pages viewed after consent.
intentSignals	Derived labels — for example donate-page, volunteer-page, issue-page — that you map to tags and activist codes.

Attribution

Field	Notes
utmSource, utmMedium, utmCampaign	Carried from the landing URL. Garbage in, garbage out.
referrer	Document referrer at entry.

Identity and deduplication

Field	Notes
resolvedVia	Which method produced the identification.
dedupeKey	Hash of the lowercased email. The join key across every destination.

Matching order

1. dedupeKey — lowercased email hash.
2. Normalized phone.
3. Name plus address.

On a match we update; on no match we create. Which fields are overwritable on update is your configuration, per destination.