mdTransit Instrumentation Overview

Summary

Image requests to the reporting server are used to track site activity. These images are referred to as crumbs and take the format /image/mdwtc-${PLACEMENT_CODE}-OBJECT_TYPE-${OBJECT_ID}?other=data&that=you&want=to&track=counts

v1 Placement

Site Traffic Crumb

One crumb with an OBJECT_TYPE of MDTRANSIT_SITE and OBJECT_ID of the template property ID in template manager should appear on every page of the site. If the referring hostname is not the same as the current host name (or nocache.current hostname) a referer_domain key/value pair should be added to the query string of the image. http://rpt.mdtransit.morris.com/images/mdwtc-${PLACEMENT_CODE}-MDTRANSIT_SITE-${SITE_ID}.gif?referer_domain=domain.com

Refer to table in appendix for placement code values.

Dealer Search Crumb

On first page of results (and only the first page) for any search for dealers a crumb should appear with an OBJECT_TYPE of MDTRANSIT_DEALER_SEARCH and OBJECT_ID of the template property ID in template manager. The query string of the image should contain information about the make searched for (make=), the zipcode searched in (zipcode=) and the type of dealer (type=). Types are freeform and what appears in the query string will appear on the reports. http://rpt.mdtransit.morris.com/images/mdwtc-${PLACEMENT_CODE}-MDTRANSIT_DEALER_SEARCH-${SITE_ID}.gif?make=TOYOTA&zipcode=30909&type=(NEW/USED/NEW+AND+USED)

Dealer Details Crumb

Any time a dealer's dealership info is displayed (dealer search returns as a primary example) a crumb should appear with an OBJECT_TYPE of MDTRANSIT_DEALER_DETAILS and OBJECT_ID of the customer ID for that dealer in the classifieds system. http://rpt.mdtransit.morris.com/images/mdwtc-${PLACEMENT_CODE}-MDTRANSIT_DEALER_DETAILS-${CUSTOMER_ID}.gif

Auto Search Crumb

On first page of results (and only the first page) for any search for autos a crumb should appear with an OBJECT_TYPE of MDTRANSIT_II_INVENTORY_SEARCH and OBJECT_ID of the template property ID in template manager. The query string of the image should contain information about the makes searched for (broken out using make.#= syntax (digits are currently configured to search from 1 to 10)), the canoncial models (i.e. F-Series for ford, not F-150, F-250, F-350) searched for (broken out in the same way as the makes), the zipcode searched in (zipcode=) and the type of auto (type=). Types, makes and zipcodes are freeform and what appears in the query string will appear on the reports (only canonical model values will be detailed below the makes however, other values will be hidden - canonical values can be found in the classifieds codesets category MDTRANSIT, key of MODEL). http://rpt.mdtransit.morris.com/images/mdwtc-${PLACEMENT_CODE}-MDTRANSIT_II_INVENTORY_SEARCH-${SITE_ID}.gif?make.1=TOYOTA&model.1=Camry&zipcode=30909&type=(NEW/USED/NEW+AND+USED)

The MDTRANSIT codesets category must contain an updated list of makes/models and model aliases for this tracking to work.

Auto Display Crumb

Any time auto info is displayed (inventory search returns as a primary example, detail pages as a second) a crumb should appear with an OBJECT_TYPE of MDTRANSIT_AD and OBJECT_ID of the customer ID for that dealer in the classifieds system. The query string of the add should send the ad id (ad_id=), make (make=) and model (model=). These are all free form and what appears in the query string is what will appear in the reports. Ad ID is not currently stored or displayed. http://rpt.mdtransit.morris.com/images/mdwtc-${PLACEMENT_CODE}-MDTRANSIT_AD-${CUSTOMER_ID}.gif?ad_id=12345&make=TOYOTA&model=CAMRY

Dealer Referral Crumb

When linking to a dealer's website, an intermediate page of some sort needs to load that contains a crumb with an OBJECT_TYPE of MDTRANSIT_DEALER_URL and OBJECT_ID of the customer ID for that dealer in the classifieds system. http://rpt.mdtransit.morris.com/images/mdwtc-${PLACEMENT_CODE}-MDTRANSIT_DEALER_URL-${CUSTOMER_ID}.gif

Data Collection Overview

Below is a description of how reporting data is collected and processed. Each step represents a potential point of failure for the mdTransit reporting system. Items in this text represent unrecoverable failure points.

  1. User requests mdTransit template.
  2. Template contains appropriate reporting crumbs.
  3. User's browser requests crumb images from reporting collection server.
  4. Crumb request is rewritten to a clear gif by a Rewrite rule in the apache configuration.
  5. Request for crumb is logged in the reporting collection server's access_log in CrumbLog format.
  6. Access log is archived after analog processing.
  7. Archived data file is moved to processing area.
  8. Archived data file is parsed and converted to a loadable format.
  9. Loadable format data file is sorted to help efficiency.
  10. Loadable format data file is loaded into the database.

Appendix A - Placement Codes

CODE PAGE
100 Vehicle Results
101 Vehicle Details
102 Advanced Search
103 No Vehicle Results
104 Full Image
105 Quick Search/Index
106 Specification Search
107 Dealer Search
108 Specification Results
109 Dealer Search Results
110 Comparison
111 Comparsion Step 3
112 My Selected Vehicles
113 Comparison Step 2
114 Calculator
115 Vehicle Quote Thankyou
116 Research & Compare
117 Finance Index
118 No Dealer Results
119 Email Notification Form
120 Quick Quote Form
121 Email Notification Thankyou
122 Quick Quote Thankyou
123 Parts Request
124 Service Appointment
125 Clipboard
126 Email ad to friend
127 Email ad to friend thank you
128 Printer Friendly Ad details

Appendix B - Data Storage Description

Site Traffic Crumbs

LOG_OBJECTS
    OBJECT_ID = PROPERTY_ID from Template Manager
    OBJECT_TYPE = MDTRANSIT_SITE

LOG_OBJECT_ATTRIBUTE (keys)
    DATE
        DATE HIT_COUNT

        PLACEMENT_CODE
            PLACEMENT_CODE HIT_COUNT

            REFERER_DOMAIN
                REFERER_DOMAIN HIT_COUNT

Dealer Search Crumb

==================================================
| Logging Breakout
==================================================
LOG_OBJECTS
    OBJECT_ID = PROPERTY_ID 
    OBJECT_TYPE = MDTRANSIT_DEALER_SEARCH

LOG_OBJECT_ATTRIBUTE
    DATE
        DATE HIT_COUNT
            MAKE
                MAKE HIT_COUNT
            ZIP
                ZIP HIT_COUNT
            TYPE
                TYPE HIT_COUNT


Dealer Details Crumb

==================================================
| Logging Breakout
==================================================
LOG_OBJECTS
    OBJECT_ID = CUSTOMER_ID
    OBJECT_TYPE = MDTRANSIT_CUSTOMER_DETAILS

LOG_OBJECT_ATTRIBUTE (keys)
    DATE
        DATE HIT_COUNT

Auto Search Crumb

==================================================
| Logging Breakout
==================================================
LOG_OBJECTS
    OBJECT_ID = PROPERTY_ID 
    OBJECT_TYPE = MDTRANSIT_II_INVENTORY_SEARCH

LOG_OBJECT_ATTRIBUTE
    DATE
        DATE HIT_COUNT
            TYPE
                TYPE HIT_COUNT
            ZIP
                ZIP HIT_COUNT
                MAKE
                    MAKE HIT_COUNT
                MODEL
                    MODEL HIT_COUNT

Auto Display Crumb

==================================================
| Logging Breakout
==================================================
LOG_OBJECTS
    OBJECT_ID = AD_CUSTOMER_ID 
    OBJECT_TYPE = MDTRANSIT_AD

LOG_OBJECT_ATTRIBUTE
    DATE
        DATE HIT_COUNT
        PLACEMENT_CODE
            PLACEMENT_CODE HIT_COUNT
            MAKE
                MAKE HIT_COUNT
            MODEL
                MODEL HIT_COUNT

Dealer Referral Crumb

==================================================
| Logging Breakout
==================================================
LOG_OBJECTS
    OBJECT_ID = CUSTOMER_ID
    OBJECT_TYPE = MDTRANSIT_DEALER_URL

LOG_OBJECT_ATTRIBUTE (keys)
    DATE
        DATE HIT_COUNT