ContentViews

Today's websites have content from various sources, not only from your own company, but third-party content as well. DéjàClick™ ContentViews sorts this content, so you can create separate reports and notify the responsible owner of the content when it is down or in error. This helps you troubleshoot performance issues within your site without having to deal with poorly performing components from external sources.

ContentViews automatically captures all site content found in your transactions, allowing you to:

• Easily monitor the components independent of each other.

• Select and prioritize whether or not to receive notifications based on ContentView errors.

• Create ContentViews-specific reports with graphs and charts.

Before you start, you must first decide how you want to partition the content contained in your transaction. For example, you need only URLs with your web site's domain in one ContentView. In another, you need specific Content Delivery Network (CDN) URLs. In the third, you need other third-party URLs.

After you decided how to classify your content, you are ready to add and configure different ContentViews.

The ways to configure ContentViews are:

1. From the Properties sidebar.

2. By using the Validation menu.

In Plan-Based accounts, ContentViews can be included as an additional feature for most DéjàClick plans. Once added to an existing plan, you can configure ContentViews as described in this guide.

In Usage-Based accounts, ContentViews consume measurement credits at a rate of 1/4 usage credit per action in your AlertSite account. If no matching content is reported by the ContentView, no usage credits are charged to your account.

For this example, we recorded 3 actions on amazon.com using DéjàClick and played it back on the desktop. After the replay, we are ready to add ContentViews.

Click the Properties tab in the DéjàClick sidebar. Locate ContentViews in the list and expand it.

In our example, we will set up 3 ContentViews, one for the amazon.com domain, one for the ad.doubleclick.net domain, and one for all other pages that do not contain amazon.com or ad.doubleclick.net. To accomplish this, we will:

1. Create a ContentView with the URL amazon.com, which we will call Amazon Only.

2. Create a ContentView with the URL ad.doubleclick.net, which we will call Doubleclick Only.

3. Create another ContentView that excludes any members of the other two ContentViews, that is, containing neither amazon.com nor ad.doubleclick.net, but some other third-party content, and we will call it Neither Amazon nor Doubleclick.

Amazon only

Doubleclick only

Neither Amazon nor Doubleclick

Next, create the ContentView Neither Amazon nor Doubleclick that contains all Domains in the transaction other than amazon.com and ad.doubleclick.net:

• Similarly to the first and second ContentViews, add the third one and enter Neither Amazon nor Doubleclick in the Name field.

• Click .

• In the Add ContentView Component dialog, click New.

• In the Add Component dialog, set the following options:

  • Select ContentView from the Type drop-down list.

  • Select Amazon Only from the Parameters drop-down list.

  • Select the Exclude from ContentView.

  • Click OK.

    

• Repeat the above steps to add Doubleclick Only to Neither Amazon nor Doubleclick. Here is what the Add ContentView Component dialog looks like:

  

  Click the image to enlarge it.

• Click OK in the Add ContentView Component dialog.

• Click OK in the Add ContentView dialog.

Now, the ContentViews property sidebar shows the three ContentViews:

Exclusionary ContentView

If you need a ContentView for specific third-party objects, you can create a regular expression to exclude any objects, the URLs of which contain a specific string. For a set of strings, you can create a regular expression by using logical notation.

For example, you want a ContentView for objects that do not contain the string amazon anywhere in the URL. In the Add Component dialog:

• Enter amazon in the URL field.

• Select the Regular Expression match type.

• Select the Exclude from ContentView check box.

• Click OK.

In case you need a ContentView for objects without amazon, doubleclick, or mdn in their URLs, in the Add Component dialog:

• Enter amazon|doubleclick|mdn in the URL field (where | is the logical or or a vertical bar).

• Select the Regular Expression match type.

• Select the Exclude from ContentView check box.

• Click OK.

To assure exclusion of all objects with any of the strings in a ContentView, the strings must be separated by |, but not just listed or excluded separately.

You can add ContentViews while recording or while replaying the recorded script at the Action or Event levels.

While recording a new transaction:

• Click and navigate to your starting page.

• At any time during the recording, when DéjàClick pauses for the next step, appears on the toolbar. Click the drop-down arrow next to the icon and select Add ContentViews.

• Follow the steps to add your ContentView as described above.

While replaying the recorded transaction:

• Click the drop-down arrow next to and select Replay Next Action or Replay Next Event.

• Click to step through the transaction.

• When the replay pauses, appears on the toolbar. Click the drop-down arrow next to the icon and select Add ContentViews.

• Follow the steps to add your ContentView as described above.

Along with partitioning on URLs, ContentViews, and predefined lists, the Add ContentView dialog has 3 optional attributes you can use in addition to the URLs or Domains to separate URLs by:

Content Types

Content TypesContent Types

• Select the Filter on Content Type check box.

