Repository navigation
Send every volunteer form field to Customer.io - #117
Merged
Merged
Conversation
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>
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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):
phone, plustoronto_2026_build_the_vote_consent_to_share_with_cjpac,toronto_2026_build_the_vote_utm_source,_utm_mediumand_utm_campaigntoronto_2026_build_the_vote_availability,_mayoral_candidateand_issuesPreviously phone and the step 2 answers (including mayoral preference) were deliberately kept out of Customer.io. Consent is always
truefor now, since the form has no consent checkbox yet.Tested:
tsc --noEmitpasses. No live sign-up submitted.🤖 Generated with Claude Code