I am building a "leave calendar" where an employee requests time off, and a manager approves it.
If an employee drags a leave-event into their fullcalendar for 2 days, and the manager approves it, but then decides later that they want to take 3 days off instead, I need a way to visually depict that 2-out-of-3 days is approved within that colored-bar-event in calendar.
You know how MS Outlook/Calendar has that "accepted state" and "non-accepted state" with the little diagonal-grey-lines. That's what I'm after - - - some visual way of showing that days 1 and 2 of the event are approved and day 3 of the event is not approved. I have not seen anything in the documentation that provides a "change visual attributes of the bar based on what date it spans over" yet. Is this even technically possible?
Related
Today we launched our first campaign on Chartboost. We added 300$ on account and started our first campaign. In less than one our we spent all the money. Then I switched campaign off but still the balance going up in negative. Can you help me why? Beacuse we didn't pay for that additional negative balance we made campaign for 290$ not 450$ ...
What can we do?
The most common reason for campaigns to go over budget is the fact that they reach their budget in the minutes before the first check that compares the spend to the budget. This can happen if you your campaign has a wide target (ie - if you are targeting the whole world for example). Campaigns that have very broad targeting (little to no usage of filtering or available targeting on the dashboard) will serve impressions very quickly and this only increases the probability of exceeding the budget.
It is also very common for CPI campaigns to continue to "Spend Money" even after the campaign has been turned off. The reason why this happens is that we attribute installs to recorded clicks up to 21 days after the click. Also, the Install is not recorded until the 1st bootup of the app. For a number of reasons this 1st bootup may not occur until a couple of days after downloading onto the device from the App Store. There is no way to "turn off installs" for clicks that have already occurred.
Hope this helps.
"Duplicate Event" button doesn't work for me. I need to replicate event data for multiple events (dates).
Can create an event template in order to create multiple events with the exact same settings/data? If so, what's the process?
Context: this is for recurring events involving sporting equipment rental.
Use the link below to see. Forward to May. Note the event times on the 15th. I essentially want the exact same events replicated from 15 May-15 October and I'd love to avoid manually inputting each event. For example, I'd like to create a template for the 11a-1p rental and create an event for each of the days within the aforementioned time period without editing every detail of the event roughly 180 times. Same for each other event. That's 8 different events (all identical) for roughly 180 days of the season. That's a lot of manual data input. Feel me?
Events Calendar
We're implementing Google Analytics in retail consumer kiosk software. There is no Javascript or SDKs or web pages involved - we craft a URL per Measurement Protocol and post it. We find that sometimes hits seem to just stop getting counted. If we watch the Real-Time section on the GA web site we can see that our hits continue to get posted, but over in the Behavior / Screens section the number of screen views for this device for today stops incrementing.
It's not just a "sometimes you have to wait 24 hours" thing, because Tuesday and Wednesday of last week still show zero today. If it's a rate limit, I can't see what - we're nowhere near 200k hits per day (per user, but from our point of view each kiosk is a user - we don't have any means to identify individual users); we shouldn't be hitting 500 hits per session because we send a session start (ec=Session&sc=Start) each time the user does something on the main menu and a session end (ec=Session&sc=End) each time the workflow finishes, which shouldn't ever be more than 20 screens - the default 'idle timeout' definition of a session wouldn't work well for us since a user can legitimately be working on a single screen for 10 minutes or more editing a picture whereas also a user can finish and leave and the next user in line start using the kiosk within just a few seconds; we shouldn't be sending events 'too fast' because it takes a couple seconds for a human to read the screen and reach out and touch a button.
What we observe is that some days it counts up to 340-360 and stops and some days it stays at 0 permanently. Any idea what's happening and how to fix it?
11/24: Today it went up to 352 and then stopped. This was about one hour of activity. All of this has been done with "Highest precision" selected.
12/1: Still same, counts for about one hour, to 347 screen views today, then stops incrementing.
When I look at Audience/Overview it says "Sessions 1". There should be dozens of sessions, split up by when we send (ec=Session&sc=Start). I think it must not be recognizing that as a session, it must be using the session timeout (idle), and staying all within a single session, and therefore limiting to 500 hits (we've got some events to go along with the screen views). And this is just wrong. Session should end when we say it does.
12/1: One correction, we actually do send sc=start and sc=end, with the values lower-case, as specified by Google.
My coworker did some experimenting and found that sc=start is ignored on t=event hits. It is recognized on t=pageview hits. I changed my reporting a bit to generate a fake pageview when a session starts, just so I could send the sc=start, and now the counts are accurate.
New to Google Analytics and couldn't figure out how to get this to show.
I would like to figure out how frequently a user visits our site after they've registered. The reason is I want track their engagement following their registration.
So let's say user registered at week 0, I want to figure out how many times they come back in week 1, week 2 and week 3. This way I can tell whether users tend to stay engaged for first 2 weeks, then slowly loses interests, or their interests grows as the weeks goes by after they've registered. Any idea on how to achieve this?
Thanks!
Set a custom variable at visitor level when your users register. Use that to build a segment for visitors that have at some point registered at your site. Apply that segment to the "frequency and recency" report (audience->behaviour->frequency and recency).
The custom variable will allow you to recognize visitors that have registered (even if they are not currently logged in) until they change browsers or delete their GA cookies.
I need some kind of control that will allow a user on a mobile device to select from available time ranges in a 24-hour period for a reservation manager.
For example, let's say the range starts at 8:00am. A user cannot rent the space between 10:00am and 12:00pm (noon), and cannot rent the space between 3:00pm and 6:00pm. Therefore, some valid rental ranges would be:
8:00am - 9:00am
8:00am - 10:00am
12:00pm - 3:00pm
1:00pm - 3:00pm
6:00pm - 7:00pm
You get the idea.
The problem is that I need to display to the user which range of times are already taken, and allow them to select a range of time from the available time slots. My boss suggested using a range slider (such as the jQuery one or the Telerik one), but none of the ones I've found seem to support this use-case.
I should note that my boss would really like to see this as a "timeline" for lack of a better word, where two slider bars represent the range and the slider line is colored red or green depending on whether that time is available.
Any suggestions? Keep in mind that this is on a mobile device using ASP.NET MVC3.
What you could do is to dynamically load the values using ajax when your control has focus and populate that control with the received values. In addition, you could use Remote attribute that would validate the selection against the available hours when a user makes a selection, just to be sure that another user did not make a reservation for the chosen time (so that you can avoid time clash).