Skip to main content
images/google.svg

Getting Started

Track Google Ads conversion events directly from Morf workflows. Before you begin, you’ll need to grant Morf access to your Google Ads account.

In Google Ads

  1. Go to your Google Ads account dashboard — not the manager account.
  2. Navigate to Admin > Access and Security and click + to add a new user.
  1. Fill in the following:
    • Email: morf-google-ads@morf-prod-5f7d.iam.gserviceaccount.com
    • Access Expires: Never
    • Account access level: Standard

Conversion Action Setup

When using the conversion API to send conversions to Google Ads, you will need to create new import conversion actions.
  1. In your Google Ads account go to Tools > Conversions.
  2. Click + New Conversion Action to create a new conversion action.
  3. Select Import.
  4. Select Other data sources or CRMs and Track conversions from clicks, then click Continue.
  5. Configure your conversion action within Google Ads. This configuration is the same as any other action in Google Ads.
  6. Update the Count setting to only count conversion actions once. This allows you to replay events if there are any issues without double counting conversions.
  7. Get the Conversion Action ID for this new action from the ctId param in the URL.
    • Example: if the URL is https://ads.google.com/aw/conversions/detail?ocid=00000000&ctId=576882000, your Conversion Action ID is 576882000.

In the Morf Dashboard

  1. Navigate to Integrations and add a new integration.
  2. Select Google Ads.
  3. Enter your Google Ads account ID (found in the top-right of your Google Ads dashboard, e.g. 123-456-7891) — not the manager account ID.
You can now use the Send Conversion Event action in your workflows.

FAQ and Testing

Customer ID is an account-level ID that is the same for all conversion actions in your Google Ads account.Conversion Action ID is unique to each conversion action and is configured per mapping. It can only be found in the browser URL of your given conversion action under the ctId parameter. For example, if the URL is https://ads.google.com/aw/conversions/detail?ocid=00000000&ctId=576882000, your Conversion Action ID is 576882000.
To debug and validate that events are going through, look at the metric all conv. (at conv. time) — this shows the number of events coming through. It can take up to 24 hours for events to appear in the Google dashboard.
Events sent to Google require a GCLID, an email, or a phone_number. If one of those identifiers is not being sent, you may see this error. Double-check that at least one of those fields is being passed on each payload.

Parameters

Parameters

Result Object Field Details

You can use the result of the action’s data as inputs to downstream workflow actions. Each fetch action requires an object name, which nests the action’s result data inside the downstream data context in the workflow. See Passing Data Between Actions for how to set it and reference the result from downstream nodes. Here we demonstrate how to refer to this data using the prefix $result_object_key.
Fetch Action Response Object