← Blog

Integrating Adjust: Verify Meta, Google, Apple and X Ads

An Adjust integration is ready for campaign decisions when the app sends the intended events, the relevant networks receive them, and cost and revenue reports reconcile at the required level. Install and test the SDK first, configure each partner, then validate these connections separately. Apple Ads attribution and cost reporting use different paths; Google requires conversion actions as well as a Link ID. Matching attribution windows helps comparisons but does not make every network's figures identical.

A purchase can appear in Adjust while its value never reaches the network bidding for that customer. A campaign can have attributed installs while its cost feed is disconnected. Treat attribution, event sharing and cost collection as separate parts of the implementation.

This guide uses Adjust’s official documentation checked on October 9, 2026. It covers the handoff between your app developer, acquisition team and reporting owner. If you are still selecting a mobile measurement partner (MMP), start with our Adjust and AppsFlyer comparison.

Prepare the app and the event definitions

Follow Adjust’s getting-started guide for the software development kit (SDK) appropriate to your app. Confirm the app IDs, production and sandbox settings, consent handling and permissions for each account. You can configure and test app events before buying traffic. A network attribution test may need a qualifying ad engagement, so record that as a separate launch test.

Give the developer an event specification that goes beyond names such as purchase. For each event, write down its trigger, value, currency, unique transaction identifier and whether the app, server or subscription system sends it. A subscription renewal sent by both the app and server can double reported revenue unless you have explicitly handled duplication.

Keep purchase revenue, ad revenue and proceeds after store fees distinct. Decide how refunds and renewals enter the report. If you are migrating from another MMP, plan existing-user handling before the release so existing customers do not become apparent new acquisitions.

Meta: connect the data source on both sides

In Campaign Lab > Partners, add the partner listed as Facebook, choose the app and enter the Meta developer App ID. New apps, new Adjust accounts and migrations must also select Adjust as a data source in Meta Events Manager. Adjust’s Meta setup documentation says Meta cannot claim engagements without that connection.

Map the events you intend to share to appropriate Meta events and check the revenue-sharing setting. A purchase event count and a purchase value are different signals. Inspect the sharing scope, including whether other-network and organic events are sent, against the app’s consent and data-sharing design.

For Android raw attribution data, review the Google Play and Meta install-referrer requirements. The Meta referrer path needs Adjust Android SDK v5, the Meta install-referrer plugin and decryption-key setup. A key alone does not establish that every Android install will have campaign-level raw data.

Create the Link ID for the correct app and platform at the appropriate Google Ads account level. Add it in Campaign Lab’s Google Ads setup. The account guide explains single-account and manager-account arrangements, which matter when several accounts advertise the same app.

Then verify the conversion actions in Google Ads. Adjust’s integration guide requires first_open and session_start, plus the mapped events you need. It distinguishes automatic imports for events created after December 3, 2025 from older actions that need manual import. Trigger the events and check the resulting actions instead of assuming that the Link ID completes setup.

For purchase-value reporting, check both event mapping and the in-app revenue option. Connect cost collection separately in DataWorks > Connections. Also inspect the Google Ads 30-day attribution-window option: it can override lower-level settings. Any iOS on-device or probabilistic measurement needs its own current prerequisites; adding a click parameter does not guarantee complete or privacy-compliant attribution.

Apple Ads: separate attribution from campaign enrichment

The Apple Ads attribution flow starts with the Adjust SDK and Apple’s AdServices framework. The app obtains a token; Adjust uses it to request Apple’s attribution response. This is not the same connection as the Apple Ads reporting API.

Link Apple Ads in DataWorks > Connections for campaign names and the reporting services you need, following the Apple Ads setup guide. If attribution has IDs but no names, examine that reporting connection. If costs are missing, check its permissions, selected service and latest successful import before changing event code.

Apple Ads does not use the same partner-event mapping flow as Meta. Evaluate its acquisition reports alongside store conversion work. Our Kleo case study reports a 127% download increase over 30 days of App Store optimization; that separate result does not validate an Adjust configuration or establish Apple Ads’ incremental contribution.

X Ads: check account selection and migration constraints

Adjust’s X setup guide still uses Twitter in parts of the interface. Add the partner in Campaign Lab, complete the account connection in DataWorks, select the intended ad accounts, and map the required events and revenue settings.

X supports only one MMP connection at a time. An old integration can explain a failed migration. Plan the change with the account owner and confirm which system will supply events. The account connection, selected accounts, event sharing and attribution settings each need a recorded test result.

Prove the integration before relying on its reports

Use a small test record that the developer and marketer can both follow. For a hypothetical US$4.99 test purchase, document the app build, test device, event time, transaction identifier and expected currency. Follow it from the app or server into Adjust and, where supported, the destination network. Keep test revenue out of business reporting.

ObservationCheck next
No event in AdjustApp/environment IDs, trigger, SDK or server request, and consent handling
Event in Adjust, absent at partnerPartner activation, event mapping, sharing scope and receiving platform diagnostics
Purchase count present, value missingRevenue-sharing option, amount and currency fields
Revenue appears twiceDuplicate senders, retries and transaction deduplication
Installs present, cost absentSeparate cost connection, account permissions and import freshness

These are diagnostic starting points, not proof of the cause. Use the platform’s test tools and logs to distinguish a configuration failure from a privacy restriction or delayed report. Adjust’s Google guide requires a live campaign attribution check and allows time for data to arrive; an SDK sandbox event alone cannot prove that connection.

On iOS, map your chosen business events in Conversion Hub using the SKAN documentation. SKAdNetwork (SKAN) returns delayed, limited attribution information. Record the schema version and the SDK responsible for updating values. Reconcile SKAN and other attribution views before combining them, since they can describe overlapping acquisitions.

Keep three different clocks visible

An attribution lookback window decides which earlier ad engagement is eligible for credit. Reporting delay describes when a result reaches the dashboard. Cohort age measures time since installation, which determines how much revenue users have had time to generate. A seven-day click window does not make a seven-day-old cohort a mature day-30 result.

Before comparing channels, record install dates, report cutoff, time zone, click and impression windows, re-engagement rules, currency and revenue basis. Compare cohorts at the same age. Mark incomplete days as provisional and retain the export used for each decision.

Changing a window can redistribute credited installs and revenue without changing customer purchases. The direction of a channel’s reported return depends on which events move. An attribution report helps allocate credit under a set of rules; proving incremental sales requires a suitable experiment.

What the implementation handoff should contain

Hand over the event specification, partner mappings, sharing settings, cost-connection status, test receipts and known reporting limitations. Assign an owner to review them after SDK releases or partner changes. Estimate the schedule from those tasks and the app’s release process, rather than promising a fixed number of hours per network.

Our Adjust implementation overview describes event mapping and campaign handoff. For reconciliation between attribution, revenue and store records, see mobile data and attribution. If the measurement is already sound and the next task is running acquisition, our paid advertising service covers that work.

Growing an app? We do this all day.

One client added 242,279 installs in 16 weeks. Another's ASO overhaul lifted downloads more than 900%. Store listing, paid UA, and retention, run as one loop.

Teegan Johnson, Founder & Chief Growth Officer, will follow up by email about your request. Unsubscribe anytime. Privacy

Prefer to talk first? Book a 30-minute call instead.

See mobile app marketing →

Add us as a preferred source on Google

A free Google setting to see more of our relevant articles in your own search experience. You can change it any time.