Uploading Google Conversions using Make.com

Beginner Questions
,
1

:bullseye: What is your goal?

I want to upload a “Qualified Lead” conversion from ActiveCampaign to a Google Ads Campaign.

:thinking: What is the problem?

I am storing all the relevant data in AC - such as GCLID & time etc. In Make, I see the “Google Ads Conversions” but when I try to use it, I only have the option for a “Upload a Google Call Conversion” or “Upload a Conversion Adjustment” ? Should I be using “Make an API Call”?

3

Yes, Make an API Call is the right module here. The two ready made modules cover call conversions and conversion adjustments only, neither of them uploads a click conversion, so there is no way to get a gclid based lead conversion out of them.

The method you want is uploadClickConversions on the customer resource, so a POST to a path of the shape customers/CUSTOMER_ID:uploadClickConversions on a current API version, with the customer id written without dashes.

The payload is a conversions array. Each entry carries gclid, conversionAction as a resource name of the shape customers/CUSTOMER_ID/conversionActions/ACTION_ID, conversionDateTime, and optionally conversionValue and currencyCode. Next to the conversions array, set partialFailure to true.

Four things decide whether this works, and they are worth checking before you wire ActiveCampaign into it.

  1. The conversion action has to be an import action, created in Google Ads under Goals, Conversions, new conversion action, Import, other data sources, track conversions from clicks. A conversion action that was created by the website tag will not accept a gclid upload.
    1. conversionDateTime needs a time zone offset, in the shape yyyy-mm-dd hh:mm:ss followed by the offset, for example 2026-09-23 14:05:00+02:00. This is the most common reason such uploads are rejected. Build it with formatDate from your ActiveCampaign timestamp, run the scenario once and read the actual value in the history before you look at anything else.
      1. partialFailure true also changes how errors reach you. Row level problems then come back inside a successful response, in a partialFailureError field, instead of as an HTTP error. A green module in Make therefore does not prove that the conversion was accepted. Open the module output in the scenario history and read that field, it names the row and the reason.
        1. The conversion action id is not the name you see in the interface. You can read it with a search call against the conversion_action resource through the same API, or take the numeric id out of the address bar when you open the action in Google Ads.
        2. One more thing on the path. Google retires old API versions on a schedule, and a retired version answers with a 404 that looks like a wrong path rather than a version problem, so keep it current.
        3. If the Make an API Call module of the Google Ads Conversions app does not let you reach that method, the fallback is the generic HTTP module with an OAuth 2.0 connection, where you set the developer token header yourself, plus the login customer id header if you work through a manager account.