Did the post go out? Amplify, a social media management app records it

Description and use

Amplify records post publishing outcomes, distinguishing live, simulated, and failed deliveries, enabling marketers to verify real posts and operators to audit performance.

Problem

Marketers need to know whether a scheduled post was actually published to a social network or only simulated, and operators need to track post outcomes and errors.

Outcome

Amplify records the outcome of each publish attempt, enabling marketers to verify real posts and operators to audit post performance. The system distinguishes live, simulated, and failed deliveries and stores provider IDs and error messages.

Workflow

• 1. User clicks Publish on a post in Amplify.
• 2. The app calls realPost for the selected channel; if the channel is not supported, realPost returns null.
• 3. If realPost succeeds, the row is saved with delivery:'live' and provider_post_id; if it fails or is unsupported, the row is saved with delivery:'simulated' and publish_error.
• 4. A pop‑up informs the user of the result (e.g., "Posted to LinkedIn for real" or "Simulated – connect the channel").

Evidence

Press Publish on a post in Amplify and the app stores what happened next. The evidence is on the row.

Source

If the provider answers with an id or a success status, the row is saved with delivery: "live" and that id in provider_post_id, and if the call throws, or comes back without a confirmation, or realPost has no call for that network, the row is saved with delivery: "simulated"

Source

The hosted demo simulates posting, so a Publish there does not reach a real social network.

Source

The same filter sits on the three working objects (channel, campaign, post) with create and update added. This is policy-based row scoping, and the workspace rule is read-only for the marketer.

Source