Call Click
CompleteA weak, early-funnel intent signal — deliberately valued below Generate Lead, Meta Advanced Matching intentionally off.
Overview
Fires on a click on any tel: link. No LinkedIn tag on this goal (LinkedIn tracking here would need its own Insight Tag/Conversion ID pairing, not built for this weaker signal). Valued and gated deliberately lower than Generate Lead — this is an unverified click, not a qualified interaction.
GTM Configuration
| Tag | Type | Trigger |
|---|---|---|
GA4 - Call Click | Google Analytics: GA4 Event | Call Click Trigger |
Google Ads - Conversion (Call Click) | Google Ads Conversion Tracking | Call Click Trigger |
Meta - Contact (Call Click) | Meta Pixel (Standard event: Contact) | Call Click Trigger |
Trigger: Call Click Trigger
Click - Just Links trigger, single condition: {{Click URL}} contains tel:.
GA4
Event name: call_click
Key Event: No
Google Ads
Category: Contact
Value: ₹75 — A weak, early-funnel, unverified intent signal — deliberately valued below Generate Lead.
Status: Secondary
Count: One.
Meta
Event: Contact (Standard)
Advanced Matching: Not enabled
Intentionally NOT enabled — a call click happens before any lead data exists, so there’s nothing real to match on yet.
CAPI: Client-side Pixel only for this goal — not part of the current CAPI/server-side build.
Bugs & Fixes
The same fix, wrongly applied
Symptom
Call Click and WhatsApp Click’s Meta tags fired the instant any visitor accepted the cookie banner, with zero actual clicks.
Root Cause
The Consent Update retry-trigger fix from #2 was mistakenly also applied to these tags — which are event-driven (fire fresh on every real click), not page-load tags with a stale-evaluation problem.
Fix
The retry-trigger fix only applies to tags whose sole trigger is a one-time page-load event, never to already-event-driven tags. This exact mistake recurred once more later in the build — see #13.
Testing Checklist
- 1.Fresh Tag Assistant session.
- 2.Before consent: click a tel: link. Only GA4/Google Ads should fire.
- 3.Accept the cookie banner alone, without clicking anything — confirm the Meta Contact tag does NOT fire (this tag is event-driven; it must never carry a Consent Update retry trigger — see Debugging Journal #3).
- 4.Click a tel: link with consent granted — confirm all 3 tags fire.
- 5.Confirm Meta’s tag shows no Advanced Matching data — expected and correct for this goal.