Creating Missions¶
Well-designed missions produce better content. This guide covers how to craft missions that achieve your marketing goals.
Mission Design Principles¶
1. Start with Clear Objectives¶
Objectives guide the AI's content strategy. Vague objectives produce generic content.
Good objectives:
- "Establish thought leadership in API design best practices"
- "Drive traffic to our new documentation site"
- "Generate beta signups from developer community"
Weak objectives:
- "Get more engagement" (too vague)
- "Be more visible" (not actionable)
- "Post good content" (not measurable)
2. Match Duration to Goals¶
| Goal Type | Recommended Duration |
|---|---|
| Campaign launch | 7-14 days |
| Ongoing presence | 30-90 days |
| Event promotion | 3-7 days |
| Brand building | 90+ days |
3. Choose Appropriate Platforms¶
Don't spread too thin. Start with 1-2 platforms and expand:
| Audience | Primary Platform | Secondary |
|---|---|---|
| Developers | ||
| B2B Enterprise | ||
| Consumers | ||
| Gen Z | TikTok |
Mission Types¶
Awareness Campaign¶
Build visibility for a new product or feature:
{
"name": "New Feature Awareness",
"objectives": [
"Announce new API versioning feature",
"Educate existing users on migration path",
"Drive traffic to documentation"
],
"platforms": ["twitter", "linkedin"],
"constraints": {
"tone": "excited but professional",
"cadence": "daily",
"posts_per_day": 2,
"posting_times": ["09:00", "14:00"]
},
"kpis": [
{"metric": "impressions", "target": 50000},
{"metric": "link_clicks", "target": 500}
],
"duration_days": 14
}
Thought Leadership¶
Establish expertise in your domain:
{
"name": "API Design Thought Leadership",
"objectives": [
"Position as experts in API design",
"Share unique insights and learnings",
"Build engaged developer following"
],
"platforms": ["twitter", "linkedin"],
"constraints": {
"tone": "authoritative but accessible",
"cadence": "daily",
"posts_per_day": 1,
"content_types": ["thread", "article"]
},
"kpis": [
{"metric": "engagement_rate", "target": 5.0},
{"metric": "followers_gained", "target": 500}
],
"duration_days": 90
}
Event Promotion¶
Drive registrations for an event:
{
"name": "Conference Speaking Promotion",
"objectives": [
"Drive registrations for conference talk",
"Build anticipation for presentation",
"Establish speaker credibility"
],
"platforms": ["twitter", "linkedin"],
"constraints": {
"tone": "enthusiastic and professional",
"cadence": "daily",
"posts_per_day": 2,
"hashtag_preferences": {
"always_use": ["#TechConf2024"]
}
},
"kpis": [
{"metric": "link_clicks", "target": 200},
{"metric": "impressions", "target": 20000}
],
"duration_days": 7
}
Ongoing Brand Presence¶
Maintain consistent social presence:
{
"name": "Ongoing Social Presence",
"objectives": [
"Maintain consistent brand visibility",
"Engage with developer community",
"Share relevant industry content"
],
"platforms": ["twitter", "linkedin", "instagram"],
"constraints": {
"tone": "friendly and helpful",
"cadence": "daily",
"posts_per_day": 2,
"require_approval": false
},
"kpis": [
{"metric": "engagement_rate", "target": 3.0},
{"metric": "impressions", "target": 100000, "period": "monthly"}
],
"duration_days": 90
}
Constraint Configuration¶
Tone¶
Be specific about how you want to sound:
| Instead of... | Try... |
|---|---|
| "professional" | "professional yet approachable, technical when needed" |
| "casual" | "conversational and witty, avoiding slang" |
| "friendly" | "warm and helpful, like a knowledgeable colleague" |
Cadence Options¶
| Cadence | Posts/Day | Best For |
|---|---|---|
hourly | 3-5 | News, live events |
daily | 1-2 | Standard presence |
weekly | 2-3/week | Thought leadership |
bi_weekly | 1/week | Quality over quantity |
Posting Times¶
Specify times in 24-hour format with timezone:
Or let AMP optimize:
Budget Controls¶
Limit AI generation costs:
KPI Configuration¶
Setting Realistic Targets¶
Base targets on industry benchmarks or historical data:
| Platform | Avg Engagement Rate |
|---|---|
| 1-3% | |
| 2-4% | |
| 3-6% |
KPI Types¶
{
"kpis": [
{
"metric": "engagement_rate",
"target": 4.0,
"platform": "twitter"
},
{
"metric": "impressions",
"target": 100000,
"platform": "all"
},
{
"metric": "link_clicks",
"target": 500,
"platform": "all"
}
]
}
Multi-Objective Missions¶
Balance multiple goals with objective weighting:
{
"objectives": [
{
"text": "Drive product awareness",
"weight": 0.5
},
{
"text": "Establish thought leadership",
"weight": 0.3
},
{
"text": "Engage existing community",
"weight": 0.2
}
]
}
Testing Missions¶
Before launching a long campaign, test with a short mission:
- Create a 3-day mission with
require_approval: true - Review all generated content carefully
- Adjust brand context or constraints based on output
- Launch the full mission
Mission Lifecycle Management¶
Monitoring Active Missions¶
# Get mission status
curl https://api.amp.dev/v1/missions/{id}/status
# View content quality
curl https://api.amp.dev/v1/content?mission_id={id}&status=published
# Check KPI progress
curl https://api.amp.dev/v1/analytics/missions/{id}
Mid-Flight Adjustments¶
Update constraints without stopping the mission:
curl -X PUT https://api.amp.dev/v1/missions/{id} \
-H "Authorization: Bearer $AMP_API_KEY" \
-d '{
"constraints": {
"posts_per_day": 3
}
}'
When to Pause¶
Consider pausing when:
- Content quality drops below standards
- External events make content inappropriate
- KPIs are significantly underperforming
- Budget is nearly exhausted
Best Practices¶
- Start small — Test with short missions before committing to long campaigns
- Be specific — Detailed objectives produce better content
- Set realistic KPIs — Unrealistic targets skew optimization
- Review early — Check first few pieces of content carefully
- Iterate — Adjust based on performance data
- Document learnings — Keep notes on what works for your brand