Search the web
Sign In
New User? Sign Up
webanalytics · The Web Analytics Forum
? Already a member? Sign in to Yahoo!

Yahoo! Groups Tips

Did you know...
Show off your group to the world. Share a photo of your group with us.

Best of Y! Groups

   Check them out and nominate your group.
Having problems with message search? Fill out this form to ensure your group is one of the first to be migrated to the new message search system.

Messages

  Messages Help
Advanced
DFA integration through Omniture Genesis   Message List  
Reply | Forward Message #15790 of 24265 |
Hi there -

I am hoping some members of this group are advanced Omntiure
SiteCatalyst users and have some experience of using Omniture's
Genesis tool to integrate data from 3rd party marketing tools - in
particular DoubleClick's DFA. I am about to start the integration
process using the online "drag-and-drop" tool where the integration is
configured, but before I do, I'd like to ask if there are any previous
learnings I should be aware of (whilst Omniture assign an
Implementation Consultant to help with this, they won't provide one
until the contract addendum is signed, so until the paperwork is done,
I thought I'd call on the expertise of this group).

During the DFA integration set-up, you must chose an eVar to store the
campaign ID shared by DFA and SiteCatalyst, and 3 custom events that
store the 3 metrics imported from DFA. My question is around which
eVar to use. I have 2 choices:
1. Use s.campaign
2. Use a designated eVar for DFA

Using s.campaign seems to be the best choice (and is the default
option used by SiteCatalyst) as traffic from DFA should be treated as
campaign just like all my other online campaigns. However, in the
small print of the implementation instructions, it says if you are
using Genesis to integrate data in this way, then you should NOT have
your normal "?src=XXX" campaign tracking code parameter in the URL (as
I'm guessing this would overwrite the special value s.campaign is set
to automatically when a visitor arrives from a DFA campaign). It is an
inconvenience to remove all my campaign URL tracking codes from my DFA
links, however, I still want to use s.campaign so that my DFA
campaigns are alongside all my other campaigns in the same report. Has
anyone else come across this issue? What solution did you chose? Is it
possible to write some logic in the Omniture JS file that simply won't
call the getQueryParam function for s.campaign if there's a value
already there (set by the Genesis code pasted on the landing page).

I am in Salt Lake this week at the Summit, so if you read this and are
also here, feel free to let me know and I'll happily buy you a drink
in exchange for your advice on this!

Many thanks,

John




Tue Mar 4, 2008 7:08 pm

johnwyllie1981
Offline Offline
Send Email Send Email

Forward
Message #15790 of 24265 |
Expand Messages Author Sort by Date

Hi there - I am hoping some members of this group are advanced Omntiure SiteCatalyst users and have some experience of using Omniture's Genesis tool to...
johnwyllie1981
Offline Send Email
Mar 5, 2008
12:36 am

Hi John I have been through this process before and I am happy to assist. I am at Summit this week, on the Acceleration stand. Stop by and we can chat... ...
Susan Fine
sfine@...
Send Email
Mar 5, 2008
6:43 am
Advanced

Copyright © 2009 Yahoo! Inc. All rights reserved.
Privacy Policy - Terms of Service - Guidelines - Help