HockeyStick Knowledge Base Knowledge Base Open Command Centre

Setting up Activate

Connect PartnerStack

What Activate pulls from PartnerStack, how it maps to leads, trials, activations and revenue, and the sync schedule.

Connect PartnerStack

PartnerStack is where Activate gets partner and outcome data. Once the client's keys are verified, Activate pulls from the PartnerStack API on a schedule. All partner metrics in Activate come from these pulls and are read-only. Nobody types them in.

What Activate pulls and how it maps

PartnerStack dataIn Activate
PartnershipsPartners in the registry. A PartnerStack partner whose name matches an existing partner (for example one Alex recommended) is adopted rather than duplicated.
CustomersEach partner-referred customer counts as a Lead and a Trial for that partner.
First approved transaction per customerOne Activation. Later transactions for the same customer never add a second.
TransactionsRevenue events (attributed revenue).
LinksPartner tracked links used by briefs.

PartnerStack attributed revenue is shown next to the client's own finance figures, never added to them. See Monthly revenue inputs.

Sync schedule

  • Delta pull: every 15 minutes.
  • Full reconcile: daily at 01:00 UTC. It repairs anything the deltas missed.
  • Authorisation health check: daily at 02:00 UTC. It re-tests the stored keys.
  • Daily metrics: run at 02:00 UTC, after the full reconcile.

Webhooks only prompt an earlier pull. They never write data themselves. Webhook health shows as its own pill: pending until traffic is verified, then healthy, and stale if no verified event arrives within the freshness window.

Running a full reconcile now

On the Products tab Integration access card, press Run full reconcile. Give a reason, between 3 and 500 characters. Repeat requests while one is running are merged into it. After a run there is a cooldown ("Retry after ..."). The card then shows the run's Requested, Operator, Started and Completed times, and any failure message. If a run fails, the button changes to Retry full reconcile.

A connection in Error keeps being retried on every pull, so a short provider outage clears on its own. Revoked or genuinely bad keys need Re-request keys.