Connect Push API to SiteOps

0 of 10 done

1. 1Open your project's settings in SiteOpsIn the SiteOps dashboard, open the project you want to send numbers to, then go to Settings and find the Push API row in the connections list. Everything in this guide happens from that row — there is no external website to visit.Each project has its own key. If you run several projects, repeat this guide once per project.
   1. Settings
   2. Push API
2. 2Generate your push keyPress Generate key. SiteOps creates a key that starts with sk_push_ and shows it once. Copy it somewhere safe — a password manager is ideal. This key belongs to this project only and is the entire setup: whoever holds it can write numbers into this project's charts.Treat it like a password. Do not paste it into client-side code or a public repository — it should live on a server or inside your scheduler's credentials store.

   Push keysk_push_····3f9a

3. 3Copy the ready-made test requestNext to the key, SiteOps shows a curl line with your key and a sample payload already filled in. The shape is simple: one POST request, your key in the Authorization header, and a small piece of JSON naming the metric, the value and the date — for example a metric called revenue, a value of 120.50, and today's date.You do not need to memorise the format. The copy button gives you a working request — change the numbers later, keep the shape.

   metricvalue

4. 4Send the first pingPaste the curl line into a terminal — on your server or your own machine — and run it. A successful response comes back in under a second. The moment it lands, the Push API row in Settings flips to Connected on its own, and the sample value appears on the Revenue card.If the command errors, check the two usual suspects first: the key was pasted with a missing character, or the quotes got mangled when copying. Copy the whole line again in one go.
5. 5Decide what you will push and how oftenPick the metrics that matter and the rhythm. Most teams push once a day: yesterday's revenue, yesterday's signups. You can push several metrics in the same request or send one request per metric — both are fine. Daily is plenty for dashboards and auto-rules; push more often only if you act on the numbers more often.Start with one metric. It is easier to add a second next week than to untangle five half-maintained ones.
6. 6Make the push repeatable and safe to retryEach push carries the date it belongs to, so sending the same day twice simply overwrites that day with the latest value — it never double-counts. That makes retries safe: if your job is unsure whether a push went through, run it again. Always send the value for a specific date rather than a running total.This is the property engineers call idempotency. In plain words: repeating a push is harmless, so build your job to retry on failure without fear.
7. 7Schedule itTurn the working request into a daily job. On a server, add a cron entry that runs the curl line each morning. In n8n or Make, create a scheduled workflow with an HTTP request step and paste in the same URL, header and JSON. In Zapier, use Schedule as the trigger and Webhooks as the action. Store the key in the tool's credential or environment settings, not in the visible request body.Point the job at yesterday's date, not today's — yesterday is complete, today is still moving.
8. 8Check the chart and set your time windowAfter the first scheduled run, open the project dashboard and confirm the metric shows the pushed value on the right day. Dates are taken as calendar days, so make sure the job and your bookkeeping agree on a timezone — pushing at 1 am can otherwise land a value on the wrong day.If a day looks wrong, just push the correct value for that date again. The overwrite fixes it.
9. 9Put the numbers to work in auto-rulesThis is the payoff. In Settings you can define base auto-rules — templates like: if revenue for the last 3 days is below 100, lower the budget. Base rules are only a template; nothing turns on by itself. To make one act, open a specific campaign in its ad cabinet and enable the rule on that campaign directly. From then on, the numbers your own server pushes steer real ad budgets.Every metric name you have ever pushed appears in the rule builder's metric list — the rule engine does not care whether a number came from Google or from your cron job.
10. 10Know how to rotate the keyIf a key leaks or a contractor leaves, press Regenerate in the Push API row. The old key stops working immediately and a new one is shown. Update the key everywhere a job still sends with it — cron, n8n, Zapier — and the pushes resume without losing history.Regenerate first, update jobs second. A short gap in pushes is fine; a leaked key writing junk into your charts is not.
    1. Settings
    2. Push API