Way to capture successful login only once per visit without using event serialization? | Community
Skip to main content
Archana_Singh
Archana_Singh
October 14, 2017
Solved

Way to capture successful login only once per visit without using event serialization?

  • October 14, 2017
  • 3 replies
  • 2902 views

On the landing page(after successful login), there is a data element 'login' which gets set to 'true' and stay true as long as the member is logged in. I want to fire an event only once when the user comes to landing page for the 1st time (not after page refresh or user coming back again to the same page in the visit). Is there a way to set a condition for that so that the event fores only once so that we don't need enable serialization from siteCatalyst side? Can we write some logic or use rule conditions to do this?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Andrey_Osadchuk

Chose "Record once per visit" in the admin console while configuring the event (see Methods of Event Serialization)

3 replies

Andrey_Osadchuk
Andrey_OsadchukAccepted solution
Level 10
October 15, 2017

Chose "Record once per visit" in the admin console while configuring the event (see Methods of Event Serialization)

J
Jan_t8rpro
May 9, 2019

Hi Andrey,

I have question related to this. If i have page called "application start" and this receives 10 visits in a day. I then set event100 (which I have set to "Record once per Visit" ) when the the "application start" has loaded.

therefore a report with pageName "application start"  = 10 Visits

and a report with event 100 = 10

Is this correct?

The reason why I asking this questions is because this is not happening for me (i have less event count vs page visits) and I wanted to check the logic above is correct.

Thanks,

Jan

Andrey_Osadchuk
Andrey_Osadchuk
Level 10
May 9, 2019

Hi Jan,

Yes, it should be correct. Maybe the event100 is not always fired together with the mentioned pageName?

Terms & ConditionsAccessibility statement

Loading footer...