Social accounts and advertising
In plain words: Reach: Social accounts and advertising
An assessment of what account access each social provider (Facebook, LinkedIn, X) requires for posting, and why posting permission never becomes permission to run paid advertising.
- 1Facebook needs a Page and posting permission; LinkedIn organization posting needs separate approval.
- 2X posting needs user-delegated OAuth; automatic replies and DMs are different operations.
- 3Prepare content and author first; spending money on ads is a separate, later capability.
Designed Assessment; local preparation exists, live onboarding does not.
Words on this page, decoded click one for its card
A founder wants to describe their AI service on Facebook and LinkedIn, answer interested people, and eventually pay to distribute a campaign. Those are different operations with different account and provider permissions. Prepare the content and exact author first; an ordinary publication grant cannot silently become authority to spend money.
The following official-source assessment was checked 2026-10-29. The connected preparation profile implements local request construction. Account onboarding, API access approval and live publication remain separate qualification work.
Pick the account and the operation
| Service | Supported direction | What account access does not imply |
|---|---|---|
A Page post as the configured Page with eligible tasks and pages_manage_posts. |
A Page token does not supply ordinary personal-profile publishing. Page posts. | |
Member publishing with w_member_social; organization publishing with w_organization_social and an eligible organization role. |
Organization Community Management access requires its own approval; member sharing does not grant organization or advertising access. Getting access, Posts API. | |
| X | Original public posts with user-delegated OAuth. | App-only bearer access does not authorize posting as a person. Automatic replies and private DMs are different operations. OAuth, Create Posts. |
Email, Chat and Forge own the other provider-family routes. This assessment stays with the Social post contract and its advertising boundary.
X requires prior written explicit approval for an AI reply bot. Its automation policy also
restricts unsolicited automated replies/DMs and requires a working opt-out. This profile prepares
original posts; it does not establish that approval or provide a reply bot. Prepared AI-authored
posts include the API's made_with_ai field. Automation rules,
post request
Promotional content before paid distribution
LinkedIn commentary uses its little markup syntax. The builder escapes reserved characters to
preserve literal input, and conservatively caps the encoded commentary at 3,000 UTF-16 units.
It refuses excess text rather than splitting one reviewed post into several effects.
Text syntax,
post length
For the first founder journey, begin by accepting the service's claims and creative assets. Prepare one Facebook Page post and one LinkedIn post, then review each exact author, text and audience. A future qualified delivery path must admit each publication separately because cross-posting makes a new disclosure at each destination. Provider acceptance of a post establishes none of its reach, engagement or sales.
Images and video require separately admitted upload artifacts and returned media references; the present connector subset constructs text requests. It does not scrape link previews, generate assets, upload media or boost a post. Broadcast release retains editorial acceptance, claims, credits, disclosures and publication judgment.
Paid campaigns need a separately reviewed request binding at least:
- The advertiser, platform, ad account, campaign objective and permitted product.
- Exact accepted creative, destination URL, audience and targeting constraints.
- Currency, daily or lifetime budget, bid constraints, start/end and total spend ceiling.
- Draft versus activation, current account role, provider policy eligibility and review identity.
- Per-operation receipt, unknown-state reconciliation, and an independently admitted pause action.
This is a design boundary, not a delivered advertising request type or campaign executor. Do not infer activation authority from approval of the copy, a Page role, or a successful upload.
Meta's Marketing API uses ads_read and ads_management for the corresponding operations.
Own-account versus other-account access differs. Limited/Full Marketing API tiers are separate
from Standard/Advanced permission access, and development-tier calls still touch production
data. Marketing authorization
LinkedIn Advertising requires separate access approval and appropriate ad-account roles. Its
development tier permits edits to up to five administered ad accounts. Version 202610 adds
member/organization boost scopes, which do not follow from ordinary posting. Never silently
upgrade an organic post into a charged boost. Access tiers and permissions
Protocol changes and recovery
The social subset pins Meta GraphStep Map v26.0 and LinkedIn 202610 with Rest.li 2.0.0.
Those pins need maintenance and qualification before live transport; they are not a promise of
permanent provider compatibility.
Page posts,
LinkedIn posts
The builders stop after constructing requests: they do not retry, rotate accounts, fetch links, open sessions or send. A future transport must check current authority, exact destination, provider limits and eligibility, then persist its attempt before submission. Record whether the result is rejected, accepted or unknown. Provider acceptance alone cannot establish exactly-once delivery; a timeout after submission must never cause WUPHF to send again to every destination.
Social · Preparation and user stories · Account lifecycle · Delivery gates