📣 Purpose
Execute, control, and monitor outreach campaigns that convert authority research into publisher contact, responses, and link or mention opportunities.
🎯 Primary Function
Operationalize authority targets into structured outreach workflows with controlled messaging, response tracking, and campaign-level state management.
🧭 UI Entry Point
Left Sidebar → Authority → Authority Building / PR Distribution (Press Releases)
Subsections: Campaigns, Inbox, Sent, and Templates (referenced, not defined here).
📥 Inputs
- Campaign name
- Source type (currently SERP; Google Maps and Backlinks sources are coming soon) and keyword targeting
- Filters (country, TLD, optional filters, skip catch-all domains)
- Connected email account
- Outreach message templates
A global blocklist for excluding domains from outreach also exists, but it is managed as a separate module-level setting rather than a field inside campaign creation.
📝 Campaign Creation
Action: Create an outreach campaign targeting publishers or domains, using a guided multi-step wizard.
User actions: click Create new campaign, name the campaign, choose a source type, define keyword targeting, apply filters (country, TLD, and other optional filters), select a connected email account, and choose or attach templates for the outreach sequence.
Campaigns are configuration-only until emails are sent, and target scope is controlled by filters and the global blocklist.
✉️ Email Presence & Sending
Action: Associate an email account and initiate outreach.
User actions: select a connected email account, review sender identity, and proceed to send outreach emails.
Emails are sent via connected inboxes, sending state is tracked per campaign, and follow-up logic is configured separately.
📬 Response Management (Inbox)
Action: Review and manage incoming replies.
User actions: open Inbox, filter by campaign, contact, or milestone, review reply content, and update status or milestone as needed.
The Inbox is synchronized asynchronously, replies are linked to originating campaigns, and manual actions do not affect sent state.
📤 Outbound Monitoring (Sent)
Action: Review outbound outreach history.
User actions: open Sent, filter by campaign or contact, and inspect delivery and send records.
Sent messages are immutable records, used for audit, reconciliation, and campaign health checks.
🔄 State Changes
Campaign lifecycle: Draft → Active → Completed (logical state); state reflects outreach activity, not success.
Contact-level states: Not contacted → Emailed → Replied; reply state appears only in Inbox.
Email synchronization: Pending sync → Available; sync delays do not affect send execution.
📊 Outputs
- Outreach emails sent
- Publisher replies received
- Engagement signals (response rate)
- Campaign-level execution metrics
- Contact-level conversation records
🔗 Dependencies
- QUEST commonly provides target domains and authority-aligned sources
- Templates define message structure (but are managed separately)
- Connected email accounts are required to send outreach
🚫 Non-Goals
Digital PR does not generate authority targets, perform SERP or query analysis, publish content or backlinks directly, or guarantee placements or responses. Digital PR does not manage indexing or content creation.
📝 Notes & Tips
- Campaign filters directly affect outreach quality and scale
- Inbox replies should be reviewed before launching follow-ups
- Use the campaign list to organize outreach by client, topic, or strategy
- Sent view is a monitoring tool, not a control surface
Digital PR defines the execution and control layer of outreach in Search Atlas. It translates authority targets into structured campaigns, enforces messaging discipline through templates, and provides visibility into outbound and inbound communication states.
No research or authority discovery occurs in this layer. Its responsibility is execution integrity, response tracking, and operational clarity. Authority creation and visibility outcomes depend on inputs provided by QUEST and execution volume controlled at the campaign level.
For message standardization and scale, refer to the Templates documentation.
If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.