Skip to content

fix: send subscribe form as urlencoded so Customer.io records form_submit#1045

Closed
betzlermeow wants to merge 1 commit intomainfrom
claude/fix-customerio-integration-rR9F3
Closed

fix: send subscribe form as urlencoded so Customer.io records form_submit#1045
betzlermeow wants to merge 1 commit intomainfrom
claude/fix-customerio-integration-rR9F3

Conversation

@betzlermeow
Copy link
Copy Markdown
Contributor

@betzlermeow betzlermeow commented May 8, 2026

Closing — investigation determined the integration is working as expected. Form submissions are reaching Customer.io and recording on the Forms integration's Submissions tab; the original symptom (no form_submit events in Activity Log filter) was a misread of the dashboard, not a real outage.

No code change needed.

…bmit

The whats-new subscribe form posts to Customer.io's submit_action endpoint,
which expects application/x-www-form-urlencoded (the encoding native HTML
form POSTs use). Commit 6cce858 replaced the native submit with a fetch()
that sent FormData (multipart/form-data); the endpoint accepts the request
and returns the 302, but does not record a form_submit event, so no one is
added to the subscriber segment. The opaqueredirect response made the UI
report success regardless.

Switch the body to URLSearchParams so the request matches the encoding the
endpoint actually processes. Add regression tests pinning the body type.
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 8, 2026

@betzlermeow betzlermeow closed this May 8, 2026
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.

2 participants