What are Actions?
Actions are trackable tasks representing work to improve your visibility:- Content creation - Write new documentation, guides, or blog posts
- Content optimization - Improve existing pages for better AI discoverability
- Developer relations - Community engagement and outreach
- PR and communications - Press and public relations efforts
- Engineering - Technical improvements to documentation infrastructure
- Product - Product changes that improve AI visibility
Accessing the Actions Hub
Navigate to Actions in your project sidebar (under the Overview section).Action Properties
Title
A clear, descriptive name for the action:- “Create getting started guide for Python SDK”
- “Improve API reference documentation structure”
- “Add comparison page: our product vs. Competitor X”
Description
Detailed information including:- What needs to be done
- Why it matters (linked to source insight)
- Success criteria
- Relevant context from the source insight
Status
Actions follow a defined workflow:| Status | Meaning |
|---|---|
| Open | Not yet started |
| In Progress | Currently being worked on |
| Blocked | Waiting on a dependency or external factor |
| Completed | Finished |
| Dismissed | Will not be acted on; not relevant |
| Archived | Retained for reference but no longer active |
Priority
Importance and urgency level:| Priority | Meaning |
|---|---|
| Urgent | Requires immediate action |
| High | Do soon, high impact expected |
| Medium | Important but not time-sensitive |
| Low | When resources allow |
Channel
Actions are routed to the appropriate team or function:| Channel | Description |
|---|---|
| docs | Documentation improvements |
| content | Blog posts, guides, marketing content |
| devrel | Developer relations and community |
| pr | Public relations and communications |
| engineering | Technical infrastructure changes |
| product | Product feature or design changes |
| other | Actions that do not fit other categories |
Source
Where the action came from:- From Insight - Generated from a DevTune insight, with context pre-populated
- Manual - Created directly by a team member
Creating Actions
From Insights (Suggested Actions)
When reviewing an insight that has a suggested action:- View the insight details
- Review the suggested action (title, description, channel, priority are pre-populated)
- Accept the suggestion as-is, or modify the details
- The action appears in your Actions Hub
Manual Creation
To create an action directly:- Go to the Actions Hub
- Click Add Action
- Fill in the title, description, priority, and channel
- Set the initial status (defaults to Open)
- Save
Managing Actions
Viewing Actions
The Actions Hub displays:- All actions organized by status
- Priority indicators
- Channel labels
- Source information (insight-linked or manual)
Filtering and Sorting
Organize your view by:- Status - Focus on open or in-progress items
- Priority - Urgent and high-priority first
- Channel - Filter by team responsibility
- Source - Insight-based or manual actions
Updating Status
As work progresses:- Find the action in the hub
- Update the status (Open -> In Progress -> Completed)
- Add notes if needed
- Save changes
Completing Actions
When work is done:- Update status to Completed
- Optionally add completion notes
- Monitor related metrics in Analytics to measure impact
Dismissing Actions
If an action is no longer relevant:- Update status to Dismissed
- Note the reason
- The action is preserved but marked as inactive
Archiving Actions
For completed or dismissed actions you want to keep for reference:- Update status to Archived
- The action remains searchable but does not appear in active views
Action Workflow
Recommended Process
- Review insights - Identify valuable recommendations
- Accept or create actions - Convert insights to tracked tasks, or create manual actions
- Prioritize - Set priority levels based on impact and effort
- Assign channels - Route to the right team
- Execute - Do the work
- Complete and measure - Mark done and track impact in analytics
Team Collaboration
Actions are visible to all team members:- Share understanding of what needs to be done
- Coordinate who is working on what
- Review progress together
Best Practices
Regular Triage
Periodically review your action queue:- Are priorities still correct?
- Any stale actions to dismiss or archive?
- New insights to convert into actions?
Realistic Scope
Keep actions:- Specific and actionable
- Reasonably sized (break large efforts into smaller actions)
- Clearly defined with success criteria
Track Impact
After completing actions:- Monitor the related visibility metrics
- Check if presence rate or share of voice improved for targeted prompts
- Use results to inform future prioritization