> For the complete documentation index, see [llms.txt](https://docs.talkfurther.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talkfurther.com/products/web-data/google-ads-conversion.md). # Google Ads Conversion Google Ads is often one of the largest paid channels for senior living operators, but native conversion tracking usually stops at clicks or early web actions. It does not show whether that click eventually became a real lead, a tour, or a move-in. That makes it harder to understand true campaign ROI, optimize bidding toward revenue-driving outcomes, and prove performance to agencies or finance teams. Further’s Google Ads Offline Conversions closes that loop by capturing the Google Click ID (GCLID) when a prospect arrives through a Further-powered experience, then sending configured downstream events back to Google Ads as offline conversions. #### What it is and what it does Google Ads Offline Conversions: * Captures the GCLID when a prospect clicks a Google ad and lands on a Further-managed experience. * Sends configured conversion events back to Google Ads later, tied to that original click ID. * Supports up to five conversion types per integration, including Lead Created, Qualified Lead, Tour Scheduled, CRM Stage, and Move-In. * Uses backend processing, not GTM event firing, to upload those offline conversions. #### Key outcomes * Better visibility into which campaigns, ad groups, and keywords drive real business outcomes. * Smarter bidding toward leads, tours, and move-ins instead of just superficial web conversions. * Stronger ROI reporting across the full funnel from ad click to downstream conversion. #### What problem it solves Customers often struggle with three things: * They can see clicks or form fills, but not whether those leads turned into tours or move-ins. * They cannot reliably optimize Google Ads toward the outcomes that matter most. * Their reporting stops too early in the funnel to show true paid-search performance. This integration solves that by linking downstream events in Further back to the original Google ad click. #### Value propositions * Outcome-based optimization. Google can optimize on the events you actually care about, not just early-stage conversions. * Closed-loop attribution. You can connect ad spend to later-funnel results like tours and move-ins. * No frontend custom build required for the offline conversion flow. The core upload process happens in the backend once the integration is configured. #### How it fits in the Further ecosystem Google Ads Offline Conversions works alongside the rest of the Further platform: * It relies on Further-managed lead journeys where GCLID can be captured. * It can send outcomes that happen later in Further, including tours, move-ins, and supported CRM-stage updates. * It complements, but is distinct from, GTM-based web event tracking. GTM is useful for site-side analytics and ad tags, while Offline Conversions is the backend Google Ads attribution layer. #### Important notes * This feature is not real-time. After Further sends a conversion, Google may take anywhere from a few minutes to about 24 hours to show it in reporting. * Customers must create the relevant conversion actions in Google Ads first, then map those action IDs inside Further. * Lead Created does not fire for leads imported from certain CRMs, because those leads did not originate inside Further. * Attribution depends on GCLID coverage. If a lead never had a GCLID, Further cannot attribute that conversion back to Google Ads unless enhanced conversion matching is enabled. * Some phone-originated paths may still have limited GCLID coverage depending on how the interaction started. #### How do you set it up **1. Prerequisites** * A Google Ads account with at least one campaign running. * Conversion actions created in Google Ads for the events you want Further to send back. * A Further-managed experience where GCLID can be captured when a prospect arrives from Google Ads. **2. Enable or access it** * Add a Google Ads integration in Further and connect the customer’s Google Ads account. * New integrations use OAuth as the standard path. * After the account is connected, assign the relevant Google Ads conversion action IDs inside Further. **3. Required setup steps** * Decide which Further events should map to which Google Ads conversion actions. * Paste each Google Ads conversion action ID into the matching field in Further. * Confirm the right communities and channels are assigned to the integration. * If needed, configure values and channel-specific overrides for different lead sources. **4. How to test it’s working** * Complete the Google Ads connection and mapping setup. * Trigger a real or test lead journey from a Google ad click into a Further-managed flow. * Check Further’s conversion logs to confirm the event was sent or see why it was skipped or failed. * Check Google Ads under Goals → Conversions after processing time has passed. #### Integrations and configurations overview **Required** * Google Ads account. * Google Ads conversion actions. * Further Google Ads integration configured in the dashboard. **Optional** * Enhanced conversion matching for cases where GCLID is unavailable but matching identifiers exist. * GTM or GA4 for separate web analytics and event-tagging use cases. **Key configuration options** * Which conversion types are enabled. * Which Google Ads conversion action IDs are mapped to each event. * Whether channel-specific overrides or custom values are used. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.talkfurther.com/products/web-data/google-ads-conversion.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.