Loading ...
Sorry, an error occurred while loading the content.

Re: Omniture Site Catalyst image request is failing

Expand Messages
  • Sid
    Yuhui This is brilliant! This is an unbelievable solution. thank you so much. Thanks again S
    Message 1 of 12 , Apr 1 2:23 AM
    View Source
    • 0 Attachment
      Yuhui

      This is brilliant! This is an unbelievable solution. thank you so much.

      Thanks again
      S


      --- In webanalytics@yahoogroups.com, Matt Curtis <matt.curtis@...> wrote:
      >
      > Yuhui,
      >
      > This is incredible. Thank you so much - I had no idea you could do something
      > like this.
      >
      > Thanks,
      >
      > Matt Curtis
      >
      > On Wed, Mar 30, 2011 at 9:55 PM, Yuhui <yuhuibc@...> wrote:
      >
      > >
      > >
      > > Thanks, Sid (and Matt), for that clarification.
      > >
      > > In that case, what you might want to do is to use unique tag objects. If
      > > you're not using that already, then here's the solution. This can get quite
      > > technical, so if you're not familiar with JavaScript, it might be best to
      > > enlist your coding guru to help you out.
      > >
      > > In your s_code.js file, look for these lines:
      > >
      > > var s_account='report suite id'
      > > var s=s_gi(s_account)
      > >
      > > Since you have 2 lines that start with "s_account=", the above lines will
      > > most likely look like:
      > >
      > > var s_account='original report suite'
      > > var s_account='test report suite'
      > > var s=s_gi(s_account)
      > >
      > > You will need to change that to:
      > >
      > > var s_account='original report suite'
      > > var s=s_gi(s_account)
      > > var s2_account='test report suite'
      > > var s2=s2_gi(s2_account)
      > >
      > > Then populate your props and eVars for the new "s2" object, e.g. s2.prop1,
      > > s2.prop2, s2.eVar3, s2.events, etc.
      > >
      > > In your pages' code, look for:
      > >
      > > var s_code=s.t();if(s_code)document.write(s_code)
      > >
      > > And change that to
      > >
      > > var s_code=s.t();if(s_code)document.write(s_code)
      > > var s2_code=s2.t();if(s2_code)document.write(s2_code)
      > >
      > > Once you've coded everything correctly, you should then see 2 tags firing
      > > for each page, one tag for "s", one tag for "s2", and you should see both
      > > report suites filling up with the expected data.
      > >
      > > Hope that helps!
      > >
      > > And Matt - if eVar22 isn't setup in a report suite, then you will never see
      > > a report for it, i.e. it's as if eVar22 was never set in your code. To my
      > > knowledge, there's no way to setup eVar22 in your report suite subsequently
      > > and then get back the "lost" data.
      > >
      > >
      > > Regards,
      > > Yu Hui
      > > Twitter: @yuhui
      > >
      > > --- In webanalytics@yahoogroups.com, "Sid" <syedspiky@> wrote:
      > > >
      > > > Hi Yuhui
      > > >
      > > > Matt is correct that I'm trying to send different data to different
      > > report suites. I'm not sending identical data to both.
      > > >
      > > > I know about scenario 2 (Multple suite tagging) but the goal I'm trying
      > > to achieve is slightly different from the simple muti-suite tagging. It's
      > > even more confusing when I see the first one is actaully failing and the
      > > second one is actually firing.
      > > >
      > > > Thanks
      > > > S
      > > >
      > > >
      > > > --- In webanalytics@yahoogroups.com, Matt Curtis <matt.curtis@> wrote:
      > > > >
      > > > > I think one of the reasons that he is using "Scenario 1" is that is
      > > sounds
      > > > > like he's trying to send different data to different suites.
      > > > >
      > > > > What happens if I have an eVar set up in Suite 1 but not in Suite 2 and
      > > then
      > > > > try to send that data to both suites? (which is what seems like would
      > > happen
      > > > > if I set the s.account to both suites?)
      > > > >
      > > > > s.account = "suite1, suite2"
      > > > >
      > > > > evar22 = [some action]
      > > > >
      > > > > On Tue, Mar 29, 2011 at 11:12 AM, Yuhui <yuhuibc@> wrote:
      > > > >
      > > > > >
      > > > > >
      > > > > > Hi Sid,
      > > > > >
      > > > > > Yeah, there's your issue. You should almost always *never* use
      > > Scenario 1
      > > > > > with Omniture tags.
      > > > > >
      > > > > > The explanation is slightly technical, but here goes: assuming your
      > > > > > JavaScript code only has one "s" object and each of your pages only
      > > has one
      > > > > > call to "s.tl()", you are only ever going to see one tag firing, in
      > > your
      > > > > > case, the first one most of the time.
      > > > > >
      > > > > > If you have no idea what I said, never mind, because the solution is
      > > very
      > > > > > simple: use Scenario 2. Don't worry about the 2048 or whatever
      > > character
      > > > > > limitation. With Scenario 2, both accounts' variables and values are
      > > never
      > > > > > duplicated within the tag, yet the same tracking data is still saved
      > > to both
      > > > > > report suites.
      > > > > >
      > > > > > Look up "Multi-Suite Tagging" in Omniture Help for more info on
      > > Scenario 2.
      > > > > > That should resolve your predicament. Hope that helps!
      > > > > >
      > > > > > (If you're still worried about hitting the browser URL character
      > > > > > limitation, take a look at Dynamic Variables (see Omniture Help). But
      > > I
      > > > > > advise you to do that only after you've actually solved this
      > > multi-suite
      > > > > > tagging issue.)
      > > > > >
      > > > > >
      > > > > > Regards,
      > > > > > Yu Hui
      > > > > > Twitter: @yuhui
      > > > > >
      > > > > > --- In webanalytics@yahoogroups.com, "Sid" <syedspiky@> wrote:
      > > > > > >
      > > > > > > Hi Yuhui
      > > > > > >
      > > > > > > I've used the first scenario on my site but the starnge thing is
      > > that the
      > > > > > first request isn't working whereas the second request is working
      > > fine. They
      > > > > > both are using different Javascript.Any idea?
      > > > > > >
      > > > > > > Thanks
      > > > > > >
      > > > > > >
      > > > > > > --- In webanalytics@yahoogroups.com, "Yuhui" <yuhuibc@> wrote:
      > > > > > > >
      > > > > > > > Hi Sid,
      > > > > > > >
      > > > > > > > When you said that you had installed 2 SiteCatalyst tracking on
      > > your
      > > > > > site, which scenario did you mean?
      > > > > > > >
      > > > > > > > Scenario 1:
      > > > > > > >
      > > > > > > > s_account = 'original report suite'
      > > > > > > > ...
      > > > > > > > ...
      > > > > > > > ...
      > > > > > > >
      > > > > > > > s_account = 'test report suite'
      > > > > > > > ...
      > > > > > > > ...
      > > > > > > > ...
      > > > > > > >
      > > > > > > > or
      > > > > > > >
      > > > > > > > Scenario 2:
      > > > > > > >
      > > > > > > > s_account = 'original report suite, test report suite'
      > > > > > > > ...
      > > > > > > > ...
      > > > > > > > ...
      > > > > > > >
      > > > > > > > If it's Scenario 1, then there could be a "race" condition, i.e.
      > > the
      > > > > > first tag that the browser processes will be the tag that works for
      > > you,
      > > > > > while the other one will give an error or not be seen at all.
      > > > > > > >
      > > > > > > > Regards,
      > > > > > > > Yu Hui
      > > > > > > > Twitter: @yuhui
      > > > > > > >
      > > > > > > > --- In webanalytics@yahoogroups.com, "Sid" <syedspiky@> wrote:
      > > > > > > > >
      > > > > > > > > Hi all site catalyst experts
      > > > > > > > >
      > > > > > > > > One of my site's Omniture tracking isn't working. Don't know
      > > since
      > > > > > when but I've installed two site catalyst tracking on the site
      > > because I
      > > > > > wanted to compare original report suite's request against a test
      > > report
      > > > > > suite requests which has a couple of variables in this. I was told if
      > > the
      > > > > > requests is above 2048 characters then IE just drops it and doesn't
      > > send the
      > > > > > request to Site Catalyst server.
      > > > > > > > >
      > > > > > > > > Now the test report suite tracking working fine but the
      > > original
      > > > > > report suite's tracking shows 'aborted' status in httpfox. It seems
      > > it's
      > > > > > failing randomly but most of the time because I can still see some
      > > data in
      > > > > > the original report suite. I've checked the requests on Firefox not
      > > in IE so
      > > > > > the length of image requests won't be an issue here I think. I can't
      > > figure
      > > > > > out anything but we've used 2 versions of jQuery for each report
      > > suite's
      > > > > > tracking in noconflict mode though in case there is a conflict. Any
      > > other
      > > > > > reason why you think this might be happening? Looking forward to
      > > hearing
      > > > > > your responses.
      > > > > > > > >
      > > > > > > > > Many Thanks
      > > > > > > > > S
      > >
      > >
      > >
      >
      >
      > [Non-text portions of this message have been removed]
      >
    Your message has been successfully submitted and would be delivered to recipients shortly.