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
Streaming Events From Firebase
Tracking the customers’ activity in your mobile application gives you insights into their journey and experience, thus helping you understand their behavior and see their preferences and expectations.
Using the mobile tracking feature, you can collect this data and use it for segmentation, targeting, and personal recommendations (similar to web tracking for a site).
Important!
To activate the mobile app tracking, subscribe to the activate the PROFESSIONAL plan.
The following diagram shows the overall flow of the data transfer from your mobile application to Yespo’s CDP.
How to Set Up Tracking
To track users' activity in your mobile app, set up the streaming of relevant data to a BigQuery table, from where it will be automatically sent to our CDP.
The data about the customer events come to Firebase. Then they are passed to a BigQuery table and exported to Yespo CDP.
To set up the mobile tracking:
-
Configure the customer data transfer from a mobile app.
-
Connect Google BigQuery with your Yespo account.
Configuring data transfer from a mobile app
To configure the customer data transfer from a mobile app to a BigQuery table, use the following instructions:
- Link BigQuery to Firebase;
- Data format and schema for Google Analytics 4 resources and Google Analytics for Firebase data exported to BigQuery.
The method of event storing depends on the operating system and programming language used. See Firebase API Reference for instructions.
The following table describes the required event types:
|
Event |
Description |
|---|---|
|
SCREEN_VIEW |
Page view |
|
VIEW_ITEM |
Item page view |
|
VIEW_ITEM_LIST |
View of the items list (from a recommendations block) |
|
VIEW_CART |
Cart page view |
|
ADD_TO_CART |
Items adding to the cart |
|
REMOVE_FROM_CART |
Items removed from the cart |
|
PURCHASE |
Item purchased |
|
Firebase_campaign |
Used for tracking the link transitions from trigger campaigns. The tracking uses UTM tags. |
For more details, see [GA4] Recommended events for the full list of events recommended by GA.
Important!
- Set the user_id for all registered users using this instruction.
- Update the contact information (user_id) in the account using the Add/update contacts API method.
After setting up the data transfer to BigQuery, set up the BigQuery connector in your account.
Connecting Google BigQuery with Yespo
Connect Google BigQuery with your eSputnik account for sending the data automatically to our CDP.
NOTE
You need to subscribe to the PROFESSIONAL plan to send the data for the mobile app tracking and activate the menu Mobile Tracking.
-
In your Yespo account, go to Account > Settings and select Mobile Tracking from the menu on the left-hand side.
-
Click the Connect Google BigQuery button.
NOTE: When creating a new connector, the first step warns you that the utm_term UTM tag will be changed. Go to Profile > Settings > Links and make sure that this change does not hamper tracking your campaigns. See How to set up UTM tags for more details. -
Click Next.
-
Click Upload to upload the BigQuery key file.
NOTE: To learn how to create and download a key file, see Integration with Google BigQuery.
-
Click Validate connection. If a proper connection is established, the “Connection succeeded” message appears for a short while.
-
Click Next.
-
Click the down arrow icon and select a BigQuery dataset from the list, then click Done.
The Google BigQuery connection appears on the Mobile Tracking page.
Now the mobile tracking is configured in your Yespo account.
Contacts Matching
When a user is not authorized in your app, but has a mobile token, getting a contactId from the account will help you. You can do this using the public API method. Pass the resulting contactId to the user.properties.
The contact ID is its unique identifier, with the help of which the system identifies a person when they enter the application from different channels, browsers, and devices.
This way, you can collect all the data about the interaction of users with your application and send them omnichannel campaigns.
The system will add all available contact identifiers to the unique contact ID, such as mobile and web tokens, phone number, and email address.
