First steps
User Data
- Responsive Email Editor Review
- Designing your email
- Creating Synchronized Modules
- Setting Up Responsive Email Design
- Setting Up Smart Containers
- Creating a Gmail Promotions Annotation
- Adding The Rollover Effect
- Adding Anchor Links
- Module Library
- Adding a Table to an Email
- Adding Custom Fonts
- Creating CTA Button
- Working with Images
- Creating Timer
- Using AI in the Email Editor
- Messenger Protocol Support in Email Clients and Platforms
Omnichannel
- Setting Up Widgets for Your Site
- Widgets Gamification
- Widget Calling
- Setting Up Locations for the Widget Calling Rules
- Storing data from widgets to contact fields
- Using Annoyance Safeguard
- Actions After Subscription
- Replacing Double Opt-In System Workflow
- Creating Pop-ups via Google Tag Manager or WordPress
- Sending Yespo Widget Events to Google Analytics
- Using A/B Tests for Widgets
- Collecting Contact Information Using Request Forms
Automation
- Building and Editing Workflows
- Configuring Workflow Start/Stop Conditions
- Start Block
- Popular Blocks
- Message Blocks
- Using One from Many Message Block
- Contact Blocks
- Conditions Blocks
- Other Blocks
- Message to Segment Blocks
- Time Blocks
- Advanced Workflow Block Parameters
- Setting Up Allowed Send Time
- Using Workflow Launch History
- Webhook Workflows
- Workflow Troubleshooting
- Double Opt-In
- Welcome Сampaign
- Welcome Series Segmented by Category
- Launching a Workflow After a Contact Import
- Regular Workflow for a Segment
- Birthday Campaign
- Linking Workflow to the Button
- Using Variables from Order in Workflow
- Collecting Order Feedback
- Customer Reactivation
- Sending Extra Campaigns
- Sending Reminders at the Time Specified by the User
- Sending Campaign to Those Who Did Not Open the Previous One
- Using A/B Tests In Workflows
Personalization
Analytics
- Email Campaign Report
- Web Push Campaign Report
- Viber Campaign Report
- Mobile Push Campaign Report
- App Inbox Campaign Report
- Telegram Campaign Report
- In-App Report
- Widget Report
- Triggered Campaign Report
- AMP Campaign Report
- SMS Campaign Report
- Multilingual Campaign Report
- Setting up UTM Tags
- Revenue from Campaigns
- Tracking Campaign Performance in Google Analytics 4
- Message Analytics
Multilanguage Campaigns
Events and Behaviour Tracking
Recommendations
API
Security and Compliance
Sending Yespo Widget Events to Google Analytics
You can send the event data related to the interaction of users with your Yespo widgets to your Google Analytics (GA) account.
Yespo supports the Universal Analytics and Google Analytics 4 scripts for tracking events on your website.
Important
It is recommended to install the Google Analytics 4 script, since the Google Universal Analytics property will stop processing data starting on July 1, 2023 (July 1, 2024, for Analytics 360 properties).
You have to install the script, using one of the following methods:
- Setting up GA4 script for a website (directly into the website code).
- Setting up GA4 in GTM.
After that, you have to enable exporting the widget event data to Google Analytics.
The entry point for events depends on the method you use to install the script:
- If there is GoogleAnalytics3 (ga), send into it.
- If there is dataLayer and there is gtag and dataLayer has at least one G-* tag:
- Then call gtag with parameters (send_to is added) for each tag id.
- Otherwise, we write to dataLayer.
Setting Up GA4 Script for a Website
To set up the Google Analytics GA4 script for a website:
1. In your GA account, select the Admin icon to open the GA settings.
2. Click Create → Property.
3. In the Property setup, enter the property name, select the country, the time zone and the currency, then click Next.
4. Describe your business — indicate the industry category and company size.
Choose your business objectives and click Create.
5. In your created property menu, select the Web platform.
6. Enter the website URL and the stream name in the corresponding boxes, then click Create & continue.
7. In the Web stream details menu, click the copy icon beside the Measurement ID.
8. Go to your site and insert the following code after the <head> tag, where substitute MEASUREMENT_ID with the one copied in the previous step.
<!-- Google Analytics -->
<!-- Google tag (gtag.js) -->
<script async src="https://www.googletagmanager.com/gtag/js?id={MEASUREMENT_ID}"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', '{MEASUREMENT_ID}');
</script>
Setting Up GA4 in GTM
Before proceeding to setting up GA4 in GTM, you have to:
1. Create a GTM account and a container following these instructions.
2. Follow the GTM standard web page installation instructions.
To set up Google Analytics 4 (GA4) in Google Tag Manager (GTM):
1. Follow steps 1 to 6 described in the Setting up GA4 script for a website section.
2. In Tag Manager, select Tags in the left-hand side menu and click New to create a new tag.
3. In the window, enter the tag name, set the following tag configuration and triggering, then click Save:
- Select Google Analytics: GA4 Event as Tag Type.
- Enter the measurement ID copied in step 7 of this instruction.
- Select All pages for Firing Triggers.
4. In the left-hand side menu, select Triggers and then New to create a new trigger.
5. In the slideout window, enter the trigger name and click the Trigger Configuration pane.
6. Set the following configuration in the trigger configuration window, then click Save:
- Select Custom Event as Trigger Type.
- Enter yespo as Event name.
- Select All Custom Events for the trigger to fire on.
7. Go to Variables in the left-hand side menu, and select New in the User-Defined Variables pane.
8. In the slide-out window, enter configuration name and click the Variable Configuration pane.
9. Set the following variable configuration, then click Save:
- Variable Type
- Data Layer Variable Name
- Data Layer Version
You have to create 3 variables with the following parameters:
| Variable Type | Data Layer Variable Name | Data Layer Version |
|---|---|---|
| Data Layer Variable | eventAction | Version 2 |
| Data Layer Variable | eventCategory | Version 2 |
| Data Layer Variable | eventLabel | Version 2 |
10. Go to Tags in the left-hand side menu, and create a new tag with the following configuration, then click Save:
- Select Google Analytics: GA4 Event as Tag Type.
- Select the tag you created at step 3 as Configuration Tag.
- Enter yespo as the event name.
- In Event Parameters, use the parameters and their values created in steps 8 and 9.
- In Firing Triggers, select Yespo event.
11. Click Submit on the top panel.
Enabling Widget Event Data Exporting to GA
To enable the widget data transfer:
-
In your Yespo account, click Site — Widgets, and select the widget type in the left-hand side menu.
-
Select the widget, which events you want to export.
-
In the widget menu, select Integrations and enable the Export data to Google Analytics slide button.
All the event data collected for that widget will be passed automatically to your GA account.
Viewing the Real-time Analytics
To view the real-time analytics in your GA account:
1. Select Reports → Realtime in the left-hand side menu.
2. In the Event count by Event name pane, Select yespo in the Event name column.
The list of event parameters displays. Click them to see the events.
The highlighted parameters are explained in the following table.
| Parameter | Description |
| eventAction | It contains the events as described in Event categories and actions. |
| eventCategory | Widget type. |
| eventLable | Widget ID. |
Event Categories and Actions
GA displays Yespo events in a table as shown below.
The Event Category column contains the description of a widget/form type, as described in the following table.
|
Widget/form type |
Description |
|
BUILT_IN |
Inline widget/form |
|
DETACHED |
Pop-ups |
|
FLOATING_BOX |
Floating box, informer |
|
LAUNCHER |
Launcher |
|
CONTENT_LOCKER |
Content locker |
The Event Action column in GA contains the action type made on a widget. The event actions are explained in the table below.
|
Event Action |
Description |
|
LauncherShow_[ID] |
The launcher button displays on a website. |
|
LauncherClick_[ID] |
The launcher button clicked. |
|
FormShow_[ID] |
The form displays on a website. |
|
FormClose_[ID] |
A site visitor closed the form. |
|
FormStartFilling_[ID] |
A site visitor started filling up the form. |
|
FormFinish_[ID] |
A site visitor filled in the subscription form (clicked “Subscribe”, no form validation errors). |
|
FormSuccessSubscribe_[ID] |
Form filling up status (subscription success). |
|
FormAlreadySubscribe_[ID] |
Form filling up status (already subscribed). |
|
FormErrorSubscribe_[ID] |
Form filling up status (subscription error). |
The [ID] part of the events for a specific widget sending its data to GA has the following structure: f(form){id}v(variant){id}, where “f(form){id}” is the form ID and “v(variant){id}” is the form variant ID.
For example, FormShow_f781v781 in your GA table means that the form with the ID of 781, and the variant ID of 781 was displayed on a site.
The form ID is displayed in Yespo, on the Widgets page in the ID column.
