Understand a reader's record
Once you have found the reader, confirm their name and email in Account details. Then choose the area that answers the support question.
For City Journal's fictional Alex Rivera, the account record identifies Alex. A monthly subscription choice, a membership attached to Alex and a recorded transaction are different pieces of information.
Choose the right area
| Area in the reader record | What it tells you | Useful next check |
|---|---|---|
| Account details | Recorded email, first and last name, company and other profile information. | Confirm you have the intended person. |
| Subscriptions | Memberships attached to this reader, with Plan and subscription names, an end date and renewal information. | Read the membership. |
| Subscriptions history | Historical membership records, with Plan/subscription names and start/end dates. | Compare a past record with the attached memberships. |
| 30-day Activity | Recorded content-view and paywall-hit counts, plus activity dates. | Read the activity measures. |
| Transactions | Recorded transaction amounts, dates and statuses. | Find and understand a transaction. |
| Mail log | Stored message subjects, dates and statuses for the reader. | Find and understand message records. |
These are boxes on the record page, not separate membership-status tabs. Scroll to the relevant box.
Keep account information separate from memberships
The reader ID in the Audience list identifies the reader record. It is not the ID of a subscription choice or a membership period.
Account status and confirmation controls concern the reader account. Do not read them as the status of every membership. A reader can have a record even when a membership or transaction box has no data.
A Plan defines content access, and its subscriptions provide choices such as City Journal Monthly or City Journal Annual. The Subscriptions box shows the reader's relationships to those choices; it does not change what the catalogue choices mean.
Read what is present
Memberships, subscription history and transactions are shown for an existing reader record. Empty tables show a no-data message. That message does not explain why a record is missing; check the intended publication and reader before drawing a conclusion.
Mailchimp and Campaign Monitor subscription boxes appear only when the corresponding publication integration is configured. They concern mailing lists and are separate from City Journal's paid-content memberships.
Follow the question
For “Which subscription is attached to Alex?”, read Subscriptions and then Subscriptions history for context. For “What payment was recorded?”, read Transactions and its status. An end date or renewal setting alone does not answer the payment question.
For “Can Alex read this article?”, the membership is only part of the answer. The Plan's rules, the article's classification and other access settings matter; Understand content access rules explains the basics.
Return to Audience and memberships, or continue to Read a reader's membership.