Address
مصر
Help center
From your first article to tracking earnings: choose a topic or search for your question.
Step by step
How bell and email subscriptions, publisher campaigns, allowances, and delivery states work.
The bell is an in-site subscription that can notify you when the writer publishes a new article while automatic notifications are enabled. Email is a separate channel for campaigns the writer launches manually. You can enable either channel, both, or neither independently.
Yes. A visitor can enter an email address from the bell or subscription dialog and confirm ownership with a verification link or code. No placeholder user account is created, and email delivery is not enabled until confirmation is complete.
Email subscription is available to a visitor after verification. In-site notifications require signing in because the internal notification belongs to a user account.
The system reuses the account email when it is real and verified. If the social account has no usable email or the provider-generated address is not deliverable, the dialog asks for a real email and uses the existing account email update and verification rules.
The system supports both methods. A valid link completes the verification flow, and the code from the same message can be entered instead. Verification requests expire; after expiry or a preference change, request a new message.
No. The channels are independent. Turning off email keeps the bell subscription unchanged, and turning off site notifications does not revoke email.
Email from that writer stops while site notifications remain unchanged. The system retains the revocation and destination version needed to reject old links and prevent accidental reactivation.
When the email system is installed, legacy subscriptions can be migrated to an initial email preference so existing users do not unexpectedly lose the expected service. The migration does not override an explicit revocation, and delivery still requires a real verified address. Users can turn email off at any time.
Because ownership of the address has not been confirmed. Check spam, request a new message, or enter the code before it expires. An unconfirmed address cannot enter an eligible campaign audience.
The address is stored encrypted and remains private. The publisher sees the subscriber identity, preference state, and delivery statistics, but not the raw email address. A protected hash is used for lookup without exposing the address.
The current campaign audience is limited to this publisher’s email subscribers who pass the eligibility rules: a real verified address, no revocation or suppression, an allowed account and destination, and no cooldown or in-flight attempt. A campaign is not automatically sent to every platform user.
No. Publishing can create in-site notifications for subscribers when the feature is enabled. Email campaigns are manual: the publisher chooses content, reviews the audience and preview, and confirms the launch.
No. The current publisher campaign scope is the subscriber who opted into this writer’s email and passes eligibility. A platform user who did not subscribe to this writer is not added automatically.
The publisher has a switch on the Subscribers page for automatic article notifications. An administrator can disable the channel globally. Disabling it does not delete subscribers or cancel manual email campaigns.
The publisher chooses owned published content, then reviews filters, subscriber type, channel, search, or manual selection. Preparation freezes the audience and required versions before launch and shows exclusion reasons before delivery.
N means subscriber collection and preference management remain available, while campaign creation and delivery are locked for that membership. The system does not invent a numeric allowance; an administrator must configure a valid value in Memberships.
The allowance comes from the existing Subscriber email messages feature on the active membership. It can be numeric, Y for unlimited, or N for disabled. The code assumes no plan numbers and records usage and reservations in a separate reviewable cycle.
The feature uses the existing membership period, including daily, monthly, yearly, and 7-day periods when configured in Memberships. A new usage cycle follows the active period without deleting previous campaign history.
Used units are messages accepted by the mail provider. Reserved units belong to attempts that started but are not settled yet. Another campaign cannot consume the same reservation; a proven rejection releases it and acceptance converts it to usage.
It means the system did not receive a conclusive answer after transport started, such as a connection loss after handing the request to the provider. It does not prove failure or delivery, so the reservation is retained and the message is not retried automatically. An administrator reviews evidence and records a proven acceptance or rejection.
These are people found by the initial search or audience but rejected by final delivery rules, such as an unverified address, email revocation, a blocked account, a changed destination, a duplicate article, cooldown, or no available allowance. Zero means nobody was excluded in that campaign.
No. Acceptance only confirms that the mail provider accepted the transport request. The current system does not treat an email open or article visit as proof of delivery acceptance or as a separate read counter.
Yes. Audience preparation and recipient delivery run through jobs on the Redis connection and the dedicated email queue, supervised by Horizon. Stopping a worker prevents new starts while records and reservations remain recoverable according to their state.
Usage remains consumed because provider acceptance already happened. The bounce is recorded and the current destination is suppressed until the address is updated or reviewed. The campaign is not automatically resent and the acceptance evidence is retained.
The audit records campaign creation, launch, pause, preference changes, and delivery reviews with the actor, time, and required identifiers. It does not expose raw email addresses or send a message when viewed.
Contact support if a verification code or link does not arrive after checking spam, if a real address is marked invalid, if an attempt remains unknown, or if counts differ after preparation completes. Never send a password, secret code, or another subscriber’s email address.
Still need a hand?
Include the page link and a short description of what happened so we can follow up.