framed pages...

[matters]

Is it possible to monitor the content of frames within an aspx page?

[webado]

Whatever pages you put in the frames need to have tracking code on them.

They need to be on the same domain as the frameset page, so there is tracking across domains.

[matters]

Thanks, though to avoid double counting I should set up a new project to track these right?

[webado]

What do you mean double counting?

The counter goes onto the page shown in the main frame. Not any of the additional frames you may have for a sidebar or a footer or whatever is constant for all pages.

[matters]

Perhaps its easier to see what I mean by looking one of the pages.

In my insurance page, users navigate to this page and within it is a frame within which the contents change depending on which insurance type they select. Since the main page is never reloaded but the frame contents are, I would like to see which insurance types are being looked at in the frame and how often.

I presume that since the main page isn't reloaded as such it won't be counted again?

[webado]

Your site isn't working. I got this error:

Server Error in '/' Application.
--------------------------------------------------------------------------------

Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>


Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>

The tracking code has got to go into the page being displayed in your frame. If it's not your page to add code to, too bad, you cannot track it.