Analytics & Optimization¶

AMP's optimization loop analyzes performance data and automatically improves content strategy. This guide covers how to leverage analytics effectively.

The Optimization Loop¶

graph LR
    P[Publish] --> A[Analyze]
    A --> I[Insights]
    I --> O[Optimize]
    O --> G[Generate]
    G --> P

1. Publish — Content goes live
2. Analyze — Collect performance metrics
3. Insights — Identify patterns and trends
4. Optimize — Adjust strategy parameters
5. Generate — Create improved content

Metrics Collected¶

Engagement Metrics¶

Traffic Metrics¶

Growth Metrics¶

Accessing Analytics¶

Overview Dashboard¶

curl https://api.amp.dev/v1/analytics?period=30d \
  -H "Authorization: Bearer $AMP_API_KEY"

Mission-Specific¶

curl https://api.amp.dev/v1/analytics/missions/{id} \
  -H "Authorization: Bearer $AMP_API_KEY"

Content-Level¶

curl https://api.amp.dev/v1/content/{id}/analytics \
  -H "Authorization: Bearer $AMP_API_KEY"

Understanding KPI Progress¶

KPI Status Values¶

Example Response¶

{
  "kpi_progress": [
    {
      "metric": "engagement_rate",
      "target": 4.0,
      "current": 3.8,
      "progress_percent": 95,
      "status": "on_track",
      "trend": "improving",
      "projected_final": 4.2
    }
  ]
}

Optimization Insights¶

The optimization stage generates actionable insights:

Timing Insights¶

{
  "type": "timing",
  "finding": "Tuesday 2pm posts outperform Monday 9am by 40%",
  "confidence": 0.87,
  "action_taken": "Shifted 30% of Monday posts to Tuesday afternoon"
}

Content Insights¶

{
  "type": "content",
  "finding": "Threads with code snippets get 2.3x engagement",
  "confidence": 0.91,
  "action_taken": "Increased code snippet frequency from 20% to 40%"
}

Topic Insights¶

{
  "type": "topic",
  "finding": "API design posts outperform general DevOps by 1.8x",
  "confidence": 0.85,
  "action_taken": "Increased API design weight from 25% to 40%"
}

Manual Optimization¶

Adjusting Strategy¶

Override optimization decisions:

curl -X PUT https://api.amp.dev/v1/missions/{id} \
  -H "Authorization: Bearer $AMP_API_KEY" \
  -d '{
    "optimization_overrides": {
      "topic_weights": {
        "API design": 0.5,
        "DevOps": 0.3,
        "Culture": 0.2
      },
      "preferred_times": ["14:00", "16:00"],
      "content_types": ["thread", "post"]
    }
  }'

Disabling Auto-Optimization¶

curl -X PUT https://api.amp.dev/v1/missions/{id} \
  -H "Authorization: Bearer $AMP_API_KEY" \
  -d '{
    "constraints": {
      "auto_optimize": false
    }
  }'

Performance Analysis¶

Top Performers¶

Identify what works:

curl "https://api.amp.dev/v1/analytics/performance?sort=-engagement_rate&limit=10" \
  -H "Authorization: Bearer $AMP_API_KEY"

Underperformers¶

Find what doesn't work:

curl "https://api.amp.dev/v1/analytics/performance?sort=engagement_rate&limit=10" \
  -H "Authorization: Bearer $AMP_API_KEY"

Pattern Analysis¶

Break down by dimension:

curl "https://api.amp.dev/v1/analytics/performance?breakdown=type,topic,time" \
  -H "Authorization: Bearer $AMP_API_KEY"

Comparative Analysis¶

Period Comparison¶

curl "https://api.amp.dev/v1/analytics/compare?period1=2024-01-01/2024-01-15&period2=2023-12-15/2023-12-31" \
  -H "Authorization: Bearer $AMP_API_KEY"

Mission Comparison¶

curl "https://api.amp.dev/v1/analytics/compare?mission_ids=msn_xxx,msn_yyy" \
  -H "Authorization: Bearer $AMP_API_KEY"

Reporting¶

Scheduled Reports¶

Configure automatic reports:

curl -X POST https://api.amp.dev/v1/reports \
  -H "Authorization: Bearer $AMP_API_KEY" \
  -d '{
    "name": "Weekly Performance",
    "frequency": "weekly",
    "day": "monday",
    "time": "09:00",
    "timezone": "America/New_York",
    "recipients": ["team@company.com"],
    "include": ["summary", "top_content", "kpi_progress", "insights"]
  }'

Export Data¶

curl -X POST https://api.amp.dev/v1/analytics/export \
  -H "Authorization: Bearer $AMP_API_KEY" \
  -d '{
    "format": "csv",
    "period": "30d",
    "include": ["content", "metrics"]
  }'

Best Practices¶

1. Set Baseline First¶

Run a mission for 2 weeks with consistent settings before enabling optimization to establish a baseline.

2. Trust the System¶

Optimization needs time to show results. Avoid making manual changes in the first 2 weeks.

3. Review Insights Weekly¶

Check optimization insights regularly:

curl https://api.amp.dev/v1/missions/{id}/optimizations \
  -H "Authorization: Bearer $AMP_API_KEY"

4. Use Realistic KPIs¶

Unrealistic targets can cause over-optimization. Base KPIs on historical data.

5. Monitor Long-term Trends¶

Short-term fluctuations are normal. Focus on week-over-week trends.

Optimization Limits¶

To prevent drastic changes, optimization has guardrails:

Troubleshooting¶

Analytics not updating¶

• Check platform connection status
• Verify Metricool API is accessible
• Wait for sync cycle (up to 6 hours)

Optimization not improving results¶

• Ensure sufficient data (at least 20 posts)
• Check if KPIs are realistic
• Review if content quality is consistent

Unexpected strategy changes¶

• Review optimization insights for rationale
• Check confidence scores on insights
• Consider adding optimization overrides