Skip to main content

Social publishing hub

How to use it​

  1. Connect your accounts in Connections. The hub shows which platforms are live.
  2. Compose — pick a source (a product, a collection, or a blog post to repurpose), a platform and a tone.
  3. Schedule it onto the calendar, or send it to the queue immediately.
  4. Approve if your store requires it.
  5. Read analytics after a couple of weeks, and run a caption A/B test on whatever you post most.

⏱ ~15 min setup · 💳 Starter to generate, Pro to publish · 🎯 Consistent social without a separate tool

Platforms​

PlatformCaption budgetHashtag ceilingPublishing
Instagram20030Adapter available, gated
Facebook3005Adapter available, gated
X (Twitter)2403Available
Pinterest2008Available
TikTok1508Generation only — no third-party publishing API
LinkedIn7005Adapter available, gated
YouTube10015Adapter available, gated
Threads5005Adapter available, gated
Google Business1,500—Adapter available, gated
"Adapter available" is not the same as "you can post today"

Two separate things have to be true: an adapter exists in the platform, and it is enabled for merchant use. Instagram and Facebook publishing, for example, depend on platform review of the specific publishing permissions.

The Connections view is the authority for your store — it reads live connection status rather than a static list, so what it shows is what will actually be accepted.

TikTok is a permanent exception rather than a gate: no third-party publishing API exists, so the hub generates captions you post yourself.

The nine views​

ViewWhat it does
ComposeGenerate and edit a caption for a source and platform
CalendarThe schedule, month and week
QueueThe publish board by lifecycle state, with retry
AnalyticsEngagement and revenue per post (Pro)
ApprovalsPosts held for review
A/B testsCaption experiments (Pro)
HashtagsYour reusable hashtag sets
ConnectionsConnected accounts and their status
SettingsDefaults, cadences and approval rules

Composing​

The composer starts from something real in your store rather than a blank box:

SourceWhat it produces
ProductA caption built from the product's own copy and attributes
CollectionA collection-level post
Blog postA repurpose — turning an article into several social posts

Tone and platform are chosen per post, and the character budget for the selected platform is enforced in the composer, so a caption is not silently truncated at publish time.

Hashtag sets are stored in the library and inserted rather than retyped, with the platform's practical ceiling applied.

The publish queue​

A publish is a tracked row with a lifecycle. The queue board is organised by state, and each state offers the actions that make sense for it — reschedule, retry, cancel, or send for approval.

This matters because social APIs fail in ordinary ways: a token expires, a media upload times out, a platform rate-limits. A fire-and-forget publish leaves you finding out from a customer that the post never went up.

Approvals​

Where your store requires it, a publish is held until approved. Approval is a separate permission from creating a publish, so a junior team member can compose and schedule while someone else decides what goes live.

Cadences​

A cadence is a recurring posting schedule — "a product post every Tuesday and Friday" — that keeps the calendar populated without someone remembering to fill it each week.

Caption A/B tests​

Caption experiments compare variants on the same source. Because engagement data comes back per post, results are measured on what actually happened rather than on a preview.

Analytics​

MetricWhat it answers
EngagementImpressions, reactions, comments, saves and clicks per post
RevenueOrders and revenue attributable to social traffic
Per-platformWhich platforms earn their time
Per-sourceWhether products, collections or blog repurposes perform better
Cross-store portfolioFor agencies, performance across client stores (Agency+)

The revenue view is the point. Engagement without revenue tells you a post was interesting; the combination tells you whether the channel is worth the effort.

Permissions​

PermissionGrantsMinimum plan
social:generateGenerate captionsStarter
social:publish:createPublish immediatelyPro
social:publish:scheduleSchedule a publishPro
social:connection:manageConnect and disconnect accountsPro
social:approveApprove or reject held publishesPro
social:analytics:viewEngagement and revenue analyticsPro
social:cadence:manageRecurring cadencesPro
social:experiment:manageCaption A/B testsPro

Plan tiers​

CapabilityFreeStarterProAgencyEnterprise
Caption generation—✓✓✓✓
Hashtag library—✓✓✓✓
Publishing and scheduling——✓✓✓
Publish queue, retries, approvals——✓✓✓
Recurring cadences——✓✓✓
Engagement + revenue analytics——✓✓✓
Bulk generation——✓✓✓
Caption A/B tests——✓✓✓
AI creative and media pipeline——✓✓✓
Multiple accounts per platform———✓✓
Cross-store social portfolio———✓✓

Publishing and analytics are Pro because they carry recurring platform-API and model cost; multi-account is the agency workflow and sits at Agency.

Best practices​

  • Check Connections before you schedule a month. A post scheduled to a platform your store cannot publish to will not go out.
  • Repurpose blog posts. It is the highest-yield source in the composer and the one most stores forget they have.
  • Build hashtag sets per collection, not per post. The library exists so the research is done once.
  • Set a cadence rather than batching. Consistency outperforms volume on every platform here.
  • Judge on the revenue column. Engagement is a leading indicator, not the result.

See also​