1. Home
  2. Users & Insights
  3. Why is there a mismatch between WebEngage notification views and GA page views for the same traffic segment?
  1. Home
  2. Campaign Management
  3. Web Notification
  4. Why is there a mismatch between WebEngage notification views and GA page views for the same traffic segment?

Why is there a mismatch between WebEngage notification views and GA page views for the same traffic segment?

There could be multiple reasons for it:

  1. Make sure the exact targeting rules defined in WebEngage have also been applied to GA.
  2. For user type targeting parameter, there could be little variation in the tagging a user as repeat or a new. It depends on session length as well as timing of the respective code integration.
  3. For geo-based targeting, the geo location is found out based on IP and it may vary.
  4. Notification once closed, clicked or exceeds its maximum view limit per visitor is not shown to the same visitor. However, GA will keep aggregating page views for the same visitor.

Was this article helpful?