Deprecated: Assigning the return value of new by reference is deprecated in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-settings.php on line 472

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-settings.php on line 487

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-settings.php on line 494

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-settings.php on line 530

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/classes.php on line 594

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/classes.php on line 594

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/classes.php on line 594

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/classes.php on line 594

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/classes.php on line 611

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/classes.php on line 705

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/classes.php on line 705

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/classes.php on line 705

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/classes.php on line 705

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/classes.php on line 728

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/wp-db.php on line 306

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/cache.php on line 103

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/cache.php on line 425

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/theme.php on line 623

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/class.wp-dependencies.php on line 15

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GoogleSitemapGeneratorLoader::Enable() should not be called statically in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/plugin.php on line 311
Analytics & optimisations « MARS IINK | Social Blog Club
Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/kses.php on line 947

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/kses.php on line 948

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/kses.php on line 947

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/kses.php on line 948

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/kses.php on line 947

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/kses.php on line 948

Archive for category Analytics & optimisations


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 55

Adobe Social Analytics

Croisé sur le site SocialMediaOptimisation, un RDV pour la présentation sur Adobe Social Analytics.
Une nouvelle brique de l’outil de Web Analytics, Omniture, qui est attendu avec impatience par de nombreux marketeurs. Réservez vos places.

No Comments


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 55

Webtrends : Webtrends Analytics 9

Webtrends vient de sortir sa dernière monture, toute de noir vêtue.
Au premier abord le design et les fonctionnalités de tableaux de bord semblent très sympa, vivement que j’ai un peu plus de temps pour jouer davantage avec l’outil !
En attendant quelques images :

,

No Comments


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 55

Google Analytics ouvre son API

Depuis le temps que certains d’entre nous l’attendait, c’est désormais officiel, Google Analytics ouvre son API :)

Voilà l’annonce faîte hier soir sur le blog officiel de Google Analytics :
“Nous sommes aujourd’hui ravis d’annoncer le lancement de l’API d’exportation de données pour Google Analytics. Cette nouvelle API rejoint Google Code Labs et est disponible pour tous les utilisateurs d’Analytics.”

Pourquoi autant d’exitation autour de cette nouvelle ?
Au-delà du fait que ça fait un moment que c’est attendu, ceux qui font du Web Analytics savent que l’important est d’avoir un outil sur mesure, qui réponde aux questionx business qui sont propres à chaque entreprise. Alors que Google Analytics fournissait des rapports plutôt standard nous allons désormais pouvoir le personnalisé en fonction de besoins spécifiques et avoir, par exemple, des tableaux de bord adaptés à vos indicateurs clés de performance et sous la forme qui convient le mieux à vos collaborateurs.

Ainsi la créativité des synergies Marketing / Technique va s’intensifier et donner lieu à de petites merveilles d’inteligence économique ;)

Les premières applications basiques, seront des visualisations de données, sur votre iPhone ou votre intranet par exemple, mais ensuite ça devra aller beaucoup plus loin. Le meilleur est à venir.

Voici les premiers exemples d’application, sur cette page, ainsi que la page dédié sur Google Code.

,

No Comments


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 55

Classification des personnalités

Une classification intéressante mais pas révolutionnaire.
Par contre c’est une bonne introduction aux classifications humaines.

,

No Comments


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 55

Classification des cerveaux : votre cerveau triunique

En 1999, après un passage rapide du côté de la psychanalyse, je découvrais la neurobiologie, une discipline passionnante pleine de révélations étonnantes sur le fonctionnement du cerveau. Parmi les nombreuses classifications proposées par la neurobiologie la première à retenir, et l’une des moins granulaire, est certainement celle de MacLean (rien à voir avec McLane).

Ce genre de classification vous permet d’optimiser efficacement vos pages pour augmenter vos taux de conversion et vos résultats. Mais de quoi s’agit-il concrètement ?

cerveau triunique

cerveau triunique

Vous avez 3 cerveaux

Parti de la théorie de l’évolution appliquée au cerveau, MacLean elabore une théorie du cerveau triunique. Il nous indique que nous disposons de 3 cerveaux, hérités de nos évolutions progressives, qui ont chacun leur intelligence, leur subjectivité, leur sens de l’espace temps et même leur mémoire. Toutefois il indique également que ces trois cerveaux fonctionnent comme 3 ordinateurs biologiques interconnectés.

Cerveau reptilien

Ce le plus primitif de nos cerveaux que nous partageons avec les reptiles.
Il s’occupe de la survie de votre corps ainsi que de sa maintenance (respiration, circulation sanguine,…). C’est le cerveau qui agit en priorité en cas de danger (deux options : la fuite ou l’attaque). Il est également à l’origine des comportements liés à la reproduction ou à la domination.
Ce cerveau fonctionne sur le mode automatique, et de ce fait il n’est pas capable de changer ses comportements, il ne fera que répéter, sans jamais apprendre de ses erreurs. Certains le considèrent même comme obsessif, et compulsif.

Cerveau limbique

