"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
Related
I have a Firebase event. According to Firebase, the event was triggered 878 times in the past 3 months by 161 users. That should be about 5.5 times per user. But it claims that it was triggered 10 times per user. By changing the date range, I get the same confusing results (about double what is expected).
What am I not understanding here? Why don't these numbers add up?
Best I could think of would be for example if a user didn't select anything their vote might not be counted, so it could approx 87 users actually doing something? although I will admit it looks odd to me.
More information here might help you in regards to how certain events are calculated if my attempted analysis was incorrect:
https://support.google.com/firebase/answer/9234069?visit_id=637443541013685645-1067495433&rd=1
Count per user: average number of times per user that the event was triggered
It doesn't have to make users/event.One user has click 20 times other 1 time and thats 10 count per user
So if 100 users clicked 20 times and 61 users 1 times should be different, but because we dont know exactly how many times each use has clicked we assume that one user has click 20 times other 1 time
The metrics reflect different information depending on the event
From Firebase docs:
Summary table
The table lists the events that were triggered in your app during your active date range.
The table shows the following metrics for each event:
Count: number of times the event was triggered List item
Users: number of users who triggered the event
Click an event in the table to see a detail report for that event. The information in each detail report varies according to the event.
Event metrics
The following metrics are provided for each event:
Event count: number of times the event was triggered
Users: number of users who triggered the event
Count per user: average number of times per user that the event was triggered
Value: sum of all VALUE parameters supplied with the event. Use this context-sensitive metric to track any data that is valuable to your app (e.g., revenue, time, distance).
I am currently using the google calendar API to insert events into a calendar. This is the RRULE that I am using for now that allows me to insert an event at the same time on specific days of the week every week.
RRULE:FREQ=WEEKLY;INTERVAL=1;COUNT=30;BYDAY=TU,WE,FR;
Currently, events are being inserted at the same time on TU, WE & FR. However, I would like to insert the event at different times each day.
For example, the event should be between 3-4PM on Tuesdays and Wednesdays every week but between 5-7PM on Fridays. I want to avoid creating 3 separate weekly recurring events by calling the calendar API with different timings for each of these instances.
You can only use the recurrence rules on recurrent events. As it is described on the docs "Events are called recurring if they repeat according to a defined schedule". In this scenario you are effectively requesting different events albeit very similar ones because you need different schedules for each one.
My question: how do I update "this and all future" instances in a recurring event which is limited by count so that the total number of events stays consistent?
What is the problem:
Trying to modify recurring event and I follow the below guide:
https://developers.google.com/calendar/recurringevents
Basically to update all future recurring events using a target event, the doc says one need to do two calls:
update existing event to make so it ends before the target event date
create a new recurring event with the same fields except of those need changes.
That works fine until there is an event that is limited by the number of occurrences.
Let's say there is a recurring event limited by 10 occurrences and target event is 5th event.
Now I need to split the original so that the first 4 events goes to the original one (so I update COUNT from 10 to 4) and then I create a new recurring event that holds the rest 6 events (so COUNT is 6 in this case)
My first observation is that this is not how the split events are displayed in google calendar - if I test that manually, the both events still show 10 occurrences but the second one doesn't produce any extra events (I'd expect 14 events from developer perspective, yet there are 10 as any user would expect). That implies there is a different approach here? Is it?
Also if I end up counting manually the number of events, there are still issues with cases like deleting one of the events first (let's say, the 4th event) - now how do I know that I need to show 6 instances in the new one and not 7?
Those thoughts make me think there is a better approach, but I can't find any other alternatives. Any advice on that?
UPDATE
It seems like google does it differently: for example after changing a title for "this and future" events in calendar view, it doesn't seem to produce two different recurring events since if you try to delete "all" events, that will remove all of them completely (rather than deleting only one chunk, either before or after the target event)
It seems like they are creating a bunch of exceptions or maybe "recurring exception" or something to do that. Can't find any examples on how to do that as of now thought.
Can't find any good solution for this after a few days of research and while I need to move forward I ended up with a sort of "compromise" between "good enough UX for my case" and "breaking best practice".
So I ended up updating each event individually which goes against google's warning as shown below but I limited the max count by 50. This is not necessary what others want to do, but this is good enough for the real world use case in my app.
Warning: Do not modify instances individually when you want to modify
the entire recurring event, or "this and following" instances. This
creates lots of exceptions that clutter the calendar, slowing down
access and sending a high number of change notifications to users.
And if user needs to schedule more than that, the user is asked to use "end date" instead.
Again, not ideal by any means so if anyone knows how to handle that correctly or knows how google handles that, you are very welcome to share it! (meh... and I need that for outlook too now...)
UPDATE: just got an idea: as an improvement, one can edit either "all future events" or alternatively the master event + "all previous events" depending on the index of the target event. In this case one can limit the number of requests by 2 (so in case of 50 events I'll need to do 25 requests maximum)
So if user wants to change the title from "Hello" to "Goodby" and if the user picked event number 5 in the series of 50 events to change all future events, we can change the master event to "Goodby" which will change the title of all events, and then update the first 4 events to the original "Hello".
Obligatory summary of comments and chat:
Updating events:
To update specific events in a recurring event you need to update the individual instance by specifying the event instance ID.
This is just the event ID concatenated with a datetime stamp (you can see this when making an Events: instances request for your eventID; if your event ID is xxxxxxxxxxxx then an instance ID would be something like xxxxxxxxxxxx__20200603T170000Z).
Unfortunately there's no direct update-instances endpoint so to update multiple instances in one request you'd need to use batching
The API doesn't have a dedicated method for updating recurring events regardless of the recurrence type, and I presume this is the reason the documentation says to edit the previous recurring event by cutting it down and inserting a new one, as per Google's warning:
Do not modify instances individually when you want to modify the entire recurring event, or "this and following" instances. This creates lots of exceptions that clutter the calendar, slowing down access and sending a high number of change notifications to users.
Batching:
Making a batch update on event instances does keep count consistency. If you edit instances in a batch and then use the 'this and all future events' option when deleting one of the instances of the recurring event they do all get deleted as they're still a part of the recurrance. There is no new event being created in either scenario, the event instances are being changed.
If you play around with Events: instances and use Events: update to change only some instances of an event, then you can see that they all stay part of the same recurrence chain and there is no count change.
For arbitrary large counts, even if you have a recurring event with 9999999 instances, each event still has an ID which you can retrieve from Events: instances. It's stored as a single event for event use, but the IDs of the instances are the identifiers which are different.
Honestly, it's not great that you have to edit each one manually; for large counts like 9999999 it's basically infeasible because you'll have to make a batch request for each set of 100 instances you want to change, but it's the only option available via the API at the moment.
Feature Request:
You can however let Google know that this is a feature that is important for the Calendar API and that you would like to request they implement it. Google's Issue Tracker is a place for developers to report issues and make feature requests for their development services, I'd urge you to make a feature request there, the Calendar API feature request form can be found here.
My situation in Google Analytics is as follows:
Everytime, user clicks a particular element on my website, it is recorded as an event (call it EVENT1).
The problem is that my GA goal is to have at least three of those elements clicked per visit.
We can say that the goal is fulfilled when a user causes 3 EVENT1 events per one visit.
Is it possible to define this?
I know it is possible to track number of pages/visit. But it is not what I am looking for, as there are many pages that does not include the element which can be clicked.
I guess another way would be to use javascript and send "CLICKED 3 TIMES" event to GA. But I would like to avoid this.
Create an advanced segment of the "sequence" type. Make every step the same event. Apply the segment to see the number of visitors included in that segment.
I'm having an issue with Unique Events and Total events. I don't really understand why unique events are greater than total events (image attached: https://analytics-a-googleproductforums-com.googlegroups.com/attach/584c3c65bd24cfec/Screenshot%20at%202013-05-14%2017:00:40.png?gda=9qkpgUYAAADqfLbDOUx1KZ9vP-6pB8mH0QevsNJBCwpb2zqmxh9R_FqJw8mf6kYUxitGhb4bDE5x40jamwa1UURqDcgHarKEE-Ea7GxYMt0t6nY0uV5FIQ&view=1&part=4).
Someone can explain how this is posible?
Santiago Vázquez
Found the thing: you will see that "Unique Events" are great than "Total Events" when you look at an event category or action, put "Event Label" as a secondary dimension and the event has been triggered some times with no label input. Google Analytics hasn't the option "(not set)" for this particular dimension, so it just doesn't show you those events in the Total Events Count, but still counts as "Unique Events" all the users that executed this particular event category / action.
I am seeing this same issue in my the first view of my Custom Report as well. I don't know WHY it is showing more, but there seems to be a more accurate Custom Report drilldown for you to use. In my reports, one page shows in my Page drilldown with 30 total events but 62 Unique Events. However, when I click into the next dimension drilldown view, in other words click to narrow in on just one page, it shows that same page with 30 total events and only 29 unique events. That seems more accurate.
My dimensions drilldowns for this custom report are "Page" and then "Event Label"
Hope this helps!
I think Google Analytics is simply buggy.
They have to work on event reporting a bit more.
We are tracking events and e-commerce data to our own database, and we realised that both Google Analitics and Universal Analitics misses some events and e-commerce data.
We are trying to find the reason for this, but no luck yet.
If you have a segment applied it's probably sampling. You can confirm or deny sampling is the cause by seeing if there is a yellow background note above the graph but below the date selection on the report page. There is also a grid of filled in and not filled in circles next to the new scholar cap (also below the date selection) sometimes.
Unique events are calculated by session, while total events are determined by the main dimension.
In the example report below, I wanted to look at how many events occurred on each page. The dimension drilldown is Page, with Total Events and Unique Events as metrics.
Users can visit a page, but not send an event by that page ( 0 total events ). However, if their session includes an event, then unique events will be 1 or more.
Custom reports allow data combinations that may not be clear (not sure if someone already posted this point or if I saw it in another thread). Basically, my report should not include Unique Events to prevent this problem from happening, though this was probably the wrong way to go about this altogether.
Template: https://www.google.com/analytics/web/template?uid=XafJ7KvSSf-n5KWWPyvn_g
Google has deprecated (renamed) Unique Events metric as it was seriously confusing. We are expecting to see a number of times event with unique combination of category / action and label happened per other dimensions in report. Instead GA calculated a unique combination of every dimension in the report!
Now, this metric is deprecated and renamed to legacy.
New one: Unique Events is giving expected results.
I written about why total events are higher than in my blog as too many questions.
Total Events are calculated as the total number of interactions with a tracked web page object. On the other hand, where a single user session (or visit) has one or more events, this is calculated as a single Visit w/Event, or Unique Event in the reports. For example, if one user clicks the same button on a video 5 times, the total number of events associated with the video is 5, and the number of unique events is 1.