WhatsApp Click

Complete

Same value/gating logic as Call Click — the interesting part is the two-trigger OR-logic pattern this required.

Google AdsGA4Meta

Overview

Fires on a click matching either wa.me or web.whatsapp.com — the two distinct URL patterns WhatsApp links can take depending on device/client. This required a specific, non-obvious trigger pattern to get OR logic correct (see Bugs & Fixes).

GTM Configuration

Tag	Type	Trigger
`GA4 - WhatsApp Click`	Google Analytics: GA4 Event	WhatsApp Click Trigger - wa.me OR WhatsApp Click Trigger - web.whatsapp.com
`Google Ads - Conversion (WhatsApp Click)`	Google Ads Conversion Tracking	WhatsApp Click Trigger - wa.me OR WhatsApp Click Trigger - web.whatsapp.com
`Meta - Contact (WhatsApp Click)`	Meta Pixel (Standard event: Contact)	WhatsApp Click Trigger - wa.me OR WhatsApp Click Trigger - web.whatsapp.com

Trigger: Two separate single-condition triggers, both attached to every tag

WhatsApp Click Trigger - wa.me ({{Click URL}} contains wa.me) and WhatsApp Click Trigger - web.whatsapp.com ({{Click URL}} contains web.whatsapp.com), both attached to each tag. Building this as ONE trigger with two conditions would produce AND logic — impossible for a single URL to satisfy both, so it would silently never fire. Two separate triggers on the same tag is GTM’s actual OR pattern. Confirmed live: both tags carry both trigger IDs.

GA4

Event name: whatsapp_click

Key Event: No

Google Ads

Category: Contact

Value: ₹75 — Same reasoning as Call Click — a weak, unverified early-funnel signal.

Status: Secondary

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.

AND vs. OR trigger logic

Symptom

WhatsApp click tracking needed to match either wa.me or web.whatsapp.com URLs — built as a single trigger with two conditions, it silently never fired.

Root Cause

A single trigger with two conditions produces AND logic (both must be true simultaneously) — impossible for one URL to satisfy both.

Fix

The correct GTM pattern for OR logic is two separate single-condition triggers, both attached to the same tag.

Testing Checklist

1.Test BOTH URL patterns separately — wa.me and web.whatsapp.com — confirm each independently fires all 3 tags.
2.Confirm via Tag Assistant that the tag’s Tag Details panel shows two trigger IDs, not one combined condition.
3.Same pre/post-consent sequence as Call Click.