• In the list, select types that you do not want to include in the ContentView and click .

• If you want to add a Content type to the list, click , enter a new Content Type, and click OK.

Content Length

Content LengthContent Length

• Minimum size – Minimum size of pages in bytes.

• Maximum size – Maximum size of pages in bytes.

Scope

ScopeScope

Click to the left of an action or event to be excluded from the ContentView.

You can also configure the ContentView to proceed to the next action or event in case of an error. To do this, select the check box under Replay Options. Enable this option, if the ContentView does not contain the critical path of the transaction.

After you have recorded and verified a transaction and configured ContentViews, upload the script to AlertSite. You will be redirected to the Manage Transaction screen, where you can make more configuration changes, for example, to the monitoring type, timeouts, locations, and so on. You can also configure there Fullpage Options, Capture Options, ContentViews, and Transaction Description.

AlertSite UXM

AlertSite 1.0

AlertSite UXM

To configure ContentView alerts in AlertSite UXM, open the monitor settings, select the Alerts tab and then select ContentViews Alerts. The options are:

• Alerts Enabled – If selected, sends notifications in case of an error in the listed ContentViews.

• Inherit Global Errors – If selected, reports global errors not associated with a ContentView URL. The following status codes apply to the option:

  Code	Description
  80	Browser event timeout encountered.
  81	Maximum transaction time was exceeded.
  90	Unexpected processing exception occurred.
  92	Maximum number of skipped events exceeded.
  93	Missing instruction for dialog prompt.
  96	Unable to parse transaction XML.
  97	Target page element was not found.
  7202	Fullpage Timeout.

Click the image to enlarge it.

AlertSite 1.0

To configure ContentView alerts in AlertSite 1.0, go to Configure > Transactions and click your monitor with ContentViews. In the ContentView Settings section, configure the following options:

• Notify – If selected, sends notifications in case of an error in the listed ContentViews.

• Inherit Global Errors – If selected, reports global errors not associated with a ContentView URL. The following status codes apply to the option:

  Code	Description
  80	Browser event timeout encountered.
  81	Maximum transaction time was exceeded.
  90	Unexpected processing exception occurred.
  92	Maximum number of skipped events exceeded.
  93	Missing instruction for dialog prompt.
  96	Unable to parse transaction XML.
  97	Target page element was not found.
  7202	Fullpage Timeout.

Click the image to enlarge it.

The ContentView Settings section is not displayed if the transaction does not have any ContentViews.

By default, some global errors that occur in the transaction may affect individual ContentViews, but they do not affect the ContentView. That is why errors may be in the main transaction but not in the ContentView issue notifications. If you want a ContentView to inherit these errors from the main transaction, select the Inherit Global Errors check box for that ContentView. For example, if a fullpage timeout occurred on one step, you may want pass that error through to the ContentView setup for your domain.

To receive notifications for the main transaction, make sure the Alerting option (or Notify on Error in AlertSite 1.0) is enabled in monitor settings because the script may fail while the ContentViews may still be successful.

To control notifications, we recommend that you create a recipient group for all ContentViews, otherwise, all recipients in AlertSite will be notified on ContentView Errors.

To create a recipient group:

Now, when the pages with the amazon.com domain produce errors, only the Administrator, Operations, and Management recipients will be notified. If pages with ad.doubleclick.net in the domain name are in error, only the Marketing recipient will be alerted. And, when pages with any domains other than amazon.com or ad.doubleclick.net are in error, only Administrator and Operations will receive alerts.

After uploading the transaction to your account, it will take some time for the transaction to propagate out to your selected monitoring locations and begin gathering performance measurements. Allow 10-15 minutes past your monitoring interval before attempting to run a report.

You can produce graphs and charts based on the selected ContentViews.

• Performance Graphs (Availability, Response Time, etc.)

• Scatter Plots

• Report API for data extraction

The Detail and Notification Detail reports can be created for the entire transaction or for individual ContentViews. ContentViews are listed below the transaction name in the monitor list when you create these reports:

AlertSite UXM

AlertSite 1.0

AlertSite UXM

AlertSite 1.0

To illustrate the properties of ContentViews-partitioned reports, we have created a couple of reports for the Amazon Only and Doubleclick Only ContentViews.

A line of measurements has been expanded in each one. By expanding the sections and drilling down to the object level, you can see that the list of objects in Amazon Only contains only objects with amazon.com in the URL:

Click the image to enlarge it.

The objects in Doubleclick Only contain only objects with the ad.doubleclick.net domain:

Click the image to enlarge it.

The objects in Neither Amazon nor Doubleclick contain only objects that do not include the amazon.com or ad.doubleclick.net domains:

Click the image to enlarge it.

In this way, reports with relevance for particular groups or individuals can be created and scheduled, then distributed as needed.