Ellipse Gradient for Header

Adjust Integration Guide

Integrate Adjust with enterprise systems through REST APIs, selected callbacks, reporting services, and raw-data exports.

Adjust integration options at a glance

Adjust provides REST APIs for reporting, tracking, application and campaign-related operations, with endpoint availability determined by the product and account permissions. It also supports selected callback scenarios for attribution, sessions, reattribution, in-app events, ad revenue, and fraud-related data. Reporting and export services can support scheduled or batch extraction, while raw-data exports may deliver JSON, CSV, or other configured formats through callbacks or accessible destinations. Adjust uses token-based authentication, including API tokens and separate app or event tokens for some tracking scenarios. Martini can consume these APIs, receive callback requests, schedule incremental reports, transform data, and route normalized results to enterprise systems.

Integration pointSupported by Adjust?Common use casesHow Martini supports it
REST APIsYesRetrieve reports, campaign and attribution data, perform supported tracking operations, and administer selected Adjust resources.Martini can consume Adjust REST endpoints from workflows, manage authentication through secrets, transform responses, and route results to downstream applications.
Webhooks / outbound callbacksLimitedReceive selected attribution, reattribution, session, in-app event, ad revenue, fraud, and related raw-data notifications.Martini can expose a controlled API endpoint or consume webhook-style requests through a workflow start trigger, then validate, deduplicate, and route payloads.
Bulk / async / batch APIsLimitedRetrieve aggregated reports over date ranges and dimensions, including large result sets or report-generation flows where supported by the selected service.Martini can schedule partitioned extractions, manage pagination or asynchronous completion, maintain watermarks, and reconcile overlapping windows.
File / raw-data exportsLimitedReceive selected raw-data datasets through callbacks or configured export destinations, subject to the Adjust product, plan, format, and retention settings.Martini can process supported JSON, CSV, or other accessible payloads and load validated data into databases, warehouses, or applications.
AuthenticationYesAuthenticate management and reporting requests with API tokens, while app and event tokens may identify tracking requests.Martini stores API tokens, app tokens, event tokens, callback credentials, and downstream credentials as environment-managed secrets.
SDKs and mobile trackingYesInstrument mobile applications to send installs, sessions, in-app events, and attribution-related signals to Adjust.Martini does not replace Adjust mobile SDK instrumentation; it consumes the resulting APIs, callbacks, reports, or exports for enterprise orchestration.
GraphQL APIsNot confirmedNo official Adjust GraphQL API was confirmed in the supplied research.Martini can consume GraphQL APIs generally, but Adjust integration planning should use the documented REST APIs and callbacks unless another interface is separately confirmed.
SOAP APIsNoNo official Adjust SOAP API was confirmed.Martini should use Adjust REST APIs, callbacks, or exports rather than assuming a SOAP interface.

How Adjust exposes data and business events

Adjust REST APIs

Adjust provides REST-based services for reporting, tracking, app and campaign-related administration, and data retrieval. Endpoint availability, parameters, permissions, and report behavior depend on the selected Adjust product and account configuration.

Martini implementation pattern

Martini implementation pattern: a workflow authenticates with an environment-managed Adjust token, calls the required REST endpoint, handles pagination or report-generation behavior, validates the response, maps Adjust objects into a canonical model, and writes the result to an enterprise target.

Implementation sequence

Authenticate with the required Adjust API token
Request the selected report or resource for a bounded date range
Process pagination or asynchronous report completion where applicable
Validate the response and preserve Adjust identifiers
Map dimensions, metrics, timestamps, and currencies to the target model
Write or upsert the transformed data and record extraction status

Adjust callbacks

Adjust supports callback-style delivery for selected attribution, reattribution, session, in-app event, ad revenue, fraud-related, and other configured data scenarios. These callbacks are not a universal stream for every Adjust object or state change.

Martini implementation pattern

Martini implementation pattern: expose a controlled API endpoint or webhook-triggered workflow, authenticate or validate the request where supported, persist the accepted payload, apply replay protection, and route normalized events to downstream applications or queues.

