Subscribers are the main way you collect email addresses and recipients on Buttondown. They're what you see on your subscribers page.
Relevant changes to the schema:
subscriber_type and email to type and email_address respectively.external_url in favor of absolute_url.A unique TypeID associated with the object.
The date and time at which the object was first created.
The email address of the subscriber.
A custom message that was sent to the subscriber when the gift subscription was created.
The subscriber's delivered count.
The subscriber's open count.
The subscriber's clicked count.
The subscriber's open rate, computed from engagement counts. Null if delivered_count is 0 or null.
The subscriber's click rate, computed from engagement counts. Null if delivered_count is 0 or null.
A structured key-value blob that you can use to store arbitrary data on the object. Metadata can be nested — you can store objects and arrays within your metadata. (You can read more about metadata.)
Any notes you want to attach to the subscriber. These are not publicly visible.
The email address of the individual who purchased this subscription on behalf of the subscriber.
A custom message that was sent to the subscriber when the subscription was purchased on behalf of the subscriber.
The risk score of the subscriber. Positive numbers represent a higher risk; negative numbers represent a lower risk.
Information collected by Buttondown's firewall about this subscriber. See the firewall for more information.
The reason the subscriber is undeliverable. (Only populated for undeliverable subscribers.)