Use platform and account overrides
Adapt common content without fragmenting one campaign into unrelated posts.
Start with a common caption and media set, then add platform configurations for network-wide fields and account-specific overrides for exceptional targets. The effective target payload should be previewed and validated after all override layers are applied.
What this means in practice
Start with a common caption and media set, then add platform configurations for network-wide fields and account-specific overrides for exceptional targets. The effective target payload should be previewed and validated after all override layers are applied.
Use the documented brand and account boundaries consistently across the scheduler, REST API, SDK, MCP tools, SSE consumers, and webhooks. That makes the same social operation explainable to an operator and reproducible by an integration.
Implementation checklist
Write a common campaign message that is safe for every selected audience.
Add provider-specific fields such as a YouTube title, Pinterest board, Instagram placement, or X poll only when capabilities allow them.
Use account-specific copy for locale, brand, disclosure, or destination differences.
Show users the resolved preview for each target rather than only the base content.
Persist revisions so reviewers can see what changed after an earlier approval.
Operational details
Overrides should be structured fields, not unvalidated opaque provider payloads.
The capability matrix and REST validation use the same provider rules.
A client can omit an override and allow the common value to flow through unchanged.
Common mistakes to avoid
- Do not copy an unsupported field from one provider configuration into another.
- Do not make reviewers compare raw JSON when a resolved target preview can show the result.
- Do not overwrite common content when editing one account's exception.