Purpose
Execute, control, and monitor outreach campaigns that convert authority research into publisher contact, responses, and link or mention opportunities.
Primary Function
Primary Function
Operationalize authority targets into structured outreach workflows with controlled messaging, response tracking, and campaign-level state management.
UI Entry Point
UI Entry Point
Left Sidebar β Authority β Digital PR
Subsections:
π£ Campaigns
π₯ Inbox
π€ Sent
π§© Templates (referenced, not defined here)
Inputs
Inputs
Campaign name and folder
Target sources (domains or keywords)
Filters (country, TLD, authority metrics, traffic)
Connected email account
Outreach message templates
Optional blacklist rules
Core Actions
Core Actions
π£ Campaign Creation
π£ Campaign Creation
Action: Create an outreach campaign targeting publishers or domains.
User actions:
Click Create new campaign
Define campaign name and folder
Select target type:
Keywords
Domains
Apply filters (TLD, country, traffic, DR, etc.)
Review and confirm targets
Execution characteristics:
Campaigns are configuration-only until emails are sent
Target scope is controlled by filters and blacklists
βοΈ Email Presence & Sending
βοΈ Email Presence & Sending
Action: Associate an email account and initiate outreach.
User actions:
Select connected email account
Review sender identity
Proceed to send outreach emails
Execution characteristics:
Emails are sent via connected inboxes
Sending state is tracked per campaign
Follow-up logic is configured separately
π¬ Response Management (Inbox)
π¬ Response Management (Inbox)
Action: Review and manage incoming replies.
User actions:
Open Inbox
Filter by campaign, contact, or milestone
Review reply content
Update status or milestone as needed
Execution characteristics:
Inbox is synchronized asynchronously
Replies are linked to originating campaigns
Manual actions do not affect sent state
π€ Outbound Monitoring (Sent)
π€ Outbound Monitoring (Sent)
Action: Review outbound outreach history.
User actions:
Open Sent
Filter by campaign or contact
Inspect delivery and send records
Execution characteristics:
Sent messages are immutable records
Used for audit, reconciliation, and campaign health checks
State Changes
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
Outputs
Outreach emails sent
Publisher replies received
Engagement signals (response rate)
Campaign-level execution metrics
Contact-level conversation records
Dependencies
Dependencies
QUEST commonly provides:
Target domains
Authority-aligned sources
Templates define message structure (but are managed separately)
Connected email accounts are required to send outreach
Non-Goals
Non-Goals
Digital PR does not:
Generate authority targets
Perform SERP or query analysis
Publish content or backlinks directly
Guarantee placements or responses
Digital PR does not manage indexing or content creation
Notes & Tips
Notes & Tips
π Campaign filters directly affect outreach quality and scale.
π Inbox replies should be reviewed before launching follow-ups.
π‘ Use folders to separate campaigns 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.
