Google Analytics 4 in Workflows

1. Log into your Google Analytics account > go to Admin > Account Settings > and under the Property column, click [Data streams]

   

2. Select the appropriate data stream > copy your Measurement ID and paste it in a note or doc (you’ll use this later in your Ivorey workflow)
   
   Note: Turn on Enhanced Measurement in your Data Stream settings to automatically track actions like scrolls, outbound link clicks, and file downloads.

   

3. Scroll down and click [Measurement Protocol API secrets]

   

4. Before an API Secret can be created, you need to acknowledge that you have completed the necessary privacy discussions and have received the rights from your end users for the collection and processing of data. Click the [Review Terms] button, at the top right corner, and then click [I acknowledge]

5. Create a new API secret key, give it a nickname, copy the value and paste it in a note or doc (you’ll use this later in your Ivorey workflow)

6. Lastly, go to Admin > Data collection and modification > Data retention > choose a retention period that suits your needs (e.g. 14 months) > and make sure [Reset on new user activity] is enabled

1. From the main Ivorey menu, go to [Workflows] > click [+ Create Workflow] or open an existing one​

2. At the top of the workflow, click [+ Add a Trigger] > and select the trigger you want to track, such as:

   1. Form Submission - when a form is submitted, to send this event to Google Analytics

   2. Page Visit - when someone visits a specific page, such as a product page, to track user behaviour

   3. Product Purchase - when a product is purchased, to send purchase-related data, such as order value, to Google Analytics

3. Click the [+] icon to add an action > then search for and select [Add to Google Analytics] under Actions​

   1. In the dropdown menu, select [Google Analytics 4]

   2. Paste the Measurement ID you copied from Google Analytics

   3. Enter an Event Name that clearly describes the action you want to track (e.g. “lead_submitted”, “appointment_booked”, “checkout_completed”)
      
      Note: Event names should follow Google Analytics naming rules - they are case-sensitive, should not include spaces, must start with a letter, and can only include letters, numbers, and underscores. Avoid using reserved Google Analytics event names.

   4. Paste the API Secret you copied from Google Analytics

   5. (optional) Add an Event Value related to the event, such as revenue amount or number of clicks, if needed​
      
      Note: Make sure there are no spaces before or after the Measurement ID or API secret, or the action will fail.

   6. Click [Save Action] at the bottom

4. You can continue to build out your workflow with more actions, as needed, such as:

   1. Send Email/SMS - After tracking an event such as “newsletter_signup”, send an email or SMS to deliver a welcome message or next steps

   2. Add Contact Tag - After tracking a purchase event, add a tag (e.g. “Purchased: Product Name” or “VIP Customer”) to trigger other automations

   3. Create/Update Opportunity - After tracking an “appointment_booked” event, move the contact into a sales pipeline stage (e.g. Booked Call)

   4. Send Internal Notification - After tracking an application or form submission, notify yourself or your team

5. When you’re done, toggle the workflow to [Publish], in the top right corner > and click [Save]

6. Test your workflow by completing the trigger (e.g. send a test form submission) > check the [Execution Logs] tab to see if there were any errors > then check the Google Analytics dashboard, under the [Realtime] tab, to confirm your events are showing up correctly​

If events are not showing up, double-check that the Measurement ID and API Secret are entered correctly without spaces. Verify that the event names match those configured in your workflow, and ensure that no filters are blocking data in your Google Analytics settings.

API Secrets can occasionally expire or need to be refreshed for security reasons. Reviewing and updating your API Secret from time to time helps ensure your Google Analytics integration remains active.

We recommend testing after any major change (like updating domains, editing events, or new campaigns) to ensure your data continues flowing correctly.

While you can see events instantly in the Realtime tab, Google Analytics 4 can take 24 to 48 hours to process that data and show it in your main Engagement or Events reports. If it’s working in Realtime, you’re all set!