Automattic / Automattic/jetpack

Feature Request: Add Additional Collection Fields to Donation Block

Open
#25,032 3 comments 0 reactions 0 assignees View on GitHub
[Block] Donations [Pri] Normal Customer Report [LEGACY] Earn New Feature Payments: Solved by Woo Triaged
Dominant language
PHP
Stars
1.8k
Forks
898
Avg merge
1d 18h
Merged PRs (30d)
774

Description

**What**
A user reached out requesting a way to collect emails, addresses, and phone numbers from folks donating via the Donations block.

**Why**
Being able to collect additional information from folks who are donating would allow organizations to pursue additional outreach and fundraising initiatives with the information collected.

**How**
I think the easiest thing layout-wise would be to add the fields below the amount information in the block, and above the actual donate button.
![image](https://user-images.githubusercontent.com/10101587/119002852-d95ade80-b952-11eb-9c9a-2b2c22ce178f.png)

As far as how to actually work with the information and expose it to the user, I wonder if it would make sense to integrate it with existing contact form responses under "feedback" such that whenever someone donates, there's a feedback entry created with the content of the fields in the donation block.

**Additional context**
This was requested in 29110583-hc

Contributor guide

Open the contributing guide

Research direction

The issue names the Donations block and existing contact form responses under “feedback,” but no files, tests, or entry points. Start by locating the block and its feedback-response handling, then clarify the data model and privacy expectations; done requires an agreed way to collect and expose email, address, and phone fields with coverage for the resulting behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
payments
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.