Il s’agit du cerveau que nous partageons avec les chevaux et du siège de l’intelligence émotionnelle. C’est en effet le centre des émotions.
C’est le cerveau limbique qui crée le lien entre une émotion et un événement, lien qui est stocké dans la mémoire du cerveau limbique.
C’est également le cerveau qui juge et de ce fait qui applique la morale et qui domine les comportements en société en éliminant par exemple le besoins compulsifs de plaisir (sexe, nourriture, bagarre,…).
Ainsi il inhibe souvent, voir écrase (override), les envies et comportements du cerveau reptilien.

Cerveau avancé : le néocortex

C’est le petit dernier que nous partageons avec les primates, mais notre version est la plus avancée. Il est composé de 2 hémisphères, droit et gauche qui contrôlent le côté opposé du corps.
Chaque hémisphère à son propre fonctionnement et fonctionnalités.
Le cerveau gauche est linéaire, verbal et rationnel tandis que le cerveau gauche est le siège de la créativité, de l’abstrait, du rythme et de l’intuition.
A l’entrée d’une forêt le cerveau droit voit un arbre tandis que le cerveau gauche voit une forêt.
Le néocortex est le siège de la raison, il est capable d’adapter un comportement indépendamment des exigences des deux premiers, de faire des projections et du coup des plans d’actions dans le futur. En fait toutes les fonctions cognitives avancées (lire, écrire, parler, influencer,…) se trouve dans ce cerveau.

Le cerveau triunique

“La vie ce n’est pas noir ou blanc, c’est triunique.”
Le fonctionnement des 3 cerveaux est dit triunique car ils fonctionnent ensemble.
Le néo-cortex ne domine pas  vraiment les cerveaux plus anciens, au contraire le cerveau limbique a tendance à prendre le dessus. En cas de stress intense c’est plutôt le cerveau reptilen qui prend la main.
Si vous souhaitez optimiser vos pages web vous devrez travailler ces 3 axes, toutefois je vous invite à miser en priorité sur le cerveau limbique.

Ce découpage neurologique peut être corrélé à la hierarchisation des besoins de Maslow.

, ,

No Comments


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 55

Tunnels de conversion en 60 secondes

Vous n’arrivez pas à convertir en dépit de la masse de trafic que vous envoyez sur votre site ?
Pensez à créer et analyser les tunnels de conversions.
Vous pouvez alors identifier combien de prospects vous perdez à chaque étape.
Maars vous invitera surement à créer des profils pour tracker plus de 4 tunnels de conversion ;)

, , ,

No Comments


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 55

Plus de visibilité pour les retailers

Omniture, LA solution d’optimisation d’activité en ligne, vient d’annoncer Discover OnPremise for Retail.
Discover est une solution d’analyse visuelle multidimensionnelle qui permettra désormais aux retailers de gérer plus efficacement leurs campagnes multicanales notament grâce à la corrélation de données offline et online, le tout en images ;)

Omniture va donc encore accélerer votre capacité d’optimisation !

Omniture lance Discover OnPremise for Retail

Omniture lance Discover OnPremise for Retail

, , , ,

No Comments


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 55

Couplage Google AdWords / Analytics : ca bouge

Visiblement ça bouge encore du côté de Google Analytics.
Cette fois c’est la connexion Google AdWords / Google Analytics qui semble être en voie de modification.
Est-ce que Google va sortir DartSearch des cartons ? Ce serait un gros cadeau !
Nous attendons donc avec impatiente le 4 mars.

=========

Extrait du mail de Google :

On March 4th, we will be updating how Google Analytics imports AdWords data to improve security and provide greater control and convenience. This update will require that your AdWords and Analytics accounts are linked and that you have “Apply Cost Data” selected. We are proactively notifying Administrators of Analytics accounts that will be affected by this change (you either have auto-tagging enabled and/or have a linked account without cost data applied to some or all of your profiles).

If you are receiving AdWords traffic (e.g. Visits), but the AdWords reports in Google Analytics do not contain impression or click data (e.g. CPC, Impressions, ROI), then it is likely that AdWords and Analytics are not linked or the cost data option is turned off for that profile. The cost data import option is selected by default when linking your accounts; however, new profiles created after the linking process may not have cost data implemented.

,

No Comments


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 55

Classifications, Omniture et Vous

Lorsque j’ai commencé à travailler avec Omniture il ne s’agissait pas uniquement de la découverte d’un outil mais d’abord et surtout de la découverte de concepts et stratégies d’optimisations.
Parmi tous les concepts que m’a présenté Omniture, les classifications sont devenus une habitude quasi obsessionnelle :)

Qu’est-ce que les classifications d’Omniture ?

Sans trop entrer dans le détail ici, nous aurons l’occasion d’y revenir plus tard, les classifications d’Omniture consistent à classer des variables et à leur attribuer des Meta données. Selon moi les classifications sont indispensables pour les campagnes et peuvent être d’une efficacité redoutable pour les produits.

Les classifications et vous

