OmnitureCare
-
@ In SiteCatalyst, if you go to Help > Knowledge Base and search for "campaign tracking code," you will find good info on this.
43 minutes ago
from TweetDeck
in reply to AmberLeighN
-
@ Sorry! I usually write that out. I mean there is an article in our Knowledge Base that explains how to capture tracking codes.
44 minutes ago
from TweetDeck
in reply to AmberLeighN
-
@ Check out KB ID 72 for more info. . . your developer should be able to tell you what param name you're set up to capture.
about 1 hour ago
from TweetDeck
in reply to AmberLeighN
-
@ The idea is that if our code sees ?cid=twitter in a URL, it can recognize "cid" (or other value) and grab the value ("twitter")
about 1 hour ago
from TweetDeck
in reply to AmberLeighN
-
@ . . .which is why tracking codes are great. You'll need to find out what query string you're using to capture them on landing.
about 1 hour ago
from TweetDeck
in reply to AmberLeighN
-
@ With many of the URL shorteners, there is no way to see referrer traffic. It's a limitation across all of web analytics, FWIW.
about 1 hour ago
from TweetDeck
in reply to AmberLeighN
-
@ . . .in your URLs before you shorten them. SiteCatalyst will be able to grab the tracking code after the redirect from bit.ly.
about 1 hour ago
from TweetDeck
in reply to AmberLeighN
-
@ I'm not surprised. It probably has to do with the way that they redirect. This is why I am a fan of using tracking codes. . .
about 1 hour ago
from TweetDeck
in reply to AmberLeighN
-
@ I'm digging into it now. FWIW, I think you're actually okay with "this" rather than "true" here. The anchor tag has an href.
about 2 hours ago
from TweetDeck
in reply to alexbrasil
-
@ OK. What report are you/they viewing in this case?
about 2 hours ago
from TweetDeck
in reply to andyblackburn
-
@ Right. The full value gets populated before the point where latency would occur. So it's not a way around that, unfortunately.
about 2 hours ago
from TweetDeck
in reply to jasonegan
-
@ Sure thing. How can I help?
about 2 hours ago
from TweetDeck
in reply to andyblackburn
-
@ OK, excellent. Let me know if anything else comes up.
about 2 hours ago
from TweetDeck
in reply to swcalise
-
@ @ That's true, although if we're still talking about s.tl() then pageName isn't going to do much anyway.
about 2 hours ago
from TweetDeck
-
@ Exactly right.
about 2 hours ago
from TweetDeck
in reply to jasonegan
-
@ @ Err, anchors. . . you know what i meant.
about 3 hours ago
from TweetDeck
-
@ @ Good to know. I was positive that query strings are stripped by default, but I wasn't 100% sure on anchor tags.
about 3 hours ago
from TweetDeck
-
@ You're welcome. Any time.
about 3 hours ago
from TweetDeck
in reply to jhellitt
-
@ . . .my understanding is that the app store changed its policies regarding API calls, which is why it's throwing that error.
about 3 hours ago
from TweetDeck
in reply to EmailJuan
-
@ Right. The new components provided for iPhone app measurement will allow you to submit the app successfully. . .
about 3 hours ago
from TweetDeck
in reply to EmailJuan
|
- Name Ben Gaines
- Location Orem, UT
- Web http://blogs.omni...
- Bio Community Manager at Omniture, an Adobe Company. Former ClientCare Support Engineer. Official representative of Omniture Client Services on Twitter.
|
