Operating
Onboarding a partner
A partner is a platform that runs its own creator relationships and wants the measurement underneath. Their users never see Acrune: they see a link on their own product, on their own dashboard.
This is a different shape from a client whose campaigns we run. A marketplace opens campaigns continuously, enrols creators from its own signup flow, and collects post URLs through its own submission form — none of which can route through an operator without becoming the bottleneck.
What to set up
1. An account and a key.
create_account { name: "Their Platform", slug: "theirplatform" }
issue_api_key { slug: "theirplatform", name: "production", scopes: ["read","write"] }Shown once. Issue ["read"] if they are only reporting.
2. Nothing else. They open their own campaigns through
POST /v1/campaigns. Do not pre-create campaigns for them; a campaign we
opened has no externalId, so their own code cannot address it without storing
an id of ours.
What to tell them
Point them at the API reference. Four things are worth saying out loud, because they are the ones that go wrong on day one:
Pass your own ids. externalId on a campaign makes creation idempotent and
lets every later call name that campaign by an id they already have. Without
it they store ours, and a retry opens a duplicate.
One enrolment is one link, keyed on externalId alone. If their creators
connect several social accounts and each should be counted separately, the
externalId must be the social account id, not the user id. Passing the
user id means the second enrolment finds the first creator and returns the
first link, and nothing reports an error. This is the single most likely thing
to be got wrong.
Attach the post. Enrolment gives a link; attaching tells us which post it went in. It is a separate call because it happens at a different moment, and the ranking depends on it.
Clicks are not a rate. Whatever they render, it is not click-through. There is no impression behind these numbers.
What they will ask for that does not exist
Be straight about this rather than letting them find out in integration:
Conversions and revenue. Not served. The click id is planted on every redirect so it can be added later without losing history, but there is no endpoint today.
Webhooks. Stats are pulled, not pushed. There is no delivery system.
A sandbox. Keys carry a live/test flag with no isolation behind it, so test keys are not issued. They should build against a campaign of their own pointed at a URL they control.
Checking on them afterwards
campaign_performance on their slug shows whether links are being issued and
clicked. list_missing_posts shows whether they are actually attaching post
URLs — a partner with many links and no post URLs has integrated half of it,
and the half they skipped is the one that produces the ranking.
read_audit_log with their key id as actor shows what their integration has
been doing.