how to get adjusted bounce rate in Omniture sitecatalyst - bounce

adjusted bounce is defined as 'bounces excluding the single page visits that have finished some interactions on the page'; for instance, single page visits that stay longer than 15 seconds, or trigger an ajax event; I want these visits to be excluded from bounce rate calculation
I know in GA it can be adjusted quite easily by customizing the GATC, but I haven't found anything about Sitecatalyst, does anyone have any idea?
thanks!

In SiteCatalyst, a "bounce" is considered a single image request (no other calls, not even custom links). Based on what you're looking for, I'd anticipate this is the segment you're looking for:
Include all visits where time spent on page is greater than 15 seconds
Exclude all visits where path length is greater than 1
Keep in mind this cannot include single page visits that did not send a custom link image request, nor can it track visits where more than one s.t() call was fired. It only includes visits where a single s.t() was fired, and at least one custom link.

Related

Instagram "posted for first time in a while" notification

Does anyone know how Instagram determines whether or not to send a push notification saying "_______ has posted for the first time in a while". Is it based purely on time, or is it different based on how often the user posts? If it's based on the individual person, what is the algorithm they use to determine whether a notification should be sent?
It depends on how often you post before. If you post every day, but then only post a week later, the notification may appear.
In general, it could be some range from 1 to 3 weeks to multiple months.

Heap Analytics - How do I capture the amount of time users spend on a page?

I am using Heap Analytics to track events (page clicks and page views), but once registering the event I am having difficulty in finding how to measure how long user views a page.
The only place similar to this measurement is in the graphs, under average time between, for pages where I select page view, along with a start and end event.
If this is the method to track event for page view, what is the start, and what is the end event?
UPDATE 25NOV16: After using a similar method for a little while to track user exits (and thus, total session time), I can say that the below method works, but not 100% of the time. It's unclear to me what determines the success (latency, maybe).
after my comment (which i deleted) i did a little testing and i have a solution, but it requires a custom event, so you can't do any retroactive analysis.
First, define a page_view event for whichever page.
Then, in your page, add this snippet:
window.onbeforeunload = function() {
heap.track('pageExited', {arbitraryProp: "string"})
}
Then, in the graph view of the heap dashboard, you can select average time between, page_view, and pageExited.
Note that onbeforeunload will fire when user refreshes, in addition to when user exits page.

StackExchange API returning less sites than actual number

I am working on one application that produces timeline of user on every site of Stack Exchange. We have some users on SharePoint.SE.
Since I want list of all the sites, I am trying to get it using API 2.2
GET /2.2/sites/
As shown here. But it is getting only partial sites. The response is missing sites like Beer.SE, SharePoint.SE.
How do I retrieve them too?
You need to pass additional parameters. Beer.SE appears on page 3 with a pagesize of 100:
https://api.stackexchange.com/docs/sites#page=3&pagesize=100&filter=default&run=true
With no parameters, the default pagesize is 30 results. You can tell if there are more items than what is returned in your call by checking the has_more parameter in the common wrapper.
In this instance, with a pagesize of 3, there are 3 total pages and Beer.SE happens to be on the last page.
After rereading the sites documentation, it says
The pagesize parameter for this method is unbounded, in acknowledgement that for many applications repeatedly fetching from /sites would complicate start-up tasks needlessly.
This means that you can set your page size to something like 1000, and Beer.SE will appear in that results. At this point, there are not 1,000 Stack Exchange sites, so that will work.

Flurry Analytics Dashboard -- Display Duration of Timed Events

On the Flurry Dashboard, is there a way to compare the total duration of 2 (or more) different timed events?
For example, suppose an application logs distinct timed events for different screens (i.e. Screen1, Screen2, Screen3, etc.) starting the timed event when the screen appears and ending the timed event when the screen disappears. We would like a way to visually compare the total amount of time for each of the events on a single graph of some sort. (We would also like to see the average total amount of time per session on a single graph) This would give us a quick understanding of what percentage of time our users are spending on different screens within the app.
I've played with the dashboard but I can't seem to find a way to do this. It seems like it is not possible to show the duration of timed events on the dashboard. So the only way to view event duration is to look at individual events in isolation in the Events section.
Hopefully I'm missing something, so thanks in advance for any answers to this question.

Mirror API latency when sending something to a timeline

It seems that sometimes timeline items (just text) arrive instantly and other times they take forever... Is there a way to send one at precisely the right time?
You can send the notification at a precise time.
timelineItem.getNotification()
.setDeliveryTime(new DateTime(oneMinuteInFuture.getTime()));
That's a java example, where oneMinuteInFuture is a Calendar object set to one minute after now.
What happens when you do this is the card is inserted in the timeline immediately, but the notification is delayed until the specified time. So the card goes in right away and one minute later I get a chime.
There is an unaccepted issue related to this at the issue tracker you might want to star and follow, it appears that this functionality might change in the future.

Resources