html - When to track an interaction on a page as a page impression, when as an event, etc.? -

The normal track of page impression is quite clear and just: put the code at the end of the page.

But with increasing use of in-page changes in layout and content, when it is ok to log in to a new page impression and when will an event be considered as only a record?

I understand that page impressions have a strong relation for ad impressions (at least in what I believe with my colleagues around).

When I have a page that reveals completely new content to the user without reloading (everything is already pre-loaded in terms of performance), is it a Can the page effect be considered? If so, then it will not be related to PI / A mathematics and I am feeling disturbed.

Should I be properly named as that click program, but the total is not counting the page impression?

Some user interactions subscribe to simple things like activating a feature for just a few things (for example a thread, in-app bookmark). I will not call them a new page impression, but an event.

Page impressions can be overturned but it can still be used as a unit of measurement. The number of unique users is equally important. This question is not about PI versus. Unique User / Client / Anyone, but strictly about how to control such incidents.

An interesting problem; The difficulty of drawing a line between AJAX's age travel (or impression) makes it difficult. As a simple rule of thumb, the number of impressions counted - the number of ad impressions (some circular but true)

In my experience, the method of recording impressions depends on the data that is for the data:

1. While gathering data for advertising agencies (such as For the expected number of impressions for some CPM ad servers), you should log the impression per per load load per page (load or refresh per page) how many times it will refresh your ads - later on the pageRegardless of dynamic change

2. If you are displaying ads on your pages and working as an agency (you are independent rule); When there is considerable change in content as a result of user interaction, it is acceptable to count an impression. I'll give an example - refreshes Microsoft's late valuable ads (hence the count of impressions) each time the map was pulled by the user (moved)

Flip between the pictures in (where the images fill most of your screens) However, Facebook updates despite pages actually changing. Method 1 is currently the industry standard, only use the most cutting edge Ajax sites 2. It has said that, my website effectively uses 2, though Applicable 1. I have a Lightbox IFrame that fits to display new content (though only on web page can be embedded inline with other content); Which means that the user never leaves the page, while in the iframes, they generate additional impressions with the implementation of 1 on the page - in this way I can cite a higher impression that if I use Ajax directly on the original page with the implementation of 1 I want to use. Technically, 1 self-recognized device such as Google Analytics (though 2 can easily be done in this case) and if guarantees to refresh ads within the IFrame (beware with ad server's TS and CS) - Many people are showing more than a certain number of overlaying / per browser view).