Les classifications font partie des questions récurrentes sur lesquelles les utilisateurs d’Omniture me demandent conseil. Ils ont du mal avec cette fonctionnalité car ils ne la voient que comme un fonctionnalité, et non comme un concept.
En fait tout le monde fait régulièrement des classifications.
Agréable et désagréable et une classification, beau ou moche est également un classification. En fait d’un point de vue PNL les classifications sont le pont entre un objet et une généralisation. Lorsque je suis devant une porte, si je la classe dans les portes automatique je sais qu’il suffit de me placer devant pour qu’elle s’ouvre.

Les classifications et moi

Avant de découvrir le concept d’Omniture, comme vous je faisais de nombreuses classifications au quotidien. Désormais, en tant que Web Analyste, ça devient une habitude. Parmis mes classifications préférées il y a les classifications des humains.
Certains trouveront cela intolérable et me traiteront de je ne sais quoi.
Toutefois en faisant cela, ils viennent de me classer.
En fait la plupart des philosophe ont également essayé de catégoriser les être humains et de les classer.
Hyppocrates, médecin grec qui a vécu entre 459 et 377 avant J.C, utilise 4 catégories pour classer les êtres humains : lymphatique, sanguin, bilieux, nerveux.
Jung, fondateur de la psychologie analytique, a dépassé la classification traditionnelle de la caractérologie pour proposer une structure schématique de la personnalité, dans son ouvrage fondateur Les types psychologiques (1911 !)
Jung y distingue quatre « fonctions » psychiques, le type Pensée, le type Intuition, le type Sentiment et le type Sensation, que chacun possède à des degrés différents.
Il existe certainement un nombre conséquent de classifications des êtres humains, mais ma préférée reste celle de Myers-Briggs, qui utilise 16 types. Les Soufis avaient déjà proposé une classification de ce type assez complexe mais très riche.

C’est quoi l’intérêt des classifications humaine pour le web analytique ?

D’abord ça me semble une façon amusante de comprendre le concept derrière la fonctionnalité de classifications d’Omniture.
Ensuite je pense que l’identification des catégories d’humains qui consultent votre site ou achètent vos produits vous permettra d’optimiser plus efficacement vos pages, votre site et peut être même vos produits, ou services.
Nous aurons certainement l’occasion de donner de nombreux exemples mais le premier qui me vient à l’esprit est celui de Castorama vs Leroy Merlin.
Castorama et Leroy Merlin sont deux enseignes de grande distribution dans le secteur du bricolage, de la décoration intérieure, et du jardin. Sur leur site Internet, les deux se déclarent « leader sur leur marché ».
Leroy Merlin s’est rendu compte avant Castorama de 2 points cruciaux :
- le rayon déco prenait de plus en plus de place dans leur CA
- bien que ce soit les hommes qui montent les étagères ce sont souvent les femmes qui décident quelle étagère acheter.
Dès lors ils ont décidé de s’adresser aux femmes.
Qu’est ce qui a changé ?
L’aspect et l’organisation des magasins, le ton de la communication, le format publicitaires (les idées prennent vie du côté de chez vous, ça vous rappelle quelque chose ?), …
Résultat : Leroy Merlin a su s’imposer sur un secteur très concurrentiel où Castorama disposait de bonnes positions.

Casto a essayé mais plus tard, et le résultat laisse a désirer je trouve…
De toute façon aujourd’hui ce n’est plus différenciant comme positionnement dans le bricolage ou la déco.

Par contre il y a peut être encore des niches a explorer :p

Peut on classer les individus comme les campagnes ?

“Non pas là non”.
Je pense qu’il y a plusieurs choses importantes à garder en tête lorsque l’on fait des classifications d’individus.
Vous pouvez vous tromper. D’abord parce que l’erreur est humaine, ensuite parce qu’un individu peut appartenir à plusieurs classes, en fonction des situations dans la quelle il se trouve.
Les individus changent (si si je persiste et je signe).
Dans le cadre du MBTI on considère qu’un individu qui suit une évolution complète passe par plusieurs types de personnalités avant de revenir à son premier profil.
Du côté Omniture un code (de tracking par exemple) ne peut pas appartenir à 2 catégories (search et display par exemple), et lorsque vous changer la classe d’une variable c’est rétroactif.

No Comments


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 55

Google AdWords ou Analytics : à qui se fier ?


Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/link-template.php on line 73

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/link-template.php on line 98

Le couplage Google AdWords / Google Analytics vous permet d’avoir une vision plus qualitative de vos investissements en liens sponsorisés.

A l’instar de Marc vous vous demandez peut être pourquoi les chiffres du tracking Google AdWords sont différents de ceux de Google Analytics. Et surtout lequel des deux a raison ?

Les deux systèmes ont raison, bien qu’ils donnent des résultat différents.
Avant de rentrer dans le détail technique, voici deux petits exemples qui nous aiderons à comprendre.

Read the rest of this entry »

, ,

No Comments


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/40/d243880784/htdocs/Social-Blog-Club/wp-includes/functions.php on line 55

Google AdWords / Google Analytics : le couplage

Le couple Google AdWords / Google Analytics est idéal pour optimiser vos campagnes de liens sponsorisés.
La question comment récupérer mes données AdWords dans Google Analytics est assez récurrente.
Bientôt un pas à pas sur la question…

, ,

No Comments