Integrations

What connects to Eondash today, what each connection is for, and how a new one gets set up.

Tracking side

These are the sources of your own record: the clicks you sent and the conversions you were told about. Each connection syncs on a schedule, and every conversion keeps the click ID it came from.

Eondash trackerTracking links on your own domains, with smartlink routing and sub IDs 1 to 10.
KeitaroRead clicks and conversions from your Keitaro install, so your buyers keep the tracker they know.
AffiseRead clicks and conversions with a network API key.
ScaleoRead clicks and conversions with a network API key.
AlanbaseRead clicks and conversions with a network API key.
Advertiser postbacks (S2S)Advertisers call your postback URL with the click ID, the event and the payout. Leads, sales and rejections are all supported.

Which setup fits you

A network on its own domains: Use the Eondash tracker. Advertisers post back to Eondash, affiliates get their links and postbacks from the portal, and nothing else has to run alongside it.
A network already on Affise, Scaleo or Alanbase: Keep it. Eondash reads clicks and conversions with a network API key and adds reconciliation, fraud screening and affiliate invoices on top.
A media buying team on Keitaro: Keep your tracker and your campaigns. Eondash reads them in, so performance, buyer management and reconciliation sit next to the numbers your buyers already use.

Each sync brings in clicks with their click ID and sub IDs, conversions with their event, payout and status, and the offer and affiliate names that make reports readable. Nothing has to be re-entered by hand.

Advertiser data

Reconciliation compares your tracking with each advertiser's own record of the same conversions: what they approved, rejected and paid.

We connect that data during onboarding, from the advertiser's or network's platform. If it runs on a platform we don't connect yet, we scope a custom integration with you before you commit.

How reconciliation uses it

S2S postback macros

Outbound postbacks to your affiliates use templates with macros, so each affiliate gets the fields their tracker expects. Set them once globally, per affiliate, or in bulk.

{clickid}
{payout}
{revenue}
{status}
{sub_id_1} … {sub_id_10}
{country}
{devicetype}
{transactionid}
{timestamp}

How a connection gets set up

You share access: an API key for your tracker, or the postback URL your advertisers should call.
We map offers, affiliates and statuses, and set the sync schedule for your plan.
We fire test conversions end to end with the link tester and check each step.
Data flows on schedule, and reconciliation runs on every sync.

API, MCP and exports

A REST API documented with OpenAPI, with separate keys for your organisation and for partners. An MCP server lets AI assistants read reports and run supported tasks, and reports export to CSV and XLSX.

Custom integration

Work with a platform that isn't listed here, or need data in or out in a specific shape? Tell us what you run and we'll scope it with you.

Bring your stack to the demo

Tell us which tracker and advertiser platforms you run. We'll show how they connect.

Request demo

or write to demo@eondash.com