Skip to content

Send every volunteer form field to Customer.io - #117

Merged
xrendan merged 1 commit into
mainfrom
feat/volunteer-fields-to-customerio
Oct 16, 2026
Merged

xrendan merged 1 commit into
mainfrom
feat/volunteer-fields-to-customerio

Conversation

@xrendan

@xrendan xrendan commented Oct 16, 2026

Copy link
Copy Markdown
Member

Follow-up to #116, which merged before this commit landed.

Every /toronto/volunteer form field now also goes to Customer.io, best-effort like the existing identify (a Customer.io failure never fails the sign-up):

  • Step 1: phone, plus toronto_2026_build_the_vote_consent_to_share_with_cjpac, toronto_2026_build_the_vote_utm_source, _utm_medium and _utm_campaign
  • Step 2: toronto_2026_build_the_vote_availability, _mayoral_candidate and _issues

Previously phone and the step 2 answers (including mayoral preference) were deliberately kept out of Customer.io. Consent is always true for now, since the form has no consent checkbox yet.

Tested: tsc --noEmit passes. No live sign-up submitted.

🤖 Generated with Claude Code

Adds phone, UTM tags and consent from step 1, and availability, mayoral
candidate and issues from step 2. Best-effort, like the existing identify.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your trial has ended. Reactivate Greptile to resume code reviews.

@xrendan
xrendan merged commit 1a9d87a into main Oct 16, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant