Master List of Coremetrics Query Strings

This is a followup to the post on debugging Coremetrics without TagBar.  In that post we walked through how to access and understand the query strings that get sent to Coremetrics servers while a user clicks around a website.   These query strings populate the tags that get set on each page to identify user actions.  Checking these strings is a technique that can help troubleshoot and debug implementations of any web analytics tool, though it’s most useful for Coremetrics.

Below is the master list of these query strings for reference.

There are still a few unknowns so let me know in the comments if you can identify them (and thanks to Shawn and Oscar for some contributions to this list).


Parameter Description
ac not sure
at action tag ID (at 5 = Shop Action 5, at 9 = Shop Action 9)
bp base price
c_a1…c_a50 extra Conversion Event tag attributes for Explore
cat conversion action type (1=initiated event, 2=completed event)
cc currency code
ccid conversion event category ID
cd registration code
cg category for pages or products (used for CDF file)
ci Client ID
cid conversion event ID
cjen JSF parameter enabled flag
cjsid JSF session ID
cjuid JSF user ID
cjvf JSF valid flag
cm_mmca1…cm_mmca50 extra marketing program tags for Explore
cm_re real estate tracking
cm_sp site promotions tracking
cpt conversion points for conversion events
ct billing city
cx1…cx15 extra custom fields for conversion events
cy billing country
e_a1…e_a50 extra Element Tag attributes for Explore
ec character set encoding
ecat element category
eid element ID
em email address
fi form inputs
fo not sure (form related)
ha1 not sure
hr href
je Boolean answering “is Java enabled?”
jv Javascript version
lp landing page
nm name of link
np0…15 technical browser properties
o_a1…o_a50 extra Order Tag attributes for Explore
on order number
or11 extra order attributes
osk order SKU
pc Boolean answering “is this a page view?”
pd Color depth
pflg product or page element? (product = 1, page = 0)
pi Page ID (page name)
pm product name
pr product number
pr_a1…pr_a50 extra Product View tag attributes for Explore
pv_a1…pv_a50 extra Page View tag attributes for Explore
qt quantity
rf referring URL
rg1…rg50 extra Registration Tag attributes for Explore
rnd Random # (used for cache-busting)
rs not sure
s_a1…s_a50 extra Shop Tag attributes for Explore
sa billing state
se search start page
sg shipping
sh Screen height
sr # of search results
st Session start time
sw Screen width
sx11 extra custom shop fields
ti not sure
tid Tag ID/type:
tid 1 = page view tag
tid 2 = registration tag
tid 3 = order info tag
tid 4 = shop tag (+action 5 =shopping cart tag, +action 9 = order receipt tag)
tid 5 = product view tag
tid 6 = technical properties tag
tid 7 = custom details tag
tid 8 = link click tag (for real estate/ site promotions click tracking)
tid 9 = link impressions tag (for cm_sp impression tagging)
tid 10 = form action tag (auto-generated for forms)
tid 14 = conversion event tag
tid 15 = element tag
tid 404 = error tag
tr total revenue
tz Time zone
ul Destination URL. The URL of the page.
vn1 Coremetrics library version
vn2 Coremetrics library version #2
zp not sure


  1. Great, this information is very helpful, I have one of the Not sure answers (lp:landing page) is usually the first page of each session.

    Thanks again Ana for sharing this

    1. Hi Marcelo, you can check the “ul” parameter and the “rf” parameter. On the landing page, the “ul” parameter may hold a value like, in which case Coremetrics takes that cm_mmc value and uses it to define the traffic source.

      For visits coming in from direct, organic search, etc, there won’t be a cm_mmc value. so in those cases Coremetrics will check the “rf” (referring site) paramater to see where the visit came from. Either way it all gets processed on Coremetrics’ servers so there’s no straightforward way to check how it’s going to show up in the reports.

Leave a Reply

Your email address will not be published.