When your CRM sends offline conversions to Google Ads, each conversion now goes to exactly one Google Ads customer account: the one that owns the click. If your organisation runs several Google Ads customer accounts under one login (for example one per location), you can tell the CRM which record values belong to which account, and the CRM works out the rest from the click itself. Conversions are never sent to an account that does not own the click.
​

1. Before You Start

2. Open the Google Ads Settings

3. Add Customer Routing Rows

4. The "Changed To" Option for New Records

5. Resolve Owners for Existing Records

6. Rules Left on Removed or Revoked Accounts

7. Deleting a Google Ads Login That Still Has Rules

8. Mapping the Campaign ID from CallTrackingMetrics

9. What You Will See on Records

10. How the CRM Picks the Account

11. Frequently Asked Questions
​

You will need:

Access requirements: CRM administrator. The section appears on the Google Ads Settings page for every instance that has the Google Ads integration.

If you do not see the "Customer routing" section on your Google Ads Settings page, contact Dazos support so the latest release can be confirmed for your instance.
​

From the CRM, navigate to Settings → Integrations → Google Ads Settings.

The page has these parts, from top to bottom:

Scroll down to Customer routing. Each row says: "when a record's field holds this value, its conversions belong to this Customer ID".

First select a login and a customer in Select Google Ads Account & Customer above; the field list in the form loads for that selection. Then fill the form below the table:

1. Click Save Routing. The row appears in the table and applies to the next conversion immediately.

2. To change a row, click the pencil on its line, edit the form and click Save Routing again. Click Cancel to leave it unchanged.

3. To remove a row, click the trash icon and confirm.
​

Tip: Add one row per location (or per value) for every module you send conversions from. Routing rows are checked before the CRM asks Google anything, so they are the fastest and most reliable way to route.
​

Important: The Customer ID must be digits only. A value with letters is refused with the message "Enter a valid Google Ads Customer ID (digits only)".
​

Below the routing form there is a switch: Also evaluate 'Changed To' rules when a record is created.
​

Leave it off (the default) if your conversion rules fire when a field changes on an existing record. Turn it on if your records are created with the value a rule looks for already filled in, for example a Location set by a workflow at creation time. When it is on, a "Changed To" rule also fires for a brand-new record whose field already holds the value.
​

The switch saves as soon as you click it and applies to every conversion rule on your instance.
​

Records created before this release have a click id but no owning customer account yet. This tool assigns one, without sending anything to Google Ads.

1. Choose the module (Leads, Intake Opportunities or Accounts).

2. Keep Dry run switched on and click Run. The result line tells you how many records were scanned, how many could be resolved and by which method, and how many could not be resolved.

3. If the numbers look right, switch Dry run off and click Run again. The owning Customer ID is now written on each resolved record.
​

Tip: Run this once after you have entered your routing rows. Records that match a routing row resolve instantly; the others are looked up in Google Ads by campaign or click, which takes longer.
​

If a Google login was deleted, revoked or deactivated while conversion rules were still attached to it, those rules never fire. The page shows a warning panel listing them.

Pick the active login in Move to and click Move rules. The page reloads and the panel entry disappears once the rules are attached to the working login.
​

Important: Enter your routing rows (section 3) before moving rules. Once moved, the rules are live again, and the routing rows are what keeps each conversion on the right customer account.
​

A login that still has conversion rules cannot be deleted; the CRM answers "This account still has N conversion rule(s). Move them to another account first."

1. In Connected Google Ads Accounts, click the pencil next to the login.

2. In the amber box Move all conversion rules to, choose the login that should take over the rules and click Move rules.

3. Click Delete Account and confirm.
​

If you use CallTrackingMetrics, four new keys are available in Settings → Integrations → VOIP Settings → Map Calling Fields: Google Ads Campaign ID, Google gbraid, GA4 session cookie and Ga Medium.
​

Map Google Ads Campaign ID onto the GACID field of Leads. With the campaign id on the record, the CRM can find the owning customer account from the campaign, without a routing row and without searching clicks.
​

Leads, Accounts and Intake Opportunities have three new read-only fields in the Web Traffic block:

The CRM fills them the first time a conversion for the record is routed. When a Lead is converted, the values carry over to the new Account and Intake Opportunity.
​

For every conversion, the CRM checks these sources in order and stops at the first answer:
1. The owner already stored on the record.

2. A single customer: if all the matching rules target one customer account, that account is used with no lookup.

3. Your routing rows (section 3).

4. The campaign list already synced in the CRM (Manage Campaigns), by the record's campaign id.
5. Google Ads, by the campaign id.

6. Google Ads, by the click id, within 90 days of the record's creation.

If none of these gives an answer, or two sources disagree, nothing is sent and the attempt is logged with the reason "owner not found". Nothing is ever sent to an account that does not own the click.
​

Q: We have only one Google Ads customer account. Do we need routing rows? No. With a single customer account every conversion goes there, exactly as before.
​

Q: A conversion did not go out. Where do I look? Open the Dazos Logger for the service "google ads". Each attempt has a routing line with the method used and the customer account found. "owner not found" means no source could tell which account owns the click; add a routing row for that record's value or map the campaign id (section 8).
​

Q: Can a record's owning account be changed later? The stored owner is reused for later conversions. To change it, clear the three Web Traffic fields on the record, add or correct the routing row, and the next conversion resolves the owner again (or run the resolve tool for existing records).
​

Q: Does "Resolve owners for existing records" send conversions? No. It only stores the owning Customer ID on records. Conversions are still sent by your conversion rules.
​

Q: Why does the warning panel show a login I already removed? Its conversion rules are still attached to it. Move them to an active login (section 6) and the panel disappears.
​

Q: Does the click-id lookup work with a Google Ads manager account? Routing rows and campaign ids work in every setup. If you connect a manager (MCC) login and conversions resolve as "owner not found" with an API error in the log, contact Dazos support.
​

If you run into issues:

1. Check the Dazos Logger (service "google-ads") for the routing line of the record and its reason.

2. Confirm the record's value matches a routing row exactly, and that the login in Connected Google Ads Accounts is Active.

3. Contact Dazos support with the log entry details and reference CRM-4122.