HELP · CREATE AND SEND POSTS
Label your posts and follow them to results
Growfinch learns what works for your business from the posts you send it. Two things make that learning sharp: a few labels on each post, and a link that can be followed to your website and its results. This page is the prompt to paste to your own agent, pipeline or developer, and what each part means.
Updated 5 November 2026 · Growfinch
The prompt to paste
Replace <your business> and the examples with your own. If an agent builds your posts, paste it there; if a person does, this is the brief. It works with the REST API and with Claude through MCP alike, because both send the same campaign body.
Growfinch asks for two things on every post <your business> sends it. Nothing here changes what the posts say.
1. Labels on every post (posts[].meta in the campaign body; snake_case keys, string values of at most 120 characters, the same spelling every time, lower-case; unknown keys are refused):
- content_pillar: the pillar the post belongs to, one word used consistently (for example education, product, community, behind_the_scenes).
- topic_category: the subject in a few words (for example pricing, onboarding, case_study, local_events).
- hook_type: how the caption opens, one of question · number_or_date · context · statement (context is a line of setting before a question).
- cta_type: what the words ask the reader to do, one of play · watch · read · visit · comment · none.
- When known: creative_format, and duration_seconds (a number) for video.
Send the same values on every platform variant of a package unless the caption truly differs. Until the labels arrive, Growfinch derives the pillar and the hook from the words and marks them "derived"; the day they arrive, the labels replace the derived values. Run POST /v1/campaigns/validate once with a labelled body before switching.
2. Attribution from the post to the outcome, on <your business>'s side, so a social post can be followed to a website session and a result without any person's identity leaving your systems:
- Every outbound link in a post or first reply carries utm_source (x · instagram · youtube), utm_medium (post · reply), utm_campaign, and a persistent utm_content that identifies the publishing variant: one value per package and platform (for example 2026-11-03-launch-instagram), never reused. Growfinch reads utm_content from the link when the campaign arrives and keeps it as the post's attribution key.
- Store the utm_content on the landing session and keep it for 7 days on the visitor's side.
- Record the events that matter to the business against the session's key: visit, signup, lead, purchase, or custom:<name> for another meaningful step. Keep them as counts per key per day, not as per-user records.
- When Growfinch's POST /v1/outcomes is available for your workspace (Growfinch tells you, and gives you a key with the scope outcomes:write), send one event per outcome within 7 days of the click: { type, event_id, occurred_at, attribution_key, value? }, batched hourly, idempotent on event_id; a reversal is a new event with reverses: <event_id>. Use validate first; the schema rejects unknown fields.
- Never send a user id, an email, a session cookie or an analytics key. Growfinch resolves the key to its own post; it keeps attributed sessions apart from assisted and confirmed conversions, and never counts a click as a conversion.
- Report the count of events per day for the first week, so the 7-day window can be checked against your own numbers.
If a pillar or a hook kind does not fit one of the listed values, ask rather than inventing a new one: the values are Growfinch's dimensions and are the same for every business.The labels and their values
Labels travel in posts[].meta of the campaign body. Keys are snake_case, values are short strings, numbers or booleans; an unknown key is refused, and a key that looks like it carries an answer fails validation (Growfinch never holds a business’s answers). Two of the four have fixed values, because Growfinch compares them across every business the same way.
| Key | Values | Why Growfinch asks |
|---|---|---|
content_pillar | your own words, one per pillar, used consistently | the mix you agreed on, and which pillar earns what |
topic_category | your own words, a few per subject | which subjects bring the audience you want, not only the largest |
hook_type | question · number_or_date · context · statement | whether a line of setting before the question earns more than the question alone |
cta_type | play · watch · read · visit · comment · none | which call to action earns replies, clicks or nothing |
creative_format, duration_seconds | your format name; a number | reel against image, short against long |
Without labels Growfinch still works: it derives the pillar from the campaign’s template class or name and the hook and call to action from the caption, and marks them derived on the Intelligence page. Labels are more reliable than inference, so the day they arrive they take over.
Attribution, end to end
A view on a platform is not a result for the business. The chain Growfinch keeps is source content → publishing variant → social post → UTM → website session → business outcome, and it only holds if the link carries a key that your website keeps. That is what utm_content does: one value per package and platform, never reused. Growfinch reads it from the link when the campaign arrives; your site stores it on the session; the outcomes you report carry it back, and Growfinch joins them to the post.
- Attributed session: a session that arrived with a Growfinch key.
- Assisted conversion: an outcome in a session that had the key among other sources.
- Confirmed conversion: an outcome your business counts as such, within 7 days of the click, reported by you.
A click is never counted as a conversion. Outcomes arrive through POST /v1/outcomes once it is enabled for your workspace; until then, start storing the key and counting the events, so there is history on the day it opens.
What never crosses over
Growfinch learns about a business only from what you configure in it and what you send through the contract. No user id, email, session cookie, answer or analytics key is ever sent to Growfinch; you check your own data and send the outcome with its key. Your learnings are yours: nothing crosses between businesses except the method.
What Growfinch does with it
Every Monday Growfinch’s Analyst compares like with like: one platform, one format and one hour at a time, one dimension against the rest, with at least five posts a side and the uncertainty shown. Where a gap holds, Scout files a recommendation for you in Approvals, one variable at a time, with the evidence. You accept, reject or ask it to investigate; nothing changes without your click. The Intelligence page shows what is working and what was learned. Results and reports explains the numbers themselves.