Databox integration
Databox is on the map, not in the product yet.
SearchHandled KPIs pushed into the Databox dashboards your agency already runs for clients.
How it works
Databox connects with a push token per data source, authenticating with Basic auth against Databox's push endpoint at push.databox.com/data. Databox is explicitly built to accept custom third-party sources this way, and SearchHandled becomes one of them: our SEO metrics appear inside the client dashboards your agency already maintains, next to the ad, social, and email metrics living there.
In the loop, Databox is the measure step delivered in your client's format. Agencies do not need a new reporting surface for SEO results; the pipeline pushes clicks, publishes, and ranking movement into the boards clients already open, and the SearchHandled dashboard remains the place your team works, not the place clients have to visit.
Best forAgencies reporting through Databox who want SEO results flowing into existing client dashboards.
Setup, step by step
- Create a custom data source in Databox for SearchHandled and copy its push token.
- Paste the token into SearchHandled's Databox connector, one token per client data source.
- Choose the metrics to push: clicks, published pieces, indexed pages, and ranking movement.
- Send the test push and confirm the metrics appear in the Databox designer.
- Add the metrics to the client's board and set the sync schedule.
Best practices
One data source per client
A push token belongs to one data source, and giving each client their own keeps metrics cleanly separated. The connector labels each token by client so the mapping stays obvious.
Push the metrics the client's board needs
Databoards work best uncluttered. Pick the handful of SEO metrics each client actually reads, and let the SearchHandled dashboard hold the full depth for your own team.
Name metrics consistently across clients
Using the same metric keys for every client data source means one board template serves all your clients, and cloning a databoard for a new client becomes a two-minute task.
Treat push tokens like credentials
A token authorizes pushes into that data source. We store them encrypted, and if one leaks, regenerate it in Databox and update the connector; the swap takes a minute.
Known issues
What practitioners actually report, from official docs, issue trackers, and community forums.
The legacy push endpoint is deprecated
Databox's older push endpoint is deprecated, and integrations still built against it face breakage as it is retired.
How we handle itThe integration is built only against the current push endpoint at push.databox.com/data, so there is no legacy surface in our pipeline to migrate off.
developers.databox.com
Tokens are per data source, so agencies hold several
Each client's data source has its own push token, and an agency with many clients manages a matching set, where a mixed-up token would push one client's metrics into another's source.
How we handle itThe connector stores tokens labeled per client and validates each with a test push at setup, so a token pasted against the wrong client is caught before any real metrics flow.
developers.databox.com
Questions teams ask
- Can SearchHandled read our Databox dashboards?
No. Push tokens only authorize sending metrics into a data source. We push numbers in and cannot read boards, other sources, or anything else in your Databox account.
- How fresh are the pushed metrics?
The feed pushes on a daily schedule, which matches how the underlying SEO metrics move. The connector shows the last successful push per client so freshness is never a guess.
- What if we do not use Databox?
The Looker Studio connector and the Sheets export cover client reporting in other formats, and the Power BI integration serves companies reporting in Microsoft's stack.
Not connectable yet
Start with the plan, not the connector.
Build a Growth Map from your site to see the work itself. Approved pages can leave through the export or the webhook today, and telling us Databox matters moves it up the rollout.