Hootsuite Social Marketing study materials
Hootsuite Social Marketing study resources

Hootsuite Social Marketing: Perch Publishing and Scheduling

Hootsuite Social Marketing · Work through your exam, one topic at a time.

All guide sections

Perch Publishing and Scheduling

Perch is the publishing surface. The exam tests scheduling mechanics - queue versus fixed time, time zone behaviour - plus per-network constraints, approval routing and tracking discipline. Most missed marks here come from assuming networks behave identically.

Scheduling mechanics

  • A scheduled post fires in the time zone configured for that social account; the calendar renders in your own local zone. Confirm which one you are reading before you choose a time.
  • The queue (auto-schedule) drops content into pre-defined slots in order; a scheduled post pins content to an exact time and bypasses the queue.
  • Evergreen recycling re-shares content on rotation. Time-sensitive posts must be excluded or they resurface after the event.
  • Drafts, bulk upload and the content library let teams stage and reuse assets before anything is queued.

Per-network constraints

  • Character limits, image and video specs, aspect ratios, mention syntax and first-comment support all vary by network.
  • Instagram requires a connected business or creator account; some formats cannot be scheduled to a personal profile at all.
  • Preview every variant. A caption that fits X will truncate on LinkedIn and bury the call to action.

Approvals and tracking

  • With an approval workflow on, posts sit pending until an approver acts, and edits after approval may re-trigger review.
  • UTM parameters must follow one convention - lowercase, fixed order - or analytics splits a single campaign into three.

Worked example

A webinar promoted on LinkedIn, X and Facebook to three time zones. Build: one master asset, three adapted captions, the same UTM set, approval routed 48 hours ahead, LinkedIn set to 09:00 audience-local rather than your local time, and X plus Facebook variants placed in the queue on staggered slots. Reasoning: the account time zone decides actual delivery, queue versus scheduled decides flexibility, and approval lead time prevents a launch-day block.

Traps

  • Scheduling in your own time zone and delivering at 3 a.m. for the audience.
  • Assuming an edited, already-approved post does not need re-approval.
  • Mixing UTM case and parameter order.
  • Recycling a time-bound post through the evergreen queue.