Automation
Update

Projects read more platforms and manage organic posts through Buffer

TL;DR

A project's numbers now include AppLovin as a paid channel and Search Console, Klaviyo, Stripe, PostHog, Adobe Analytics and Buffer shown beside the KPIs — never counted in them. Organic posts a project makes in Buffer are linked to their plan item, listed on the project page and flagged for a person when the item moves or is removed.

More platforms in a project's numbers

  • AppLovin is a paid channel like Google Ads or Meta: spend, impressions, clicks and sales or installs per campaign, from the websites and apps reports. Its reports reach 88 days back; a longer period is read in part and marked partial.
  • Search Console is shown beside the KPIs, not counted in them: clicks from search are not conversions.
  • Klaviyo is shown beside the KPIs, not counted in them: its attributed revenue would be counted twice against the store and the ad platforms.
  • Stripe is shown beside the KPIs, not counted in them: it counts every charge, renewals included, and would double a store's revenue.
  • PostHog is shown beside the KPIs, not counted in them: pageviews are traffic, not conversions.
  • Adobe Analytics is shown beside the KPIs, not counted in them: the read does not know the suite's currency, and a suite without commerce would put 0 orders in place of the platforms' numbers.
  • Buffer is shown beside the KPIs, not counted in them: organic posts have no spend.
  • A project reads Adobe Analytics numbers for a report suite it names among its campaigns (its rsid or its name); with several suites and none named, the project lists them instead of guessing.
  • These sources load after the ad channels and the store, each within a time limit, so a slow one never holds up spend or store numbers.
  • Microsoft Clarity is not read: its data covers only the last 1–3 days.

Organic posts through Buffer

  • When a Buffer channel is in the project, the plan schedules each organic post through Buffer, one post per plan item.
  • A post a project task drafts, schedules or publishes is linked to its plan item and listed on the project's Overview, marked “via Buffer”, with its status read back from Buffer.
  • When an item's dates move or it is removed, its post is flagged for a person — never moved or deleted on its own. An admin or editor chooses Move to the proposed time, Keep its time or Cancel.
  • A flag cannot stop Buffer: a scheduled post still goes out at its time unless someone decides. The page and the project's email say so.
  • Keep its time sticks until the item's dates change again — the post is not flagged again on every check.
Tested on a real Buffer account with a draft (created, linked to a project, listed and deleted); nothing was scheduled or published. How projects work · Buffer

Platforms in this article

Try it on your own account

Start free — 2,500 credits a month, no credit card. Reads run at once, and writes wait for your approval by default.

Related releases