What the plugin does and does not do

When the option is on, the page gets one short inline script. It listens for clicks on the button’s links, pushes { event: 'beckonbird_click', beckonbird_channel: … } to the page’s dataLayer, and, if a gtag function exists on the page, also calls gtag('event', 'beckonbird_click', { channel: … }). It does not load Google’s script and it does not know your measurement ID. That belongs to the Google Analytics plugin, the theme or the tag manager you already use.

Getting it into Google Analytics 4

If your site uses gtag directly, the event arrives by itself. Click the button once yourself and look for beckonbird_click among the events in the real-time report. To use the channel in reports, add channel as an event-scoped custom dimension in the property’s admin, and to count the clicks as a goal, mark the event as a key event. Both are done in Google Analytics, not in WordPress.

If you use Google Tag Manager, the same event is in the data layer, and the tag manager guide shows the trigger and the variable.

Consent

The plugin does not know about your consent banner. If your analytics only starts after a visitor accepts, the event goes where it goes: nowhere before consent, and into analytics after. That is the correct behaviour for most setups, and it also means numbers from Analytics will always be lower than the real number of clicks.

If you want a count that does not depend on Analytics

Pro keeps its own count on your server, per channel, person and page, without cookies and without an IP address. Which page do your WhatsApp leads come from shows what it looks like.