Product
Build on the same measurement your team uses.
Read DATALYR marketing, attribution and revenue data through the HTTP API. Build internal workflows with explicit workspace access and metric definitions. Connect code to reporting without maintaining a parallel interpretation of the numbers.
Compare plans and usage
Custom workflows still need consistent definitions.
A spreadsheet export or internal tool can drift from the application when it quietly uses different dates, currencies or attribution rules. The DATALYR API exposes supported workspace data and governed query capabilities so an integration can preserve those definitions. Authentication, scopes, pagination and unavailable responses are part of the implementation, not afterthoughts.
In DATALYR
Marketing analytics API
Query a defined metric
Use the metric catalog and supported dimensions to construct a bounded question. Keep the returned context with the data so later consumers understand what was measured.
Use scoped access
Give an integration the permissions it needs. Reading an attribution report and changing a conversion rule are different operations and should be treated accordingly.
Handle incomplete results honestly
Inspect pagination, freshness and unavailable reasons. A failed upstream source must not become a zero-valued row in a business dashboard.
The workflow
From setup to a useful answer.
Choose the endpoint contract
Identify whether you need a report, raw events or a governed query. Read the current endpoint reference and decide how much data the integration actually requires.
Implement a bounded request
Use the correct authentication and date conventions. Add handling for limits, pagination and explicit errors before scheduling the workflow for regular use.
Reconcile a known result
Compare the response with a matching application report. Align filters and attribution settings, then document any intentional differences before relying on the integration.
Verify the result
Know what good looks like.
- Credentials are stored securely with appropriate permissions.
- Pagination and unavailable responses are handled explicitly.
- A known query reconciles with the same application definition.
Go deeper
Use the guide for context, then follow the implementation reference for your setup.
A few practical questions.
Can API credentials change settings?
Only supported operations with the necessary permission scopes can write. Review the endpoint contract and use a dry run where supported before applying a configuration change.
Can I build an AI workflow with the API?
Yes, or use the hosted MCP connection when your client supports it. Keep the same access controls and require the workflow to expose the basis of reported numbers.
Explore related workflows.
- Marketing analytics MCP server ↗
Connect a compatible AI client to DATALYR through MCP to investigate marketing performance, run supported reports and work with scoped tools.
- Marketing reporting dashboards ↗
Build saved reports, dashboards and analyses in DATALYR so your team can review marketing and revenue performance with a consistent measurement basis.
- Conversion tracking health monitoring ↗
Investigate tracking, identity and conversion delivery health in DATALYR when marketing data changes unexpectedly.