Google Ads offline conversions

Use the Data Manager API to send event data for Google Ads offline conversions or enhanced conversions for leads.

Send offline conversions

If you're upgrading from the Google Ads API, see Upgrade from the Google Ads API.

Workflow overview

To send event data with the Data Manager API, complete the following steps:

1. Prepare destinations: Define the Destination objects for the destinations field of the ingestion request to specify the target account and conversion or event destination. See Prepare destinations for details.

2. Prepare event data and identifiers: Populate Event fields with event details and required identifiers (such as ad click, client, or app instance identifiers). If you include user contact information in userData, normalize and SHA-256 hash the identifiers according to the formatting guidelines, and optionally encrypt them. See Prepare event data for details.

3. Build and send the ingestion request: Submit an events.ingest request containing your destinations, Event records, and encryptionInfo if you encrypted userData. Use validateOnly: true to test your payload for fast-fail errors before sending production data. See Send events for field requirements and code samples.

4. Check diagnostics and adjust conversions: Retrieve asynchronous processing diagnostics with requestStatus.retrieve, and adjust or retract previously recorded conversions as needed.