LimeCall + Google Analytics 4:
Track Callback Conversions in GA4

No. Google sunset Universal Analytics (UA) on July 1, 2024 and stopped processing hits. The LimeCall analytics integration is built for Google Analytics 4 (GA4) only. If you were previously using Universal Analytics goals to track callback conversions, you need to migrate those goals to GA4 conversion events. LimeCall's GA4 integration sends events in the GA4 measurement protocol format — it is not compatible with the older Universal Analytics hit format.

Yes. LimeCall fully supports Google Tag Manager (GTM) for the GA4 integration. Instead of adding the LimeCall GA4 snippet directly to your page source, you can deploy it as a Custom HTML tag in GTM. LimeCall publishes a pre-built GTM tag template that you can import — it fires the correct GA4 events for callback request, callback completed, and missed call with all required event parameters pre-configured. Using GTM also lets you add additional triggers or conditional firing rules without touching your site code.

In GA4, go to Admin → Events. LimeCall sends events named "limecall_callback_request", "limecall_callback_completed", and "limecall_callback_missed". Find the "limecall_callback_completed" event in your events list — it will appear after the first test call — and click the toggle to mark it as a conversion. GA4 will then include this event in your Conversions report and allow you to use it as a goal in Google Ads. You can also create a custom conversion with a value equal to your average call revenue for monetary conversion tracking.

LimeCall sends the following custom event parameters with each GA4 event: utm_source, utm_medium, utm_campaign, utm_content, utm_term, page_location (the URL where the callback was requested), call_duration (in seconds, for completed calls), call_outcome (e.g. "demo_booked", "follow_up", "not_interested"), widget_name (the LimeCall widget that was used), and agent_name. All parameters are visible in GA4's DebugView during testing and in the Events report after 24–48 hours of data collection.

Yes. In GA4, go to Admin → Audiences and create a new audience based on users who triggered the "limecall_callback_completed" event. This audience syncs to your linked Google Ads account and can be used for remarketing campaigns — for example, showing follow-up ads to people who called but did not convert, or excluding existing customers from prospecting campaigns. GA4 audience syncing requires linking your GA4 property to a Google Ads account, which takes under 5 minutes in the GA4 admin panel.

Yes. Once LimeCall callback events are flowing into GA4, you can connect your GA4 property to Looker Studio (formerly Google Data Studio) using the native GA4 connector. In Looker Studio, create a custom dashboard that pulls callback event counts, conversion rates, and event parameters — segmented by source, medium, campaign, or page. This gives you a dedicated callback conversion dashboard alongside your other GA4 traffic data. LimeCall also publishes a free Looker Studio template pre-built for callback reporting that you can copy and connect to your own GA4 property.

Use GA4's built-in DebugView to verify the integration. Enable debug mode by adding the query parameter "?ga-debug=1" to your page URL (if using the LimeCall snippet directly) or by enabling the GTM preview mode (if using GTM). Then request a test callback on the page. Within 30 seconds, the "limecall_callback_request" event should appear in DebugView with all event parameters. After the call ends, "limecall_callback_completed" should fire. If events appear in DebugView, the integration is working correctly and data will flow into your GA4 reports within 24 hours.