It is possible to integrate WebEngage with Google Tag Manager (GTM). You just need to follow the following steps:

1. Login to your GTM account and create a GTM container to add WebEngage integration code
2. Next, you would have to go to the ‘New‘ tab and select the ‘Tag‘ option in order to create a custom HTML tag in the container
3. You would then have to add a ‘tag name‘ and select ‘Custom HTML Tag‘ type
4. Go to the WebEngage Dashboard » Settings »  widget integration tab –  here you would find the ‘Widget integration code for Tag Managers‘ (This is different from the default WebEngage Integration Code). Copy it and paste it into the “HTML” window.
5. You would then have to add a rule in the GTM that would enable the regulation of the display of WebEngage widget.
6. Next, you would have to save the newly created tag and publish it.

There are few parameters for cookie based targeting in WebEngage.

1. Domain of the existing cookie should match
2. Make sure the path of the cookie matches the page url path
3. The cookie should not be http. If the cookie is marked as “HttpOnly”, you’ll see a tick mark beside it. HttpOnly cookies can’t be read through JavaScript.

In order to achieve your requirement, you could choose from Box, classic or modal layout of notification. These layouts allow embedding of rich HTML. Here, you could add the Facebook iframe integration code for the ‘like’ button.

1. You would have to go to the Facebook resource and get the code here . This enables one to embed a Facebook like button.
2. Put the facebook code for ‘like’ button in iframe with APP ID in the iframe.

Actual individual user responses (with at least one question answered) are considered in the usage limit. You can create a single question survey or a multi-question survey, the limit simply depends on number of people submitting the responses.

Yes, it is possible to add video in the notification.

You would need to use either classic layout or the box layout. You need to paste the video embed code in the rich text box of notification layouts.  You can then edit the HTML and embed the url code as shown in the illustration:

You would have to go to Feedback ‘Settings’ in your dashboard and go to the field named ‘Feedback tab alignment’. Here you can choose your desired alignment.

You can make use of scope feature in surveys. It is available in JavaScript API. By default, the scope of the response gets tied to user session and hence once a response is submitted it doesn’t appear again to the same visitor. By changing scope to blog post URL or postID, each visitor would be able to rate per blog post.

More about it is mentioned here

An example:  Show same survey to visitor everyday even if it has already been submitted

For your case, add this line in your JavaScript integration code and substitute the variables in CAPS –

_weq['webengage.survey.scope'] = {
  'scope' : _BLOG_POST_ID_
  'scopeType' : 'session',
  'surveyIds' : ["_ENTER_SURVEY_ID_"]
};

In order to track WebEngage Events with Google Tag Manager (GTM) with Universal or Classic Analytics Tag Type, you would have to implement the solution in two steps:

Step 1: Google Tag Manager (GTM) Configuration for WebEngage Event Tracking

1. First Create a new Tag inside your GTM dashboard.
2. Give an appropriate title (e.g. ‘GA-Events’) and then select tag type as ‘Google Analytics > Universal/Classic Analytics‘.
3. Copy the tracking-id from your Google Analytics account and then paste it in the Tracking ID
   field of your GTM.
4. Set ‘Track Type’ of your Tag to ‘Event’. Since we are using dataLayer API of GTM, you will need to add appropriate macros for all the parameters. Refer the below image for the same.

   WebEngage Events GTM Tag

5. For Non-Interaction Hit you might have to add a dataLayer Macro. See the image below.

   Create nonInteraction dataLayer macro

6. Now, go to the ‘Firing Rules‘ section and click on add to insert rule.
7. An edit rule window would open up. Give a suitable name for your rule and in the ‘Conditions‘ section add ‘event‘ condition with operation set to ‘equals‘ and values ‘WebEngage-Survey‘. Save to add the rule.
8. Then repeat step 5 and 6 for events ‘WebEngage-Notification‘ and ‘WebEngage-Feedback‘. Refer the following three images.

   Feedback Events Firing rule

   Survey Events Firing rule

   Notification Events Firing rule

Step 2: WebEngage Widget Integration Code Changes

1. Add the line _weq[‘webengage.ga.gtm’] = true; in the WebEngage widget integration code. This would let WebEngage Widget know that you are using Universal GA with GTM.
2. Optionally, if you want to track for a specific GA tracking-id when you have both classic and universal GA, add the line _weq[‘webengage.ga.trackerId’] = ‘UA-XX-XXXX'; in the widget integration code.
3. If you are using custom value for the GoogleAnalyticsObject instead of default value (viz. ‘ga’) then add the line _weq[‘GA.universalAnalyticsFunction’] = ‘myGA'; in the widget integration code.

