Send events to Google Analytics 4 without code: leads, payments, bots

Sending events to Google Analytics 4 in nana800 takes one block: it sends an event from the server through the Measurement Protocol when something important happens, such as a payment in a CRM or a lead in a Telegram bot. To connect it you need a data stream ID and an API secret from the Google Analytics settings. Every event costs $0.001, and your balance is topped up to $3.50 for free every month.

Build it in the builder
  • Block run: $0.001
  • Free every month: $3.50
  • No card needed

What you can do

  • Send GA4 events that do not happen on your site: a payment, a lead from a bot, a call, a deal status change in a CRM
  • Pass event parameters as name and value pairs, for example the lead source or the product name
  • Link an event to a site visitor with client_id and to your customer with user_id
  • Work with a website (GTAG type) and with a mobile app on Firebase
  • Check every event on the Google validation server and get the error text if Google finds a problem

Blocks in the builder

  • Google Analytics event

    Action · $0.001 per run

    Sends one event with parameters to Google Analytics 4 through the Measurement Protocol, for a website or a Firebase app. It validates the event with Google first, returns success_sent and puts validation errors into error_text.

How to set it up

  1. 1

    Get the keys in Google Analytics

    In Google Analytics 4 open Admin, then Data streams and the stream of your website. Copy the measurement ID that looks like G-XXXXXXX and create a secret in the Measurement Protocol API secrets section. For a Firebase app you need firebase_app_id instead of the measurement ID.

  2. 2

    Add a trigger that brings the event

    Create a scheme in the builder and add a trigger that brings the event: webhook for leads and payments from your site or CRM, Telegram message from user to bot for actions in a bot. For the first test the button trigger is enough.

  3. 3

    Set up the block

    Add the track GA event block. In app type choose GTAG for a website or FIREBASE for an app. Paste api_secret and measurement_id, and write the event name in event_name, for example generate_lead for a lead or purchase for a purchase.

  4. 4

    Add the visitor and parameters

    Put the site visitor ID into client_id if it came with the lead: the _ga cookie stores it. You can pass your own customer ID in user_id. Add event parameters in event_props: the name on the left, the value or a trigger field on the right.

  5. 5

    Turn the scheme on and test it

    Turn the scheme on, press the button trigger and open the block result. If success_sent is false, error_text holds the answer of the Google validation server with a hint on what to fix. When everything works, keep the scheme on. While it is on, it costs $0.0042 per hour.

Frequently asked questions

Every event costs $0.001. An enabled scheme costs $0.0042 per hour. Your balance is topped up to $3.50 for free every month, no card needed. A scheme kept on around the clock for a month spends most of that on scheme hours.

In Google Analytics 4: Admin, Data streams, the stream of your website. The measurement ID that looks like G-XXXXXXX is measurement_id. In the Measurement Protocol API secrets section of the same stream you create the secret for api_secret.

Google Analytics 4: the block sends events through the Measurement Protocol with a data stream ID and an API secret. Choose GTAG for a website, or FIREBASE for a mobile app on Firebase with the firebase_app_id and app_instance_id fields.

It is the visitor ID that Google Analytics uses to link an event to the visits of that person. The _ga cookie stores it, so it is sent together with the lead from your site. If you know the customer in your own system, add their ID in the user_id field.

The block first sends the event to the Google validation server and then to normal data collection. If validation finds errors, success_sent is false, the block is marked as failed and error_text lists them. Google may ignore an event with errors, so fix them right away.

No. The block is set up with fields in the browser, and the event data comes from the trigger. The event only has to reach the scheme: through a webhook from a CRM or payment service, a message to a Telegram bot, or on a schedule.

Build your first scheme for free

Sign-up is free and needs no card. Every month the balance is topped up to $3.50 for free, enough for about 3,500 runs of basic blocks.

Build it in the builder