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.
'Out of the box' variables such as custom link name and keywords cannot be classified. Please make it possible for us to do this!
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?
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.
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.
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.
I'd like to be able to apply wild-card rules to identify popular mis-spellings of branded terms
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.