Implementation sequence

Receive the selected Adjust callback request
Validate callback credentials, structure, and required identifiers
Persist the payload or acceptance record before acknowledging it
Generate a deterministic idempotency key
Map event, attribution, revenue, and campaign fields
Apply routing and fraud or business rules before downstream delivery

Adjust raw-data exports

Adjust supports raw-data export and data-delivery options for selected datasets. Exact formats, destinations, schedules, retention, and availability depend on the configured product and customer plan.

Martini implementation pattern

Martini implementation pattern: retrieve or receive the configured export, parse the supported format, validate schema and reporting context, transform rows into warehouse or application models, and reconcile counts and totals before marking the batch complete.

Implementation sequence

Receive or retrieve the configured raw-data export
Identify the app, dataset, reporting period, and export batch
Parse the supported JSON, CSV, or other configured format
Validate required fields and reject malformed rows safely
Transform records into warehouse or application tables
Reconcile row counts and metrics before completing the batch

Common Adjust integration patterns

Pattern 1: Sync Adjust attribution to Salesforce

When to use this pattern

Use this pattern when marketing and sales teams need mobile acquisition, attribution, and conversion context alongside leads, contacts, campaigns, or custom Salesforce objects. A scheduled report workflow can retrieve Adjust data over an overlap window and account for delayed attribution changes.

Integration direction
Adjust
Martini
Salesforce
Example Mapping
Adjust FieldCanonical FieldTarget Field
app_tokenapplicationIdAdjust_App_Token__c
tracker_namemarketingSourceMarketing_Source__c
campaign_namecampaignNameCampaign_Name__c
attribution_timestampattributedAtAttributed_At__c
Martini implementation pattern

Martini schedules an Adjust reporting workflow, partitions the extraction by app and date window, maps tracker and campaign dimensions to Salesforce fields, and upserts records using stable external identifiers. The workflow applies validation, retries transient failures, and sends invalid or unreconcilable rows to an operational review path.

Martini capabilities used
  • workflows
  • API consumption
  • scheduling
  • data mapping
  • business rules
  • error handling

Pattern 2: Process Adjust in-app events for finance

When to use this pattern

Use this pattern when mobile purchases, subscriptions, refunds, or attributed revenue must be reconciled with a finance or billing process. Selected Adjust callbacks or report data can be normalized before downstream posting.

Integration direction
Adjust
Martini
Finance or billing application
Example Mapping
Adjust FieldCanonical FieldTarget Field
event_nameconversionTypeTransaction_Type
revenueamountAmount
currencycurrencyCodeCurrency
event_timestampoccurredAtTransaction_Date
Martini implementation pattern

Martini receives a supported Adjust event callback or retrieves event data through reporting APIs, validates event names and financial fields, normalizes currency and timestamps, and sends approved transactions downstream. Deterministic keys prevent duplicate postings, while retry policies distinguish temporary target failures from invalid financial data.

Martini capabilities used
  • API consumption
  • workflow triggers
  • data mapping
  • validation
  • business rules
  • idempotency
  • error handling

Pattern 3: Load Adjust campaign and spend data into a warehouse

When to use this pattern

Use this pattern to combine Adjust campaign, adgroup, creative, install, event, revenue, and spend metrics with product and customer data in BigQuery, Snowflake, Amazon Redshift, or another supported database.

Integration direction
Adjust
Martini
Data warehouse
Example Mapping
Adjust FieldCanonical FieldTarget Field
campaign_namecampaignNamecampaign_name
adgroup_nameadGroupNameadgroup_name
installsinstallCountinstalls
reporting_datereportDatereporting_date
Martini implementation pattern

A scheduler-triggered Martini workflow calls Adjust reporting endpoints for daily or hourly windows, handles pagination or asynchronous report completion, and maps configurable dimensions into warehouse tables. An overlap window and deterministic dimension key support late-arriving changes, while reconciliation totals and batch status make failures visible.

