Skip to main content
Connect Google Ads to send tracked conversions back to Google. First confirm that your campaign records incoming events in Metricanic.

Connect the right Google account

  1. Open Integrations. Click Add integration.
  2. Choose Google Ads.
  3. Sign in with a Google account that can access your conversion action.
  4. Approve the requested access.
  5. Return to Metricanic. Check that the connection is active.

Choose the conversion destination

  1. Click Configure postback on the active connection.
  2. Enter the destination details:
  1. Open the conversion action in Google Ads. Copy the numeric ctId from its URL into Offline conversion action ID.
  2. Click Generate postback URL. Copy the result.
The operating account must own the action. If you access it through a manager account, enter that manager in Login account ID. Generating the URL checks the settings. It does not send a real conversion.

Attach the route to an event

  1. Edit the Metricanic campaign. Open 2. Events.
  2. Select the event that should trigger the Google conversion action.
  3. Enable Outgoing postback. Paste the generated URL into Destination URL.
  4. Save the campaign.
For example, attach a Qualified lead action to the approval event. Leave it off for submissions if Google should receive only approved leads. You can also save the generated URL as the traffic source’s postback. Use source postback copies that URL into an event. Update existing events if you change the source URL.

Preserve the original ad identifier

Use the Google Ads traffic source template to capture the ad identifier: The visit must contain a real Google identifier. If you changed the source’s token positions, use the matching positions in the generated postback URL.

Decide what value to send

The generated URL uses {payout} for the amount. Send payout with the incoming event or set fixed event revenue. If you use both, check which amount the postback sends. Use 0 for a conversion with no monetary value. The generated currency is USD. Use the correct three-letter code if you send values in another currency. Changing the code does not convert the amount. Keep {tx_uid} and {event_ts} in the URL for the transaction ID and conversion time. Keep the generated URL private. Its secret authorizes requests to the destination.

Test the full journey

Use a real eligible Google ad click and complete the selected conversion. Check that:
  1. The visit has its Google identifier.
  2. The event appears in Metricanic.
  3. Its outgoing attempt succeeds in Postbacks.
  4. The conversion appears under the correct action in Google Ads.
If the event exists but the conversion is missing in Google, check the event’s Outgoing postback settings and delivery details.

Keep the connection usable

Reconnect if Google requires authorization again. Check the destination account and conversion action if setup fails. Archive integration stops conversion delivery through the connection. It does not stop advertising in Google. Record Google advertising spend separately with cost settings or cost corrections.