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).
|at||action tag ID (at 5 = Shop Action 5, at 9 = Shop Action 9)|
|c_a1…c_a50||extra Conversion Event tag attributes for Explore|
|cat||conversion action type (1=initiated event, 2=completed event)|
|ccid||conversion event category ID|
|cg||category for pages or products (used for CDF file)|
|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|
|cx1...cx15||extra custom fields for conversion events|
|e_a1...e_a50||extra Element Tag attributes for Explore|
|ec||character set encoding|
|fo||not sure (form related)|
|je||Boolean answering “is Java enabled?”|
|nm||name of link|
|np0…15||technical browser properties|
|o_a1…o_a50||extra Order Tag attributes for Explore|
|or11||extra order attributes|
|pc||Boolean answering “is this a page view?”|
|pflg||product or page element? (product = 1, page = 0)|
|pi||Page ID (page name)|
|pr_a1…pr_a50||extra Product View tag attributes for Explore|
|pv_a1…pv_a50||extra Page View tag attributes for Explore|
|rg1…rg50||extra Registration Tag attributes for Explore|
|rnd||Random # (used for cache-busting)|
|s_a1…s_a50||extra Shop Tag attributes for Explore|
|se||search start page|
|sr||# of search results|
|st||Session start time|
|sx11||extra custom shop fields|
|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|
|ul||Destination URL. The URL of the page.|
|vn1||Coremetrics library version|
|vn2||Coremetrics library version #2|
17 thoughts on “Master List of Coremetrics Query Strings”
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
Thank you Oscar! I updated the post.
This is very useful!
I believe "nm" is the name of the link. The name attribute is used to identify a link destination, or anchor, on a page. http://reference.sitepoint.com/html/a/name
Thanks, updating the post!
great reference, just come in handy and saved my life !
That's what I like to hear! Thanks for the note.
Many thanks for this post. I have been digging around for just this information and it is a useful reference.
Thanks, Rod. I hope it helped save you some time. And nice site!
Any of those parameters tell us which traffic source Coremetrics gets? Something similar co GA utmcc.
Hi Marcelo, you can check the "ul" parameter and the "rf" parameter. On the landing page, the "ul" parameter may hold a value like http://www.yoursite.com/?cm_mmc=A-_-B-_-C, 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.
what is the diff betweek cm?ti-8 and cm?=15 , am getting only cm?ti=8 on debugging the buttons clicks
Still so relevant. Thanks for the cheat sheet.
I know this is a REALLY old thread, but I still use it and appreciate it. I just found out that "ha1" is related to the Shop tags (5/9). it is used to determine if the tag is unique or not. If all attributes of the tag are the same, the "ha1" makes the determination that it is a duplicate cart item and does not add it to the data. If anything is different (like size, color, etc) in the tag, it uses this field to determine it may be a 2nd instance of the same item, but there is something different about it and records both Shop tags.
Also, just noticed, your explanation of "ul" with marketing tags, you are short 1 parameter. "http://www.yoursite.com/?cm_mmc=A-_-B-_-C" should be "http://www.yoursite.com/?cm_mmc=A-_-B-_-C-_-D" without the last parameter, the marketing tag will fail. There is also an old version of the marketing tag where you fire each part separately: "cm_ven=xxx&cm_cat=xxx&cm_pla=xxx&cm_ite=xxx" in this instance, if afield is left off (particularly cm_pla) the interface will replace the missing field with a "-1"
Hi John, thank you for the comment! I haven't used this tool in years, so I'm happily surprised to hear the article is still relevant 😀
Thanks also for the information about ha1 and cm_mmc.