MokoConsulting/MokoSuiteCross
1
0
Fork 0
Code Issues 25 Pull Requests 1 Releases 2 Wiki Activity

Best time to post: engagement analytics and scheduling recommendations #165

New Issue
Open
opened 2026-06-23 13:40:20 +00:00 by jmiller · 0 comments
jmiller commented 2026-06-23 13:40:20 +00:00
Owner
Copy Link
Copy Source

Summary

Analyze historical cross-post engagement data to recommend optimal posting times per platform. Buffer, Hootsuite, Sprout Social (ViralPost), and Publer all offer this.

Data Collection

Track engagement metrics when available:

  • platform_response JSON already stores API responses
  • Some platforms return view/like/share counts on subsequent API calls
  • Add a scheduled task to poll engagement data for recent posts

Analysis

Per-Service Heatmap

  • Day of week x hour of day grid
  • Color intensity based on engagement rate
  • Minimum 30 posts per service before recommendations

Recommendation Engine

  • Suggest best posting times per service
  • Factor in timezone
  • Update weekly from new data

Implementation

New Table: #__mokosuitecross_analytics

  • post_id, service_id
  • impressions, clicks, likes, shares, comments
  • fetched_at

Scheduled Task

  • plg_task_mokosuitecross already exists
  • Add analytics fetch routine (poll platforms for post metrics)
  • Run daily for posts from last 7 days

Dashboard Widget

  • Heatmap visualization
  • Recommended posting times per service

Acceptance Criteria

  • Analytics data collection from platform APIs
  • Heatmap visualization on dashboard
  • Per-service recommended posting times
  • Timezone-aware analysis

Priority

Tier 2 -- Medium Impact, High Effort. Requires engagement data accumulation over time. v02.00.00 target.

## Summary Analyze historical cross-post engagement data to recommend optimal posting times per platform. Buffer, Hootsuite, Sprout Social (ViralPost), and Publer all offer this. ## Data Collection Track engagement metrics when available: - `platform_response` JSON already stores API responses - Some platforms return view/like/share counts on subsequent API calls - Add a scheduled task to poll engagement data for recent posts ## Analysis ### Per-Service Heatmap - Day of week x hour of day grid - Color intensity based on engagement rate - Minimum 30 posts per service before recommendations ### Recommendation Engine - Suggest best posting times per service - Factor in timezone - Update weekly from new data ## Implementation ### New Table: `#__mokosuitecross_analytics` - `post_id`, `service_id` - `impressions`, `clicks`, `likes`, `shares`, `comments` - `fetched_at` ### Scheduled Task - `plg_task_mokosuitecross` already exists - Add analytics fetch routine (poll platforms for post metrics) - Run daily for posts from last 7 days ### Dashboard Widget - Heatmap visualization - Recommended posting times per service ## Acceptance Criteria - [ ] Analytics data collection from platform APIs - [ ] Heatmap visualization on dashboard - [ ] Per-service recommended posting times - [ ] Timezone-aware analysis ## Priority Tier 2 -- Medium Impact, High Effort. Requires engagement data accumulation over time. v02.00.00 target.
Sign in to join this conversation.
Labels
No items
No labels
Priority Medium
Type Feature
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoSuiteCross#165
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?