How to Set Up Google Ads Enhanced Conversions for Agencies
Set up Enhanced Conversions for an agency by completing one client-specific measurement contract, obtaining approval for the customer-data path, isolating accounts and identifiers, implementing the event, and giving the client evidence that the browser, CRM, commerce, and offline results agree. Reuse the workflow and QA checklist, not another client’s business definition or data.
Use Google’s Enhanced Conversions best practices, web conversion setup, and offline conversion guidance. The client approves the data purpose, fields, retention, and business outcome; the agency implements within that boundary.
1. Open a client measurement brief
Record the client, account, website, product or service, region, conversion goal, decision owner, technical owner, privacy owner, and reporting window. Ask what the campaign should acquire: qualified lead, booked appointment, order, trial, activated account, opportunity, or another outcome.
Define the count unit and proof. A lead may be a valid form or sales-accepted record; an order may be a paid transaction with an order ID; a SaaS event may be workspace activation. Record how duplicates, existing customers, cancellations, refunds, renewals, and test records are handled.
Keep the raw, qualified, and completed milestones separate. Use Google’s primary and secondary action guidance to decide the optimization role after the client has approved the definitions.
2. Get client approval for data use
Before implementation, document which customer-provided fields may be used, where they originate, how they are normalized, what consent permits them, who can access them, how long they remain, and how the client deletes or revokes them. Review Google’s Enhanced Conversions best practices with the client’s privacy or security owner.
Do not copy raw email, phone, form content, passwords, payment details, or sensitive service data into agency tickets, URLs, screenshots, or logs. Use a synthetic test record or a restricted approved record. Include an offboarding step for credentials, test data, and agency access.
Test consent denied, consent granted later, regional variants, and third-party forms or checkouts. Client approval should cover the complete path, not only a tag template.
3. Inventory the client stack
List Google tags, tag-manager containers, analytics imports, forms, call or booking systems, ecommerce plugins, CRM connectors, product events, billing webhooks, and offline uploads. Record owner, account, last publish, event source, identifier, value, and status for each path.
Find duplicates before adding code. A custom thank-you trigger may overlap with a form provider, analytics import, CRM connector, or platform plugin. Mark each path as creator, enrichment, or reporting-only and name the source of truth.
Keep client environments isolated. A shared agency container or template must not carry another client’s conversion ID, value, identifier, audience, or test record through a variable mistake.
4. Choose the implementation path
Use a browser or tag-manager event when the client can prove the milestone in the web journey. Use a product, CRM, billing, booking, or server event when the outcome occurs later or outside the browser. Follow Google’s web conversion setup and Google tag guidance for the web foundation.
Name the conversion after the client milestone, not the agency implementation. “Qualified consultation” remains meaningful when the tag manager changes; “agency-form-v3” does not. Keep the technical mapping in the client brief.
For a lead, capture the approved source identifier through the form and CRM. For an order, use the order ID and trusted value. For SaaS, use workspace or account identity. For a booking or service, keep location and appointment identity.
5. Configure the conversion action
Create or review the action with the business name, category, counting choice, value behavior, conversion window, and primary or secondary role. Have the client owner approve any change. Do not accept a default because the agency has used it elsewhere.
Use a specific form-success, purchase, product, or booking trigger. Avoid a generic URL or page view that can fire on refresh or direct navigation. Make the approved identifier, customer-data fields, action name, timestamp, value, currency, and consent state available only according to the client policy.
If a later CRM or offline action is imported, keep it separate from the browser event until identity and duplicate handling are proven. Explain the layered counts in the client report.
6. Implement consent and matching
Connect the client’s consent state to the browser and any supported server or CRM path. Verify that the event is withheld or handled according to policy when consent is denied, is granted after the first page, changes, or differs by region. Do not let a backend import silently bypass the approved choice.
Use only the approved first-party fields. Keep them out of public URLs and debug output. Restrict access to implementation logs and remove raw values from the agency’s evidence pack. Record the consent test result, not the customer’s actual contact data.
7. Connect CRM, commerce, or product outcomes
Use the client’s source system for mature outcomes. For lead generation, map accepted, qualified, opportunity, and won stages. For ecommerce, map purchase, subscription, renewal, refund, and order identity. For SaaS, map signup, activation, trial, paid, and workspace identity. For local businesses, map call, booking, location, job, and payment.
Follow offline conversion guidance for supported imports. Start with a safe test set and check action, identifier, stage time, value, currency, consent handling, and accepted or rejected rows. Do not turn a CRM note, webhook retry, or booking reschedule into a new acquisition.
8. Document the value model
Use the client’s fixed, dynamic, or expected value. A qualified lead can use historical acceptance and win rates; an order can use finance-approved revenue or contribution; a booking can use completed-service value; a subscription can use first invoice or an approved expected contribution.
Keep currency, discounts, margin, product, location, plan, cancellation, and renewal rules visible. Never use an invented value to make a client report look better. Have the client finance or commercial owner approve changes because a value change can affect automated bidding.
9. Test a client-safe matrix
Use Tag Assistant for web checks and safe records for CRM, commerce, product, booking, or offline paths. Verify client account, action, identifier, approved fields, consent, timestamp, value, currency, and one-time behavior.
Test the events that match the client: validation failure, duplicate form, purchase retry, refund, call transfer, canceled booking, no-show, invited user, activation failure, CRM merge, lost identifier, rejected import, consent denial, mobile flow, and regional domain. Write expected zero, one, or update outcomes.
Remove raw customer data and credentials from screenshots and logs. The client should receive the test date, record type, expected result, observed result, owner, and remediation, not unrestricted personal information.
10. Reconcile and hand off
Compare browser or server events, Google Ads actions, client CRM or order data, qualified stages, and later outcomes by date, product, region, and account. Explain attribution window, time zone, consent, ad blockers, import delay, duplicate suppression, account merges, and sales-cycle maturity.
Give the client a handoff with event dictionary, technical mapping, consent decision, value formula, duplicate rule, sources, test evidence, reconciliation sample, owner, and next review date. The client should be able to understand the setup without asking the agency to interpret every conversion count.
11. Maintain approval and access
Assign client business and privacy owners plus agency strategy and technical owners. Require approval for primary status, counting, conversion windows, fields, consent, value formula, imports, and account goals. Record each change, test, effective date, and expected reporting effect.
Review access, credentials, containers, templates, and client data at offboarding. Do not retain a client test record or production identifier in an agency-wide library.
Common agency setup errors
- Copying another client’s event definition or conversion ID.
- Treating one client approval as permission for every account.
- Adding tags before finding platform and analytics imports.
- Mixing browser, CRM, server, and offline events without a duplicate rule.
- Reporting raw leads, bookings, or trials as customer revenue.
- Storing raw customer data in tickets or QA screenshots.
- Testing only the tag and not the client’s source-of-truth system.
- Changing goals without client approval and a reporting note.
The repeatable asset is the review process, while the business meaning remains client-specific.
Agency setup checklist
Confirm the client outcome, account scope, count unit, source of truth, approved fields, consent map, identifier, action role, value, duplicate behavior, source inventory, offline mapping, test matrix, reconciliation, owner, and offboarding plan. Use the Enhanced Conversions checklist and conversion tracking checklist for companion reviews.
Start with one client and one action. Obtain written acceptance of the evidence before applying the workflow to the next account.