Skip to main content
mcolema1
Level 5
Feb 13, 2010 5:50 AM UTC
Investigating

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

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 replies

    Show previous replies
    benjamingaines2
    Adobe Employee
    benjamingaines2Adobe Employee
    Adobe Employee
    Dec 12, 2012 1:58 PM UTC

    @keith_macd: Thanks for doing the leg work! I will combine these ideas into a single entity so that the votes are aggregated. This definitely helps us understand the priority. Keep the great ideas, votes, and comments coming on this!

    Translate
    benjamingaines2
    Adobe Employee
    benjamingaines2Adobe Employee
    Adobe Employee
    Dec 12, 2012 2:01 PM UTC
    Removing the "partially implemented" status per Mark's request. I also merged four other ideas into this one.
    Translate
    d1g1tal
    Level 3
    Jul 23, 2013 4:56 AM UTC

    I appreciate you can using a prop or eVar copy over the value from Keyword in to one of these to classify but what would be really useful is to be able to out of the box SAINT Classify traffic source keywords. I expect this is the same with most companies but we want to be able to build a report that is one column for SEO Brand Terms and one column for SEO Non-Brand terms, which should be simple. Having to push this in to another variable to classify seems unnecessary especially given it's not as robust as using the standard variable used round the business.

    Translate
    stefanies325986
    stefanies325986
    Level 4
    Jun 9, 2020 6:52 AM UTC

    what's the status here?

    Translate
    Terms & ConditionsAccessibility statement

    Loading footer...