Skip to main content

πŸ“£ Digital PR β€” Outreach Execution & Control (Search Atlas)

Operational outreach layer for executing campaigns, managing replies, and controlling publisher engagement at scale.

Updated yesterday

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 β†’ Digital PR

Subsections:

  • πŸ“£ Campaigns

  • πŸ“₯ Inbox

  • πŸ“€ Sent

  • 🧩 Templates (referenced, not defined here)

Inputs

  1. Campaign name and folder

  2. Target sources (domains or keywords)

  3. Filters (country, TLD, authority metrics, traffic)

  4. Connected email account

  5. Outreach message templates

  6. Optional blacklist rules

Core Actions

πŸ“£ 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

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)

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)

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

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

  1. QUEST commonly provides:

    • Target domains

    • Authority-aligned sources

  2. Templates define message structure (but are managed separately)

  3. 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

    • Guarantee placements or responses

  • Digital PR does not manage indexing or content creation

Notes & Tips

  1. πŸ“ Campaign filters directly affect outreach quality and scale.

  2. πŸ“ Inbox replies should be reviewed before launching follow-ups.

  3. πŸ’‘ Use folders to separate campaigns by client, topic, or strategy.

  4. πŸ“ 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.

Did this answer your question?