Martini capabilities used
  • scheduling
  • API consumption
  • workflows
  • data mapping
  • SQL/database integration
  • monitoring
  • error handling

Pattern 4: Route Adjust callbacks to fraud and operational workflows

When to use this pattern

Use this pattern when selected attribution, event, session, reattribution, or fraud-related callbacks should trigger internal actions in systems such as Salesforce, ServiceNow, or a messaging destination.

Integration direction
Adjust
Martini
ServiceNow
Example Mapping
Adjust FieldCanonical FieldTarget Field
callback_typesignalTypeu_adjust_signal_type
app_tokenapplicationIdu_adjust_app_token
device_idsubjectIdentifieru_subject_identifier
fraud_reasonriskReasonu_risk_reason
Martini implementation pattern

Martini exposes a controlled endpoint for the configured Adjust callback, validates and persists the request, applies fraud or routing rules, and sends an operational case or message to the target system. Replay protection, correlation identifiers, and dead-letter handling support safe processing of delayed, duplicated, or malformed callbacks.

Martini capabilities used
  • API exposure
  • workflow triggers
  • validation
  • business rules
  • data mapping
  • idempotency
  • error handling

Applications commonly integrated with Adjust

Adjust data is commonly combined with marketing, analytics, advertising, and operational applications. Direct support and available fields depend on the customer’s Adjust plan and configuration; Martini can coordinate the confirmed APIs, callbacks, exports, and downstream interfaces in reusable workflows.

Application Scenario Direction Martini Pattern
Salesforce Associate mobile acquisition, app events, and attributed conversions with leads, contacts, campaigns, or custom marketing objects. Adjust → Martini → Salesforce Schedule Adjust report extraction or receive selected callbacks, normalize campaign and attribution identifiers, then upsert Salesforce records using deterministic external keys and retryable error handling.
BigQuery Combine Adjust attribution and event data with product analytics, revenue, and customer datasets for reporting and modeling. Adjust → Martini → BigQuery Run incremental Adjust report workflows, transform dimensions and metrics into warehouse tables, apply overlap-window deduplication, and load validated batches into BigQuery.
Snowflake Centralize mobile marketing performance, attribution, event, and revenue data for enterprise reporting and analysis. Adjust → Martini → Snowflake Retrieve date-partitioned Adjust reports or exports, map configurable campaign dimensions to a canonical model, and write staged data to Snowflake with reconciliation totals.
Amazon Redshift Store campaign, install, event, and revenue metrics for marketing and product analytics. Adjust → Martini → Amazon Redshift Use a scheduler-triggered workflow to call Adjust reporting services, paginate or partition results, normalize currencies and timestamps, and insert or upsert warehouse rows.
Google Ads Compare paid acquisition activity with Adjust attribution and conversion outcomes. Google Ads → Martini → Adjust Coordinate campaign identifiers and approved conversion data between advertising workflows and Adjust endpoints, with validation for app, event, attribution, and reporting dimensions.
Meta Ads Reconcile app-install and conversion performance with Adjust measurement data. Meta Ads → Martini → Adjust Use Martini workflows to normalize campaign and conversion data, apply account-specific business rules, and exchange approved data through the documented Adjust and advertising interfaces.
Tableau Present Adjust campaign, attribution, event, and revenue data in enterprise dashboards. Adjust → Martini → Tableau Extract Adjust data into a warehouse or reporting database, standardize metrics and reporting dates, and expose curated tables or APIs for Tableau consumption.

How to build a Adjust integration in Martini

Objective

Establish the Adjust API, callback, or export interface and keep all credentials outside workflow logic.

Instructions in Martini

  • Identify the required Adjust API, callback type, or export mechanism.
  • Store API tokens, app tokens, event tokens, callback credentials, and target credentials as environment-managed secrets.
  • Confirm account permissions, app configuration, and least-privilege access.

Objective

Select an event-driven or scheduled entry point that matches the Adjust data-delivery model.

