Launch
Launch is the publishing phase of the campaign lifecycle. It is the moment outputs transition from ready to live — content is published, posts go out, and the campaign reaches its audience. In March, launching happens at the output level: you publish individual outputs through connected integrations as they are ready.
What happens in Launch
Section titled “What happens in Launch”During Launch, the team publishes the outputs that were created and finalized in Coordinate. Depending on the campaign, this can happen all at once or be spread across a schedule.
Common launch activities include:
- Posting to social channels — Publishing to X, LinkedIn, Instagram, Threads, TikTok, and other platforms.
- Pushing to CMS — Publishing blog posts and content to GitHub (as Markdown with frontmatter) or Sanity (as CMS documents).
- Notifying the team — Sending Slack messages when content goes live.
Publishing from March
Section titled “Publishing from March”When an output has a status of Ready, you can publish it directly from the output detail view. Select the target platform and March handles the rest. The output status changes to Published and March records metadata:
- Platform — Where the content was published.
- Post ID — The identifier on the external platform.
- Post URL — A direct link to the published content.
- Published at — The timestamp of publication.
This metadata stays attached to the output, so you can always trace where and when something was published.
Scheduling with the calendar
Section titled “Scheduling with the calendar”Outputs with target dates appear on the calendar view. You can plan a launch schedule by setting target dates during Coordinate and then publishing outputs on those dates. Drag and drop outputs on the calendar to adjust timing.
This approach supports rolling launches — you don’t need to publish everything at once. A content series might publish one article per day, while a product launch might publish all outputs simultaneously.
Publishing without integrations
Section titled “Publishing without integrations”If your team publishes through platforms that are not connected to March, you can still use March as the coordination layer. Team members publish content manually in their respective tools and then update the output status to Published in March. This keeps the campaign view accurate even without automated publishing.
Supported publishing integrations
Section titled “Supported publishing integrations”| Platform | What Gets Published |
|---|---|
| X, LinkedIn, Instagram, TikTok, Threads, Facebook, YouTube, Medium, Discord, Telegram, Press Release, Generic | Social posts |
| GitHub | Markdown files with configurable frontmatter and branch |
| Sanity | CMS documents with field mappings |
| Slack | Team notifications |
See the Integrations page for the full list and setup details.
After publishing
Section titled “After publishing”Once outputs are published, analytics begin flowing in automatically from connected platforms:
- Social analytics — Impressions, reach, likes, comments, shares, and engagement data for each published post.
- Website analytics — Pageviews, unique visitors, and referrer breakdowns from Google Analytics 4 or PostHog for published content.
These metrics are attached to individual outputs, giving you a direct line from the content you shipped to the results it produced.
Example
Section titled “Example”An e-commerce team launches a seasonal campaign. The campaign has six outputs: two LinkedIn posts, an email, a blog article, and two Instagram posts. The blog article is published to GitHub on Monday. The LinkedIn posts go out Tuesday and Thursday. The Instagram posts are published Friday. Each output is published directly from March, and its status changes to Published automatically. By the end of the week, the team can see social engagement data flowing in for each post.
Related pages
Section titled “Related pages”- Coordinate — The phase before Launch.
- Improve — Reviewing results after Launch.
- Outputs — The deliverables published during Launch.
- Integrations — Platforms that automate publishing and tracking.