Developers

Standardized interfaces for attribution data ingestion and result retrieval

Designed for teams evaluating attribution workflows, event structures, reporting outputs, and secure integration pathways.

Contact Sales

Event Ingestion

Submit structured channel and campaign performance inputs into the attribution workflow.

Attribution Request

Trigger attribution processing based on selected models and reporting windows.

Result Retrieval

Retrieve normalized summaries and channel-level outputs for downstream reporting.

Webhook Notifications

Receive asynchronous status or result notifications for connected systems.

Request example

POST /api/attribution
{
  "channels": [
    { "name": "Google Ads", "spend": 12000, "clicks": 8400, "conversions": 176, "revenue": 52400 },
    { "name": "Meta Ads", "spend": 9000, "clicks": 11200, "conversions": 151, "revenue": 41800 }
  ],
  "model": "multi_touch",
  "date_range": "2026-01-01_to_2026-01-31"
}

Response example

{
  "summary": {
    "total_spend": 21000,
    "total_conversions": 327,
    "total_revenue": 94200,
    "overall_roas": 4.49
  },
  "channel_results": [
    { "name": "Google Ads", "attribution_weight": 0.54, "cac": 68.18, "roas": 4.37 },
    { "name": "Meta Ads", "attribution_weight": 0.46, "cac": 59.60, "roas": 4.64 }
  ]
}

Data notes

What evaluators need to know

Required fields: channel name, spend, clicks, conversions, revenue, and date range.

Optional fields may include campaign tags, region identifiers, or internal business references.

Users may compare last-click and multi-touch logic depending on reporting needs.

Outputs can include summary metrics, channel weights, efficiency indicators, and review-ready views.

Clear structure supports better internal discussion and executive review.

Security

Enterprise-aware integration posture

Managed API credentials and scoped permissions

Enterprise access governance for submitting and retrieving outputs

Awareness of sensitive data handling, minimization, and controlled access