Instructions in Martini

  • Use a callback or webhook-triggered workflow for selected real-time notifications.
  • Use a scheduler trigger for reporting and batch extraction.
  • Define date windows, overlap periods, and expected delivery behavior.

Objective

Obtain Adjust data reliably while accounting for pagination, report generation, callback retries, and large payloads.

Instructions in Martini

  • Call the required Adjust REST endpoint or accept the configured callback.
  • Handle pagination, asynchronous report completion, or export batches where applicable.
  • Persist correlation identifiers, extraction state, and callback acceptance status.

Objective

Convert Adjust-specific objects and metrics into a stable internal or target data model.

Instructions in Martini

  • Map Apps, Trackers, Campaigns, Events, Attributions, and Reports to canonical fields.
  • Normalize timestamps, reporting time zones, currencies, event names, and campaign dimensions.
  • Preserve source identifiers and raw payloads where reprocessing is operationally appropriate.

Objective

Apply validation, privacy, routing, deduplication, and business rules before writing downstream data.

Instructions in Martini

  • Validate required identifiers, metrics, callback signatures, and payload structure.
  • Minimize device-level and personal data according to retention and privacy requirements.
  • Use deterministic keys and overlap-window reconciliation to prevent duplicates.

Objective

Deliver validated Adjust data to applications, databases, warehouses, or internal APIs.

Instructions in Martini

  • Upsert Salesforce or operational records using stable external identifiers.
  • Load transformed batches into a supported database or warehouse.
  • Expose normalized data through a Martini API when multiple consumers need a consistent interface.

Common Adjust data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
AppsRepresent mobile applications configured in Adjust, including app tokens and platform-specific settings.Salesforce, data warehouses, advertising platforms, reporting databasesMartini preserves app identifiers, validates platform and account context, and maps app metadata into canonical marketing and analytics models.
TrackersIdentify attribution links, traffic sources, and campaign hierarchy.Salesforce, BigQuery, Snowflake, TableauMartini normalizes tracker identifiers and hierarchy fields, retains source lineage, and uses stable identifiers for reconciliation.
CampaignsDescribe marketing campaigns and source, campaign, adgroup, and creative dimensions.Salesforce, data warehouses, advertising platformsMartini maps configurable campaign dimensions, standardizes naming and dates, and applies business rules before downstream writes.
EventsRepresent in-app actions such as registrations, purchases, subscriptions, and other conversion events.Finance platforms, billing systems, warehouses, SalesforceMartini validates event names, timestamps, revenue, currencies, and attribution identifiers, then applies idempotent delivery rules.
AttributionsAssociate installs or reattributions with trackers and marketing sources.Salesforce, warehouses, analytics and reporting applicationsMartini preserves Adjust attribution identifiers, handles delayed or repeated updates, and upserts canonical attribution records.
ReportsProvide aggregated installs, events, revenue, spend, and campaign metrics over selected dimensions and periods.BigQuery, Snowflake, Amazon Redshift, TableauMartini schedules report extraction, partitions large requests, normalizes time zones and currencies, and reconciles totals before loading.

Authentication and security considerations

Token-based authentication

Adjust uses token-based authentication for API services. API tokens, app tokens, and event tokens may serve different purposes, so the required credential should be confirmed for each endpoint.

Secrets and least privilege

Martini should store Adjust tokens, callback credentials, and downstream credentials as environment-managed secrets. Use the narrowest account permissions and rotate credentials without changing workflow logic.

Callback and data protection

Validate callback requests using the security options available for the configured Adjust feature. Minimize device identifiers and personal data, and apply authorization and retention controls before exposing normalized data through a Martini API.

Operational considerations for Adjust integrations

Rate limits and report size

Confirm limits for each Adjust API and control concurrency. Partition large reports, process pagination or asynchronous generation, and avoid repeatedly extracting unchanged historical periods.

Incremental synchronization

Use reporting dates, event timestamps, or supported watermarks with an overlap window. Reconcile overlapping results by stable dimensions and identifiers because attribution and revenue data can change after the original event.

