WA.cr

Connect Google Analytics

Send your conversation events to your own Google Analytics, bring its audiences back as contact tags, and record your own events from Auto Flows.

Connecting Google Analytics puts your customer conversations next to your website numbers — messages, replies, short-link clicks and Auto Flow steps show up in your own GA4 property, and the audiences you build there come back to WA.cr as contact tags.

What it does

  • Events out. WA.cr sends conversation events to your GA4 web stream: WhatsApp messages sent, delivered, read and failed; replies on WhatsApp, Instagram and email; short-link clicks; and Auto Flow steps. You tick the ones you want. Each of these events carries the contact's WA.cr ID — never a phone number, email address or message text.
  • Audiences back as tags. Pick up to 20 GA4 audiences per property. Once a day, everyone in them that WA.cr can match gets a tag such as ga4:cart_abandoners — filter contacts by it, send a broadcast to it, or start an Auto Flow from it.
  • Your own events from Auto Flows. Add a Send to Google Analytics step to a flow to record events of your own, such as booking_confirmed or quote_sent.

Steps

  1. Open Integrations and choose Connect Google Analytics.
  2. Pick how you want to connect:
    • Sign in with Google — approve WA.cr on Google's own screen. Nothing to create, nothing to copy. This is the one to use when it's offered.
    • Use my own Google app (advanced) — the same, through an app you register in Google Cloud yourself. Switch on the Google Analytics Admin API and the Google Analytics Data API in your project first.
    • Service account (advanced) — paste a service account's key file, then add its email address as a Viewer in Google Analytics under Admin → Property access management.
  3. On the Google Analytics card, under Add a property, choose a property and press Add. Repeat for each property you want.
  4. Open Send events (Measurement Protocol) on the property.
  5. Check the Measurement ID (it starts with G-). It's filled in when the property has one web stream; otherwise copy it from Google Analytics under Admin → Data streams.
  6. In Google Analytics, open Admin → Data streams → (your stream) → Measurement Protocol API secrets and create a secret. Paste its value into Measurement Protocol API secret.
  7. Under Events to send, tick the events you want — including Events from Auto Flows if you'll use the Auto Flows step.
  8. Turn on Send these events and press Save.
  9. Press Send test event, then open Admin → DebugView in Google Analytics. The test event appears within a few seconds.

Browser IDs decide who gets events

Google Analytics counts people by the browser ID its cookie sets on your website. WA.cr sends a contact's events under their browser ID, so they join that person's visits to your site. Browser IDs reach WA.cr from your forms, from Auto Flows and from your developer integration.

Most contacts won't have one, and their events aren't sent — unless you tick Also send for contacts with no browser ID. Then they're sent under a stand-in ID that stays the same for each contact but never joins your website visitors.

Audiences as contact tags

  1. Open Audiences as contact tags on the property.
  2. Turn on Bring audiences back as contact tags, tick up to 20 audiences and press Save.
  • It runs once a day, early in the morning. Sync now runs it sooner — at most once an hour.
  • Google's audience lists run about a day behind your website.
  • Expect a low match rate: only contacts with a browser ID can be matched.
  • Someone who leaves the audience loses the tag at the next run. A tag you remove by hand comes back while they're still in the audience.
  • An Auto Flow that starts on a ga4: tag starts once each time someone joins.

Send your own events from an Auto Flow

  1. On the property, under Send events (Measurement Protocol), tick Events from Auto Flows and press Save.
  2. Open Auto Flows, edit a flow and add the Send to Google Analytics step.
  3. Give the event a name, such as booking_confirmed: letters, numbers and underscores, starting with a letter, up to 40 characters. Names Google keeps for itself, and names starting with wacr_, aren't allowed — the step tells you as you type.
  4. Add up to 24 parameters. Each has a name and a value, and the value can use variables such as {{contact.name}} or {{var.plan}}.
  5. Connect the step to whatever should happen next. It has one way out, and the flow always carries on.
  • A value that's a plain number, like 499, is sent as a number, so Google Analytics can add it up.
  • A value holding an email address, or that is the contact's phone number — with or without the country code — is left out. Google doesn't allow personal details.
  • Test runs send nothing.
  • The flow's run record shows whether the event was queued, or why not.

If you use RecoveryFlow

RecoveryFlow sends its own store events to Google Analytics straight from your WooCommerce store. A coming update also passes your shoppers' browser IDs to WA.cr at checkout — only when your store's cookie consent allows analytics, and only on the Scale plan — so far more of your contacts' events join their website visits, and more audience members match. Your ga4: audience tags are ordinary contact tags, so RecoveryFlow can read them like any other.

If it doesn't work

  • The test event doesn't show in DebugView — check the measurement ID, then paste the API secret again. Google accepts a wrong secret without complaint, so DebugView is the only real check. The secret must belong to the same web stream as the measurement ID.
  • Sending won't turn on — it needs a measurement ID, an API secret and at least one ticked event.
  • Real contacts' events never arrive — most contacts have no browser ID. Tick Also send for contacts with no browser ID, or collect browser IDs through your forms.
  • The property list is empty — a service account only sees properties it has been added to as a Viewer.
  • An audience matched almost nobody — expected: only contacts with a browser ID can be matched.
  • The Auto Flows step sends nothing — tick Events from Auto Flows on the property and make sure Send these events is on.
  • Press Test on the connection card at any time to check the connection.