Make Paid/Natural Search Keywords built in eVars for Classifications, etc.

markc44481791

12-02-2010

Make Search Keywords, for Natural & Paid, native built in system variables (at least eVars) so that we can Classify them for Segmentation, Pathing, Fall Outs, Path Finder, etc.

24 Comments (24 New)
24 Comments

wath360

16-11-2012

'Out of the box' variables such as custom link name and keywords cannot be classified.  Please make it possible for us to do this!

dberger

25-11-2012

I'd like to be able to classify Search keywords captured by the baked-in keyword reporting.

While Paid vs Natural is already a nice distinction, I'd like to be able to classify as Branded / Non-Branded (Current Workaround is a custom report, filtered with Brand Rules), as well as to identify targeted keywords

 

From a business perspective, I may have 300 targeted keywords and phrases for my SEO Manager to optimize for, and the ability to trend against the targets will help identify and measure her performance.

 

Why should we have to waste an eVar moving keywords captured by Search Detection in order to classify them?

Michael_Sky

28-11-2012

Hi David,

 

totally agree. Best solution would be to add "branded" and "non-branded" SEO to traffic sources. And configure brand regexp on administration interface for each report suite - like paid search.


Best,

 

Michael

keithmacd

04-12-2012

I suggest extending this request a bit.  There are a number of data points which are provided through SiteCat data pre-processing or report runtime filters which I'd love to be able to classify:

 

Search Keyword (e.g. Branded/Non-Branded, groups of similar terms within Non-Branded)

GeoSegmentation (e.g. Europe/Middle-East/Asia)

Referring Domains (e.g. Google [all google domains], Consumer Message Boards & Forums, Couponing Sites)

- it's worth noting that the functionality already exists -> the Referrer Type report is a classification of referring domains

Technology Reports (e.g. Browser Width > 1024px, Browsers High-Level [Firefox, Chrome, Safari, IE - all versions aggregated])

 

Currently, the work-around would be VISTA rules to copy those data points to variables, and then you'd set up classifications on those variables.  I'd prefer this be available out of the box.

dberger

04-12-2012

Keith:  Agree these are all good uses.

FWIW, VISTA Rules aren't the only option...  Can accomplish the same thing with some custom scripting, but I don't see the value in using uip the eVars in the first place.

keithmacd

04-12-2012

I've gone through the first 4 pages of search results for "classification" and found a few posts which all seem to be asking for the same or very similar things:

 

ID 8515

ID 8561

ID 6855

ID 216

ID 1638

 

Cross-posting to all of them to tie together the loose threads.

keithmacd

04-12-2012

I've gone through the first 4 pages of search results for "classification" and found a few posts which all seem to be asking for the same or very similar things:

 

ID 8515

ID 8561

ID 6855

ID 216

ID 1638

 

Cross-posting to all of them to tie together the loose threads.

keithmacd

04-12-2012

I've gone through the first 4 pages of search results for "classification" and found a few posts which all seem to be asking for the same or very similar things:

 

ID 8515

ID 8561

ID 6855

ID 216

ID 1638

 

Cross-posting to all of them to tie together the loose threads.

keithmacd

04-12-2012

I've gone through the first 4 pages of search results for "classification" and found a few posts which all seem to be asking for the same or very similar things:

 

ID 8515

ID 8561

ID 6855

ID 216

ID 1638

 

Cross-posting to all of them to tie together the loose threads.

alysonmurphy

11-12-2012

I'd like to be able to apply wild-card rules to identify popular mis-spellings of branded terms