Idempotency and callbacks

Callback delivery may be delayed, duplicated, or out of order. Persist acceptance records, generate deterministic keys, and use idempotent upserts before acknowledging or routing a notification.

Schema, time, and currency controls

Adjust dimensions and metrics vary by endpoint and product. Version internal schemas, validate required fields, explicitly configure time zones, and normalize currencies before financial aggregation.

Monitoring and testing

Monitor API latency, throttling, extraction counts, callback acceptance, rejected records, retry volume, and reconciliation differences. Test representative callbacks, report windows, privacy controls, and downstream failure scenarios before production release.

Why use Martini instead of scripts or point-to-point integrations?

Orchestrate more than an API call

Scripts can retrieve Adjust data, but enterprise integrations also need scheduling, callback intake, validation, transformation, routing, retries, and operational visibility. Martini coordinates these concerns in maintainable workflows.

Separate source and target models

Martini can map Adjust’s campaign, attribution, event, and report structures into canonical models instead of embedding point-to-point field logic in every consumer.

Reuse integration assets

Reusable workflows and APIs can standardize authentication, pagination, deduplication, error handling, and downstream delivery across multiple Adjust applications and reporting processes.

Expose controlled data services

Where several internal applications need Adjust data, Martini can expose a normalized API façade with controlled access rather than requiring each consumer to implement Adjust-specific authentication and data rules.

Frequently asked questions

How can Adjust be integrated with enterprise systems?

Adjust can be integrated through its REST APIs, selected attribution and event callbacks, reporting services, and configured raw-data exports. Enterprise workflows can retrieve reports, receive notifications, transform Adjust data, and deliver it to applications, warehouses, databases, or internal APIs.

Can Martini integrate with Adjust?

Yes. Martini can consume Adjust REST APIs, receive supported Adjust callback-style notifications, process configured exports, and synchronize Apps, Campaigns, Events, Attributions, and Reports with enterprise systems through workflows and APIs.

Do I need a connector to integrate Adjust with Martini?

No. A dedicated Adjust connector is not required. Martini can use Adjust’s confirmed REST APIs, callbacks, exports, and token-based authentication through standards-based API consumption, workflow triggers, mappings, and reusable integration logic.

Is there any extra Lonti cost to integrate Adjust with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate Adjust. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Adjust, cloud infrastructure, warehouses, or other third-party systems depending on subscriptions, usage, and deployment choices.

Which Adjust integration methods should a new implementation use?

REST APIs are the primary method for reporting, tracking, and selected administration. Selected callbacks are appropriate for attribution, session, event, ad revenue, and fraud-related notifications. Raw-data exports and batch reporting can support larger or scheduled data movements. No official Adjust GraphQL or SOAP API was confirmed.

Does Adjust provide webhooks or event callbacks?

Adjust supports callback-style delivery for selected attribution, install, reattribution, session, in-app event, ad revenue, fraud-related, and related data scenarios. This is not a universal webhook stream, so callback coverage, payloads, timing, and delivery behavior must be confirmed for the configured feature.

How does Martini synchronize Adjust data?

Martini can run scheduled workflows for bounded reporting windows or process selected callbacks as they arrive. It can handle pagination or report generation, use overlap windows for late-arriving attribution data, normalize time zones and currencies, and upsert downstream data using deterministic keys.

How does Martini handle Adjust mapping, errors, and duplicate data?

Martini maps Adjust objects and metrics into canonical target models, validates required fields, applies privacy and business rules, and separates retryable failures from invalid data. Stable Adjust identifiers and composite keys support idempotent processing, while workflow logs and operational review paths support troubleshooting.

Related Martini documentation

APIs

Workflows

Transformation

Security

Operations

Connect Adjust to your enterprise systems

Use Martini to build secure, observable Adjust integrations for reporting, callbacks, attribution data, and mobile event workflows.

EXPLORE MARTINI
BOOK A DEMO