Developer tools integration
Planned integrationCustom Integrations integration
Plan a custom reporting integration for business tools that do not yet have a dedicated adslink.io connector.
See the reporting experience
Custom Integrations dashboard preview
A proposed layout to illustrate reporting possibilities. This integration is not available to connect yet.
- Source
- Your platform Sample
- Fields
- 4 proposed Sample
- Currency
- Explicit Sample
- Status
- Planned Sample
Proposed field mapping
{ "source": "sample", "currency": "AED",
"fields": ["campaign", "spend", "clicks"] }Define the scope
- Source owner
- Required
- Metric definitions
- Required
- Access approval
- Required
Example reporting fields
| Source field | Report field | Definition |
|---|---|---|
| campaign_name | Campaign | Source campaign label |
| cost | Spend | One currency |
| click_count | Clicks | Source-defined clicks |
Custom Integrations reporting in your workspace
A custom integration is useful when your reporting source has a workflow or data model that an existing connector does not cover. Start with the business question and the source records required to answer it. Arbitrary data imports and a self-service connector builder are not currently available in adslink.io.
Reporting scope to plan
- A source-specific reporting scope and a clear list of required fields.
- Explicit account ownership, permission boundaries and reporting identifiers.
- A proposed update schedule with currency, timezone and metric definitions.
Before you begin
- The source platform name and the reporting problem you need to solve.
- A non-sensitive description of available exports or API documentation.
- An authorized owner who can review a future connection’s access requirements.
How to prepare for Custom Integrations
Check existing integrations
Review the directory first; the reporting API may already support reading the saved advertising data your system needs.
Describe the source records
List the entities, example field names and reporting dates needed. Use synthetic examples rather than private customer records.
Define the reporting rules
Specify how identifiers, currencies, timezones, refunds and duplicate records should be handled.
Request a connector review
Send the platform and reporting requirements to the team. A reviewed implementation and its own authorization flow would be needed before a new source can connect.
Availability and reporting limits
A request is not an active connection or a delivery commitment. Do not send API secrets with a feature request. Existing provider connections keep their own access controls.
No connection is created by visiting this page or requesting an integration.
Custom Integrations integration FAQs
Can I upload any JSON or CSV as a new data source?
There is no general-purpose source importer on this page. Describe the workflow so the team can assess an appropriate connector.
Can my POS read existing reports instead?
The private reporting API can expose permitted saved reporting data to an authorized POS client. That is a separate, already available read-only capability.