Currently there is no way to disable the feedback tab just on the mobile-site and keeping it on your desktop site. However, you could use the following script to make sure you don’t show the feedback-tab on the mobile devices.

This not only checks UserAgent string but also the screen size (screenWidth below 480px).

WebEngage widget is initialized on the page load. All the custom and rule data, you may want to use, will be understood at this point. So WebEngage might not work seamlessly with web-apps using a Single Page Architecture (SPA).

Though WebEngage does not provide any configuration in the dashboard, there is a way to re-initialize the widget using WebEngage JS API. See the example below, which re-initializes widget on hashChange event. Also, code assumes that jQuery is there on the page.

NOTE : This code needs to be part of your WebEngage Integration code.

WebEngage widget integration code requests a JavaScript file webengage-min-v-4.0.js, which loads asynchronously. Everything after that gets triggered on DOMContentLoaded event (https://developer.mozilla.org/en-US/docs/Web/Events/DOMContentLoaded).

Also, in the WenEngage JS-API you can specify the delay for the Widget-Initialisation. http://docs.webengage.com/api/js-api-v-4.0.html#widget-settings

Since it loads and executes asynchronously, the WebEngage Widget does not affect the website’s performance in any way.

The WebEngage targeting engine enables you to target your on-site campaigns towards specific user segments.

The targeting rules are divided into 3 broad categories, as seen on the Targeting page as well:

1. Whom to show? (Traffic Segment Targeting)
2. When to show? (Event Trigger Targeting)
3. Where to show? (Session Level Targeting)

Listed below are all the targeting rules explained in detail:

Whom to show? (Traffic Segment Targeting)

Using WebEngage, build segments on clickstream information of users. You can use the clickstream data to create a segment of users and target them with specific messages.

These are the options within traffic segment targeting:

1. Devices: You can target your visitors on any device (computer, mobile, tablet), they use. You can choose to target them on all one any combination of devices suited best for your campaign.

2. Operating Systems / Platforms: This targeting rule provides you the option to pick and choose your users on different platforms viz. Windows, Linux, Macintosh, Android, iOS and more.

3. Browsers: You can also choose to display or not display your web messages created using WebEngage, based upon the browser your user is on. We help you target on almost all famous browsers out there like, Internet Explorer, Firefox, Google Chrome, Safari, Netscape and Opera.

4. Visitor Type: Choosing the visitor type gives you a flexibility to target either new or repeat visitors via WebEngage. You can left the option untouched if you want to target all.

5. Geographic Location: You can also target your users based upon the geography they are in. The conditions are usual, ‘any’ or ‘none’ of the selected geographies and WebEngage would display web messages based on the satisfying rule.

There are three levels of targeting provided under geographic location viz. country, state and city, each having the option to select more than one option to target.

6. Traffic source – referring sites: This targeting rule provides you with an option to target the visitors that come to your website through different sources. These sources can include all major search engines, social networking sites and also direct traffic. You can even define your source and target visitors according to them.

Where to show? (Session Level Targeting)

This category showcases all the options that can enable you to target a user who have expressed their intent in a certain way. It may mean they could have visited some pages, or have viewed more than a certain amount of products in a session, or have certain cookies planted in their browser and so on and so forth.

This is how the Session Level Targeting rules look like, when collapsed:

1. Page URL targeting: You can specify on which page URL(s), the notification/survey to be displayed. You can add multiple page URLs as well as page URL patterns in regular expression format. You can also specify either inclusion or exclusion using “Group condition”.

Note:

• If you are using “equals to” or “starts with” as the operator in the drop-down, make sure that you specify that each page URL starts with either http:// or https://
• If you have specified homepage of your website, make sure you add two URL(s) – one with trailing slash in the end (e.g. httpL//www.mysite.com/) and other without (http://www.mysite.com).
• If you are specifying an exclusion rule with multiple page URL conditions, make sure you select group condition as “ALL Rules must satisfy”.

2. WYSIWYT (What You See Is What You Target): Through WYSIWYT, you can build dynamic rules without having to need their developers for any kind of data integration.

You can read in detail about it here: http://blog.webengage.com/2014/11/14/wysiwyt-what-you-see-is-what-you-target/

3. Number of page(s) viewed by a visitor in a session: Allows you to show a notification / survey to a visitor after (s)he has viewed pages in the current browser session reaches or exceeds the specified limit.

4. Cookie(s): For specified cookies, you can choose the survey or notification to appear only on those pages, on which the cookie related rules are met. You can add multiple conditions on same or different cookies. While doing so, you can either opt the group condition as ALL rules (all specified cookie related conditions) or ANY rule (any one of the cookie related conditions) to satisfy.

Note: Cookies with “HttpOnly” flag set, can not be used for targeting. They are inaccessible through JavaScript.

5. Custom Rules: Through custom rules, WebEngage lets you create rules on the basis of the data you choose to share with it. One can create complex business rules such as showing a survey to users who are signing in after 60 days, displaying an offer to a repeat visitor who abandoned the cart in last visit.

You can refer to out blog post: Custom Targeting to know more about them.

When to show? (Event Trigger Targeting)

As the name suggests, this capability of WebEngage is based on top of understanding the events that happen on your website. These events are the occurrences on your website either caused by an user’s actions or otherwise. They can be the user ‘on a particular page’, ‘searches for a product’, ‘scrolls x% of the page’, ‘tries to leave the page’ and many more.

WebEngage keeps a track of all these and more events on the website and enables you to target your visitors based on such events.

1. Leave Intent Targeting: Through Leave Intent Targeting, the cursor movement of a visitor is tracked and you can target them with relevant messages just when they try to leave the page.

2. Time delay on a page: Time spent by any visitor on a particular page is also a tracked event and you can choose to display your message after the passage of a particular time. For example, if you enter 5 seconds in the rule below, your message will be displayed only after the visitor has been on your page for 5 seconds.

3. Total time spent on your site by a visitor: The total time spent on your website in a session is also an event pre-defined for WebEngage and you can choose to target the visitors based on it.

4. Time of day: If you want to display certain messages only during a particular time period of the day, you can define that via this targeting rule. It also provides you the option to define the time according to your or the visitor’s timezone for better relevance.

5. Scroll: Page scroll percentage is automatically calculated by WebEngage and you can target your messaging for visitors based upon the percentage of your page they have scrolled.

6. Custom Events: The above mentioned events are the default events captured by WebEngage and you can directly target your visitors based on them. But events are not limited only on them. Custom events gives you the liberty to define events exclusive to your website and target users based on the occurrences, non-occurrence or conditional occurrence of such events.

WebEngage SDK’s allow you to track custom events and user logins/attributes. Which you can use later for user-segments analytics and even for targeting engagements. Its a very powerful way of knowing and selecting your audience for engagement.

If you are using GTM on your web-site for third-party integration and custom event tracking with GA and other third-parties. And if you want start tracking this information with WebEngage, it is possible by adding custom tag in your GTM container and and invoking it with the triggers configured for these custom events in GTM.

GTM ⇨ TAG – TIRGGERS – VARIABLES

Tag holds the content that needs to go onto HTML page mark-up.

Trigger helps in deciding when a tag needs to be invoked.

Variables are reusable dynamic values in GTM, they could be global variables or JavaScript code snippets. Google also provides bunch of variables by default and also lets you create
dataLayer and custom variables.

Generic tag to log custom GTM events to WebEngage (whatever that is passed in the custom-event is captured as event attributes in the webengage.track) –

Sample screenshot of GTM tag for tracking events with WebEngage –

Invoking Tag on Triggers defined in GTM –

Code snippet shared above is very generic, if you have a specific use case and want to customize the above code to suit your need, we will assist you. Get in touch.

Of all the data that WebEngage gleans for your business, Acquisition Source is one of the most important factors when it comes to defining segments based on them. Google Analytics defines Acquisition Source as the source through your user finds your website or mobile app.

Keeping in mind the standardisation and ease of use, almost all the sources active by default in the WebEngage dashboard follow the same convention as Google Analytics. All of these channels can be selected as the qualifying criteria for making a segment individually or in combination with other acquisition channels. A combination of 2 or more acquisition channels gives you a union of traffic acquired from both the channels.

As of now, WebEngage attributes users with First Click Attribution Model when creating segments.

The default channels of acquisition which can be used for segmentation through our dashboard are:

1. Campaign
2. Paid Search
3. Organic Search
4. Social
5. Referral
6. Email
7. Display
8. Direct

1. Segmentation based on Campaign Parameters

Campaign is a name given to your online marketing efforts used for sending traffic to your property. A campaign is further identified via parameters passed along with your landing page url. WebEngage allows you to create a segment based on these parameters. These parameters are passed as name-value pair defined by UTM tags.

UTM tags or parameters help Google Analytics attribute the source of traffic to the website. For example, consider you are running a marketing campaign to increase signups for your business and the landing page (www.mysite.com/signup) gets traffic through different channels such as ppc ads, email and social media.

In this scenario, UTM tags can be used to attribute traffic volume through each specific source. Sample utm tagged url as shown below –

http://mysite.com/signup?
utm_source=facebook&
utm_medium=cpm&
utm_campaign=revisedpricing

where,

source is ‘from where you are getting users to your lp’ such as facebook, google, newsletter
medium is ‘how you are getting users to your lp’ such as email, cpc, cpm etc.
campaign is ‘from which marketing campaign you are getting users to your lp’ such as revisedpricing etc.

There’s another parameter called ‘utm_term‘, which is an optional parameter used to identify the keywords in your paid campaign. WebEngage allows you to create a segment out of these terms as well.

Adwords provides a feature called ‘auto tagging’ that enables data to be pushed from adwords to analytics. If you enable ‘auto tagging’ in adwords, a parameter named GCLID is appended on-click to the landing page urls. WebEngage allows you to create segment from inclusion or exclusion a list of GCLIDs.

While creating segments using WebEngage, you can use Campaign parameters such as campaign name, source, medium, term and GCLID to define your segment.

Read more about Campaign Parameters on the Google Analytics Knowledge Base.

2. Segmentation based on Paid Search

A paid search campaign has two defining parameters, search query and search term. WebEngage lets you create segments on basis of both of these parameters.

Both these parameters have operators to further drill down on those parameters. The operators available with WebEngage currently are:

When both the parameters are used in combination, the segment derived is an intersection of the two.

3. Segmentation based on Organic Search Terms

Google encrypts organic search terms and prevents access to organic keyword referral data. However, WebEngage allows you to create segments based on those keywords that are shared by search engines.

4. Segmentation based on Social Media Channels

You can create a segment of your users acquired through the social media channels such as Facebook, LinkedIn, Pinterest, Twitter, and others. You can further drill down a level to create segments of users acquired through a union of a few social channels or the opposite with the help of operators, illustrated below.

5. Segmentation based on Referral Traffic Source

Selecting ‘referral’ as the acquisition source lets you create a segment of all the users acquired through referral links. If you want to create a segment of users acquired through a particular link or a set of links, you can also do that and much more by using the operators with referral links.

6. Segmentation based on Acquisition through Email

WebEngage understands when a user is acquired through an email. This is achieved through the reading of UTM tags appended to the URL. In case of absence UTM tags, the acquisition source attributed is ‘Direct’.

It is recommended to use ‘Campaign’ as the First Acquisition Source when using referral url with utm tags.

Selecting Email as the First Acquisition Source provides you a segment of your users acquired through emails.

7. Segmentation based on Acquisition through Display Ads

As the name suggests, selecting Display as the acquisition channels select all your users acquired through your display ads, into one segment. All the users acquired through a Banner, CPM or any display ad are attributed to ‘Display’ by default.

It is recommended to use ‘Campaign’ as the First Acquisition Source when using referral url with utm tags.

8. Segmentation based on Direct Traffic

Direct traffic corresponds to all the users who come to your website or mobile app through a direct URL or a URL where referrer can’t be clearly identified. Scenarios where user can be termed as Direct would be: link clicks within pdf, within mobile apps, link clicks from https to http sites etc.

Selecting Direct as the acquisition channel, WebEngage creates a segment of traffic acquired through the Direct Channel.

For enterprise pricing please contact at: 1 (408) 890-2392 (US) or +91 (22) 67259495 (India). To check out features, pleas take a look at our pricing section.

In case you are hitting your monthly usage limits, you can easily upgrade to a higher plan. System sends out alert messages to you when you hit 50%, 80% and 95% of your limits allowing you to upgrade your account. Each product (Feedback, Survey and Notification) has its own monthly limit based on the subscribed plan. In case you skip upgrading, the product that reached its monthly usage limit will stop functioning for rest of the billing month. Limits reset back to zero beginning your monthly cycle.

There is a limit on maximum number of active notifications you can run at a time. If you wish to activate a new notification, you need to de-activate the notifications that are not in use. The System allows you to create as many notifications per month. The limits are specified on the pricing features page.

Your account is in the Basic plan, which has a 100k/month impression limit on Notification views. You exceeded that for the current cycle. See this link to get an overview of limits – http://webengage.com/pricing. Your limits would be reset to zero when the billing is renewed or if you upgrade to a higher plan.

Yes, it is possible to target visitors coming from a particular geo location and show them a notification on your website. The closest the system provides targeting is at city level. Geo location is identified based on visitor’s IP. For more information about targeting please refer to – http://webengage.com/notification#targeting

Sure, it is possible. While targeting surveys/notifications, you need to choose “Traffic Source” based targeting and select “Social Media” as the channel. When a visitor clicks on a link of your website from one of these social network site Twitter, Facebook, Pinterest etc. then they get to see the configured notification/survey. Do note that, if the page on these websites that contain your link is accessed through HTTPS protocol then your URL should use HTTPS protocol for this targeting to work.