Key Takeaways Use separate conversion actions for calls placed from ads and calls made after an ad-driven website visit. Keep phone-number clicks Secondary when completed or qualified call tracking is available. Inspect call recording before launch because it is enabled by default for many eligible accounts and carries notice and consent considerations. Test the forwarding number, destination line, qualification rule, conversion action, and call report before allowing the signal to guide bidding. In this guide Match each customer route to the right conversion Review call qualification before installing anything Turn on reporting and configure calls from ads Track calls made after a website visit Test the full route, not just the tag Use a simple cost check before changing bids Fix these failures before letting calls guide bidding If customers can call directly from an ad or after visiting your site, create two Google Ads conversion actions: Calls from ads and Calls from websit...
Key Takeaways Use native Google Ads tracking as the usual primary bidding signal, while sending the same successful event to GA4 for cross-channel analysis. A GA4-based Google Ads conversion can guide bidding if it is primary and its goal is selected; it is not automatically an inferior option. Never allow native and GA4-based copies of the same outcome to count as primary bidding actions at the same time. Use One for typical lead actions and Every for purchases, adding unique transaction IDs to prevent repeat counting of the same order. Judge performance against CRM, booking, call, or order records rather than expecting GA4 and Google Ads totals to match exactly. In this guide The two systems have different jobs Choose the source by business outcome When native Google Ads tracking is the better fit When a GA4-based conversion is a sensible choice Do not give the same event two primary labels Set counting rules around the action, not a blanket policy Enhanced conversions may se...