Google Ads multi-source conversions

Use the Data Manager API to send multi-source conversions an additional data source for your tag conversions to maximize ad interaction signals and strengthen your data and overall performance.

Send online conversions

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: Retrieve asynchronous processing diagnostics and verify ingestion status with requestStatus.retrieve.

Conversion adjustments

To adjust a previously recorded conversion, send an event with the same transactionId as the original event. For details, see Conversion adjustments.

  • Adjust real-time conversion values: Send accurate financial updates (like restatements, upsells, or finalized cart totals) from your CRM to override the initial estimated value.
  • Enhance measurement accuracy: Supplement your conversions with missing user-provided data (like email or phone number) to mitigate signal loss, recover conversions that may be missed by the Google tag, and unlock better bidding.

Next
Send events