Status Update
Comments
si...@gmail.com <si...@gmail.com> #2
Unfortunately, setting the color of a progress indicator at runtime has only been possible since api 31.
For earlier API support you can override Glance.AppWidget.CircularProgressIndicator
style to set the colors of your indicators.
di...@gmail.com <di...@gmail.com> #4
ph...@googlemail.com <ph...@googlemail.com> #5
can be recorded in GA.
Here are some other examples of useful data to add annotations to...
Google News Events
Chart + News on Googlefinance
ip...@gmail.com <ip...@gmail.com> #6
mailing. But another, perhaps better, way to track "external events that drive website traffic indirectly" is
integration with a Google Calendar.
ce...@gmail.com <ce...@gmail.com> #7
[Deleted User] <[Deleted User]> #8
star it.
ma...@gmail.com <ma...@gmail.com> #9
da...@gmail.com <da...@gmail.com> #10
how what we're working on how publishing great content to the web affects their
traffic and repeat visitors.
ni...@gmail.com <ni...@gmail.com> #11
use analytics to measure trends in sales.
jm...@gmail.com <jm...@gmail.com> #13
jo...@gmail.com <jo...@gmail.com> #14
an...@gtempaccount.com <an...@gtempaccount.com> #15
wi...@gmail.com <wi...@gmail.com> #16
de...@gmail.com <de...@gmail.com> #19
mr...@gmail.com <mr...@gmail.com> #21
me...@gmail.com <me...@gmail.com> #22
si...@gmail.com <si...@gmail.com> #23
br...@gmail.com <br...@gmail.com> #24
[Deleted User] <[Deleted User]> #25
ga...@gmail.com <ga...@gmail.com> #26
wh...@gmail.com <wh...@gmail.com> #27
jr...@google.com <jr...@google.com> #28
jr...@google.com <jr...@google.com> #29
pf...@google.com <pf...@google.com> #30
ma...@gmail.com <ma...@gmail.com> #31
jm...@intelius.com <jm...@intelius.com> #32
When considering this feature, it may be helpful to imagine multiple audiences using it. For example, as melvin said above, the dev team can automate the notifications of code changes. Email marketers can note major newsletter or offer mailings. Paid advertisers can note the launch date of campaigns. Optimizers can note A/B or MVT test launches, etc. It would be helpful if these were categorized so we can see all public dev anotations, all email annotations, personal private annotations etc.
Since many of the stakeholders are using various software packages to update or report, having API access to read AND write annotations would provide a very useful level of functionality.
wo...@gmail.com <wo...@gmail.com> #33
This would allow us to add annotations based on published content for a news website I manage. Some kind of csv upload or xml file linking could also be a solution.
[Deleted User] <[Deleted User]> #34
ct...@gmail.com <ct...@gmail.com> #35
yn...@gmail.com <yn...@gmail.com> #36
[Deleted User] <[Deleted User]> #37
do...@gmail.com <do...@gmail.com> #38
op...@gmail.com <op...@gmail.com> #39
st...@rsc.org <st...@rsc.org> #40
pa...@gmail.com <pa...@gmail.com> #41
ha...@hansakoch.com <ha...@hansakoch.com> #42
dh...@gmail.com <dh...@gmail.com> #43
[Deleted User] <[Deleted User]> #44
an...@numerique.ca <an...@numerique.ca> #45
do...@gmail.com <do...@gmail.com> #46
do...@gmail.com <do...@gmail.com> #47
pa...@gmail.com <pa...@gmail.com> #48
jd...@dagerot.com <jd...@dagerot.com> #49
ba...@gmail.com <ba...@gmail.com> #50
ar...@gmail.com <ar...@gmail.com> #51
ja...@gmail.com <ja...@gmail.com> #52
je...@burnbright.net <je...@burnbright.net> #53
aa...@gmail.com <aa...@gmail.com> #54
ct...@gmail.com <ct...@gmail.com> #55
si...@gmail.com <si...@gmail.com> #56
wo...@gmail.com <wo...@gmail.com> #57
Btw; yes - I too still want this feature!
You should be able to unsubscribe by "unstarring" the thread. Though that will also undo your vote for this issue. And I guess we all want to keep those votes, so that perhaps one day somebody at Google will work on this.
Perhaps you should just make an email filter instead?
jo...@gmail.com <jo...@gmail.com> #58
mi...@gmail.com <mi...@gmail.com> #59
ba...@gmail.com <ba...@gmail.com> #60
[Deleted User] <[Deleted User]> #61
c....@gmail.com <c....@gmail.com> #62
[Deleted User] <[Deleted User]> #63
ju...@gmail.com <ju...@gmail.com> #64
[Deleted User] <[Deleted User]> #65
If we had this feature on the API we would be able to do shared annotations more securely.
da...@abbeytheatre.ie <da...@abbeytheatre.ie> #66
c....@gmail.com <c....@gmail.com> #67
to...@brickhousesecurity.com <to...@brickhousesecurity.com> #68
mi...@gmail.com <mi...@gmail.com> #69
ra...@rafaelfurquim.com.br <ra...@rafaelfurquim.com.br> #70
su...@gmail.com <su...@gmail.com> #71
c....@gmail.com <c....@gmail.com> #72
da...@gmail.com <da...@gmail.com> #73
es...@gmail.com <es...@gmail.com> #74
da...@gmail.com <da...@gmail.com> #75
fc...@gmail.com <fc...@gmail.com> #76
[Deleted User] <[Deleted User]> #77
* As an API user, I can send a request to retrieve all of my annotations so that I can store them in a third-party system
* As an API user, I can add annotations so that my third-party data can be reflected in Google Analytics
* As an API user, I can delete annotations so that my data is up to date
These are essentially the requirements that this ticket is trying to address. Additional features could be:
* Retrieve all annotations by date range
* Retrieve all annotations across multiple profiles
[Deleted User] <[Deleted User]> #78
ho...@gmail.com <ho...@gmail.com> #79
For example if I have a email program, it could add an annotation to GA every time an email is sent to customers, then we can easily look at sales behaviour based on that annotation.
ed...@gmail.com <ed...@gmail.com> #80
want is with events. Events are really powerful, you should look into it.
Annotations were added to be one-off notes for final users for a date. Like
for example: next time you have a spike in your traffic, you an annotate
the date with a "emails sent to customer", so that when you look at it
again 3 months for now, you can remember what it is.
[Deleted User] <[Deleted User]> #81
gr...@gmail.com <gr...@gmail.com> #82
It would be really convenient to be able to connect the bug tracker of choice to your GA account.
Or, the business is running Marketing campaigns that they may be tracking with a calendar in a certain application. Auto adding that would make sure that we are not losing information.
c....@gmail.com <c....@gmail.com> #83
- marketing events occurred
- site changes/releases occurred
- outages occurred
- 3rd-party / world events affecting site behavior occurrred (e.g., getting Slashdotted, a holiday occurring that impacts traffic, etc)
- marking the start of tests
Annotations are timeline metadata, to be compared against any other metric. Annotations have no quantitative value directly associated with them aside from the timestamp. It exists in a different space from tally-able data like Events, visits, etc - and is meant to be consumed alongside with it.
The idea behind exposing the API is not so we don't have to track this stuff internally - but specifically so we can, and have that data sync (back and forth) with Google Analytics.
Another nice feature would be being able to tag these annotations for categorization purposes, but I'll settle for the CRUD ops.
ko...@gmail.com <ko...@gmail.com> #84
to...@gmail.com <to...@gmail.com> #85
ge...@gmail.com <ge...@gmail.com> #86
mc...@gmail.com <mc...@gmail.com> #87
ai...@gmail.com <ai...@gmail.com> #88
wi...@gmail.com <wi...@gmail.com> #89
[Deleted User] <[Deleted User]> #90
gi...@leetix.com <gi...@leetix.com> #91
tw...@gmail.com <tw...@gmail.com> #92
nu...@gmail.com <nu...@gmail.com> #93
la...@gmail.com <la...@gmail.com> #95
[Deleted User] <[Deleted User]> #96
[Deleted User] <[Deleted User]> #97
[Deleted User] <[Deleted User]> #98
wu...@googlemail.com <wu...@googlemail.com> #99
na...@gmail.com <na...@gmail.com> #100
de...@gmail.com <de...@gmail.com> #101
[Deleted User] <[Deleted User]> #102
jo...@gmail.com <jo...@gmail.com> #103
[Deleted User] <[Deleted User]> #104
by...@gmail.com <by...@gmail.com> #105
[Deleted User] <[Deleted User]> #106
It would also fit in with the ethos of the Universal Analytics "upload everything into GA" mentality being promoted. I'm not sure whether read-only access to annotations would be as crucial, but it would still be a help in this case.
I'd imagine it would probably need to sit in a similar position to Content Experiments - as a "management.annotation" resource living underneath the profile, but like experiments requires the profile ID for listing; no "~all" access.
(With v3 of the Analytics APIs, I'd suggest that this bug is miscategorised after the automatic component change from the sole Data Export API to Core Reporting, as it'd be a Management API feature now.)
[Deleted User] <[Deleted User]> #107
[Deleted User] <[Deleted User]> #108
pi...@siteoptimo.com <pi...@siteoptimo.com> #109
da...@broadplace.com <da...@broadplace.com> #110
da...@gmail.com <da...@gmail.com> #111
jo...@oxygenna.com <jo...@oxygenna.com> #112
le...@gmail.com <le...@gmail.com> #113
ju...@gmail.com <ju...@gmail.com> #114
rb...@gmail.com <rb...@gmail.com> #115
ga...@gmail.com <ga...@gmail.com> #116
te...@jewelsite.nl <te...@jewelsite.nl> #117
te...@jewelsite.nl <te...@jewelsite.nl> #118
This would be extremely helpfull for the same reasons everyone else posts, I also can't make a hack to do it in the meanwhile, so again, this would be extremely usefull.
I understand this takes time to build, but a simple 'extract items [from-till || limit=10]' and a 'post item [date][text]' wouldn't be the most complicated piece of code (I think ;) ).
[Deleted User] <[Deleted User]> #119
be...@gmail.com <be...@gmail.com> #120
[Deleted User] <[Deleted User]> #121
ne...@gmail.com <ne...@gmail.com> #122
si...@gmail.com <si...@gmail.com> #123
[Deleted User] <[Deleted User]> #124
da...@holstee.com <da...@holstee.com> #125
go...@gmail.com <go...@gmail.com> #126
ra...@rafaelfurquim.com.br <ra...@rafaelfurquim.com.br> #127
ar...@gmail.com <ar...@gmail.com> #128
sm...@gmail.com <sm...@gmail.com> #129
ti...@screenpages.com <ti...@screenpages.com> #130
If it was possible to create annotations via the Management API then I think that would open up lots of useful possibilities for setting them in a structured way -- for example as part of the process of sending out an email or launching some other form of campaign, or launching a new a/b text, and so on.
Similarly, organisations which use external tools for reporting, dashboards etc would benefit from being able to use annotations within those interfaces. And, indeed, creating annotations from within their interface.
I also wonder whether the annotations system to could be expanded to allow for commentary widgets within the GA dashboards.
As a starting point for the native dashboards, how about a dashboard widget for the existing form of annotations? That might help develop their use.
[Deleted User] <[Deleted User]> #131
ad...@contentfirst.com.au <ad...@contentfirst.com.au> #132
[Deleted User] <[Deleted User]> #133
[Deleted User] <[Deleted User]> #134
[Deleted User] <[Deleted User]> #135
ma...@gmail.com <ma...@gmail.com> #136
[Deleted User] <[Deleted User]> #137
The minute we can write an annotation via the API we'll be integrating it with the CMS we use and into our deployment tools. Incredibly useful to understand how key content changes are affecting traffic and behaviour.
tr...@topspot.com <tr...@topspot.com> #138
vi...@gmail.com <vi...@gmail.com> #139
mc...@digitaloutdoors.co.uk <mc...@digitaloutdoors.co.uk> #140
[Deleted User] <[Deleted User]> #141
in...@gtempaccount.com <in...@gtempaccount.com> #142
[Deleted User] <[Deleted User]> #143
lu...@gmail.com <lu...@gmail.com> #144
st...@bigtripper.net <st...@bigtripper.net> #145
[Deleted User] <[Deleted User]> #146
em...@gmail.com <em...@gmail.com> #147
[Deleted User] <[Deleted User]> #148
do...@gtempaccount.com <do...@gtempaccount.com> #149
do...@gmail.com <do...@gmail.com> #150
[Deleted User] <[Deleted User]> #151
please rank up
cs...@skyscanner.net <cs...@skyscanner.net> #152
ca...@gmail.com <ca...@gmail.com> #153
We need this asap.
ca...@gmail.com <ca...@gmail.com> #154
Would it be possible to get an update from Google regarding this feature request?
ge...@gmail.com <ge...@gmail.com> #155
vl...@gmail.com <vl...@gmail.com> #156
ni...@stmichaelshotel.co.uk <ni...@stmichaelshotel.co.uk> #157
ro...@qwamplify-analytics.com <ro...@qwamplify-analytics.com> #158
am...@gmail.com <am...@gmail.com> #159
sd...@gmail.com <sd...@gmail.com> #160
jo...@thewarehousegroup.co.uk <jo...@thewarehousegroup.co.uk> #161
[Deleted User] <[Deleted User]> #162
[Deleted User] <[Deleted User]> #163
ar...@onlinemarkethink.com <ar...@onlinemarkethink.com> #164
[Deleted User] <[Deleted User]> #165
db...@prismamedia.com <db...@prismamedia.com> #166
Might be interesting to interface with tools like JIRA, Bitbucket.
n....@rai.nl <n....@rai.nl> #167
ma...@googlemail.com <ma...@googlemail.com> #168
ma...@googlemail.com <ma...@googlemail.com> #169
er...@gmail.com <er...@gmail.com> #170
he...@reliefweb.int <he...@reliefweb.int> #171
ju...@gtempaccount.com <ju...@gtempaccount.com> #172
ju...@gtempaccount.com <ju...@gtempaccount.com> #173
ju...@gtempaccount.com <ju...@gtempaccount.com> #174
ma...@acsi.eu <ma...@acsi.eu> #175
ko...@idimension.net <ko...@idimension.net> #176
al...@gmail.com <al...@gmail.com> #177
im...@webdigital.ro <im...@webdigital.ro> #178
rb...@gmail.com <rb...@gmail.com> #180
No kidding, is there a user guide or guidance somewhere to look at ? Is this will be available for Universal Analytics ?
ti...@gmail.com <ti...@gmail.com> #181
ma...@gmail.com <ma...@gmail.com> #182
[Deleted User] <[Deleted User]> #183
xa...@gmail.com <xa...@gmail.com> #184
lf...@nationsphotolab.com <lf...@nationsphotolab.com> #185
ra...@opensooq.com <ra...@opensooq.com> #186
ls...@gmail.com <ls...@gmail.com> #187
mi...@proxyserver.com <mi...@proxyserver.com> #188
Thanks!
je...@gmail.com <je...@gmail.com> #189
It will allow us to automatically annotate when a website has an improvement, tweak, crash, post, news feed, etc.
This ticket has been a very long-standing requested. Do we need to raise another ticket?
an...@gmail.com <an...@gmail.com> #190
ti...@google.com <ti...@google.com>
[Deleted User] <[Deleted User]> #191
lo...@gmail.com <lo...@gmail.com> #192
ja...@gmail.com <ja...@gmail.com> #193
st...@gmail.com <st...@gmail.com> #194
co...@gmail.com <co...@gmail.com> #195
az...@gmail.com <az...@gmail.com> #196
vi...@gmail.com <vi...@gmail.com> #197
[Deleted User] <[Deleted User]> #198
[Deleted User] <[Deleted User]> #199
mi...@gmail.com <mi...@gmail.com> #200
[Deleted User] <[Deleted User]> #201
al...@lesseverything.com <al...@lesseverything.com> #202
da...@gmail.com <da...@gmail.com> #203
ch...@allestelle.com <ch...@allestelle.com> #204
See
So I hope that this can get some attention from the GA team:
->
lo...@firebrand.net <lo...@firebrand.net> #205
fa...@gmail.com <fa...@gmail.com> #206
br...@search-integration.com <br...@search-integration.com> #208
[Deleted User] <[Deleted User]> #209
be...@gmail.com <be...@gmail.com> #210
ch...@templatemonster.me <ch...@templatemonster.me> #211
dj...@gmail.com <dj...@gmail.com> #212
GOOGLE, how many votes does this need for you to action it? I'm serious, how many for you to consider this seriously!
And while we wait for a response, is there an alternate solution using the "custom data" option in Data Import form admin?
se...@watchfinder.co.uk <se...@watchfinder.co.uk> #213
@googleanalytics Please, please, please add the ability to Add Annotations via API
jo...@gmail.com <jo...@gmail.com> #214
@googleanalytics Please, please, please add the ability to Add Annotations via API
tj...@gmail.com <tj...@gmail.com> #215
ch...@gmail.com <ch...@gmail.com> #216
dj...@gmail.com <dj...@gmail.com> #217
_________________________
Daniel Laidler
djlaidler@gmail.com
On Thu, Mar 2, 2017 at 8:53 PM, <buganizer-system@google.com> wrote:
ma...@gmail.com <ma...@gmail.com> #218
pe...@gmail.com <pe...@gmail.com> #219
It would be so amazing to share the annotations automatically between various analytics properties (more company websites - homepage, shop, blog, etc.).
lo...@firebrand.net <lo...@firebrand.net> #220
da...@gmail.com <da...@gmail.com> #221
a kickstarter campaign to cover what must be a huge cost for Google to
develop?!!
On Sat, 8 Apr 2017 at 5:50 AM, <buganizer-system@google.com> wrote:
Cheers,
Mark
Mark Scott
Dakine Interactive
-----------------------
w|
e| mark@markscott.co.nz
c| 021 721 291
p| 03 929 0586 DDI
[Deleted User] <[Deleted User]> #222
[Deleted User] <[Deleted User]> #223
ch...@gmail.com <ch...@gmail.com> #224
[Deleted User] <[Deleted User]> #225
An...@betfred.com <An...@betfred.com> #226
ko...@gmail.com <ko...@gmail.com> #227
da...@gmail.com <da...@gmail.com> #228
[Deleted User] <[Deleted User]> #229
ma...@gmail.com <ma...@gmail.com> #230
Google doesn't care. Shut up and keep throwing Adwords cash at us, suckers.
fa...@gmail.com <fa...@gmail.com> #231
ti...@gmail.com <ti...@gmail.com> #232
jo...@facetinteractive.com <jo...@facetinteractive.com> #233
be...@gmail.com <be...@gmail.com> #234
0x...@gmail.com <0x...@gmail.com> #235
[Deleted User] <[Deleted User]> #236
th...@gmail.com <th...@gmail.com> #237
da...@gmail.com <da...@gmail.com> #238
[Deleted User] <[Deleted User]> #239
[Deleted User] <[Deleted User]> #240
ro...@gmail.com <ro...@gmail.com> #241
h....@gtempaccount.com <h....@gtempaccount.com> #242
da...@gmail.com <da...@gmail.com> #243
gu...@gmail.com <gu...@gmail.com> #244
[Deleted User] <[Deleted User]> #245
ma...@gmail.com <ma...@gmail.com> #246
[Deleted User] <[Deleted User]> #247
za...@gmail.com <za...@gmail.com> #248
[Deleted User] <[Deleted User]> #249
le...@shopdirect.com <le...@shopdirect.com> #250
le...@shopdirect.com <le...@shopdirect.com> #251
be...@thehutgroup.com <be...@thehutgroup.com> #252
mo...@farfetch.com <mo...@farfetch.com> #253
Lu...@chefkoch.de <Lu...@chefkoch.de> #254
star it.
jo...@thewarehousegroup.co.uk <jo...@thewarehousegroup.co.uk> #255
em...@gmail.com <em...@gmail.com> #256
pr...@gmail.com <pr...@gmail.com> #257
he...@jonathonmilne.com <he...@jonathonmilne.com> #258
an...@gtempaccount.com <an...@gtempaccount.com> #259
vi...@gmail.com <vi...@gmail.com> #260
I wanted to share a solution that I thought might help you all. At my org we had this same issue. I commented above a long while back. To fill the gap, we created a form attached to a google sheet. People would submit their annotations via this form. It would be a 150 character description, the date it was associated to if not today, their e-mail address, the website (from a pick list) and the classification for the annotation (e.g. release, outage, campaign, announcement, etc.). Everyone who had access to analytics along with web marketing and our development team were encouraged to simply add everything they wanted to remember. Any activity that they thought they might want to remember the date for that could impact the performance, function or traffic to the site.
Once that data got into the Google sheet, and using additional tabs in the sheet, we wrote simple queries to sort the data and split it by domain. Then all we needed to do was use Google Sheets embed function to put the annotations on a web page that anyone internally could use while performing an analysis.
To our amazement, everyone started to use it. For everything. Dev wrote a simple web hook to submit the form every time they do a release with a link to the details of the release so analysts could see what was happening. The annotation board was bookmarked by everyone too. Executives started using it as a really simple calendar of past events. Even the non-web BI team started using it for their analysis. If desired, you could write directly into the Google Sheet using the Docs API. It's pretty silly what's possible when you have that data in tabular format vs. in the UI.
I like this model better because it gave us more control of what we wanted to capture and didn't require users to have access to Analytics in order to help gather data that could help with site performance analysis.
UNFORTUNATELY, it has a lot of private company information in it and I don't have the time to generalize our solution to share it here for you all but let me know if you have any questions and I will be happy to answer for you here if you are interested in the solution.
Anyways... I hope this gives you some ideas.
Vinny Sosa
mp...@gmail.com <mp...@gmail.com> #261
[Deleted User] <[Deleted User]> #262
ge...@gmail.com <ge...@gmail.com> #263
to...@gmail.com <to...@gmail.com> #264
[Deleted User] <[Deleted User]> #265
ra...@gmail.com <ra...@gmail.com> #266
kr...@rp3agency.com <kr...@rp3agency.com> #267
re...@gmail.com <re...@gmail.com> #268
te...@googlemail.com <te...@googlemail.com> #269
ma...@cak.nl <ma...@cak.nl> #270
ri...@gmail.com <ri...@gmail.com> #271
ab...@gtempaccount.com <ab...@gtempaccount.com> #272
jo...@bark.com <jo...@bark.com> #273
ti...@amicusenterprises.com <ti...@amicusenterprises.com> #274
[Deleted User] <[Deleted User]> #275
sh...@dealerinspire.com <sh...@dealerinspire.com> #276
da...@gmail.com <da...@gmail.com> #277
ma...@gmail.com <ma...@gmail.com> #278
to...@naptown.com <to...@naptown.com> #279
sp...@gmail.com <sp...@gmail.com> #280
ct...@gmail.com <ct...@gmail.com> #281
On Wed, Nov 8, 2017 6:12 AM, buganizer-system@google.com wrote:
Replying to this email means your email address will be shared with the team
that works on this product.
Changed
sp...@gmail.com added
+1 !!
_______________________________
Reference Info: 35352433 Add Annotations update API
component:Public Trackers > Google Analytics > ManagementAPI
status:Assigned
reporter:ic...@gmail.com
assignee:mc...@google.com
type:Feature Request P2 S2
duplicate issue:35352655, 35352700
Triage:Acknowledged
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google
IssueTracker
Caroline TalleyCell: 707.688.0301Email: ctalley87@gmail.com
Please help in this wonderful cause -The Olympic Club Foundation - "to support
programs that share the belief that participation in organized athletics
enriches young lives and develops future community leaders."
vo...@gmail.com <vo...@gmail.com> #282
na...@gmail.com <na...@gmail.com> #283
jo...@gmail.com <jo...@gmail.com> #284
hj...@gmail.com <hj...@gmail.com> #285
za...@gmail.com <za...@gmail.com> #286
mi...@gmail.com <mi...@gmail.com> #287
wi...@gmail.com <wi...@gmail.com> #288
sk...@mcmnet.co.uk <sk...@mcmnet.co.uk> #289
cl...@gmail.com <cl...@gmail.com> #290
ia...@gmail.com <ia...@gmail.com> #291
pm...@openspacetrust.org <pm...@openspacetrust.org> #292
da...@gmail.com <da...@gmail.com> #293
[Deleted User] <[Deleted User]> #294
Plan:
1) we make it popular
2) it goes viral on reddit and hacker news
3) google pays attention and implement this feature
na...@gmail.com <na...@gmail.com> #295
br...@gmail.com <br...@gmail.com> #296
Some fun facts: Since I made my first comment March 29th 2011 (#24), I've moved to a different state, had a 3rd child, and that little guy is now in first grade. He drew this picture the other day.
[Deleted User] <[Deleted User]> #297
I have one kid so far, moved to Singapore a couple of years ago and doing some product management here.
Fun fact: I`ve just read this article about biohacking and started getting curious how far the humanity from being immortal or live at least 200 years :)
[Deleted User] <[Deleted User]> #298
re...@trove.co <re...@trove.co> #299
da...@gmail.com <da...@gmail.com> #300
+1 for the kid to change the world.
lu...@critical.pl <lu...@critical.pl> #301
da...@gmail.com <da...@gmail.com> #302
na...@gmail.com <na...@gmail.com> #303
br...@gmail.com <br...@gmail.com> #304
ja...@gmail.com <ja...@gmail.com> #305
da...@gmail.com <da...@gmail.com> #306
[Deleted User] <[Deleted User]> #307
I am actually curious, what will be the price for flight tickets from Singapore to the US in 2038? ;)
es...@gmail.com <es...@gmail.com> #308
I'm pretty sure we will all be dead before we see this implementation live.
[Deleted User] <[Deleted User]> #309
dr...@gmail.com <dr...@gmail.com> #310
li...@gmail.com <li...@gmail.com> #311
jg...@gmail.com <jg...@gmail.com> #312
I remember when I first commented on this thread, I was so young and full of hope...
ko...@idimension.net <ko...@idimension.net> #313
br...@gmail.com <br...@gmail.com> #314
[Deleted User] <[Deleted User]> #315
Actually, quite curious, where and what I will be doing when this issue got fixed or at least, noticed by Google.
[Deleted User] <[Deleted User]> #316
Which pub are we hitting btw?
ct...@grubhub.com <ct...@grubhub.com> #317
br...@gmail.com <br...@gmail.com> #318
ch...@ons.gov.uk <ch...@ons.gov.uk> #319
[Deleted User] <[Deleted User]> #320
[Deleted User] <[Deleted User]> #321
an...@freshegg.com <an...@freshegg.com> #322
[Deleted User] <[Deleted User]> #323
is...@google.com <is...@google.com>
sh...@actionable.co <sh...@actionable.co> #324
ko...@idimension.net <ko...@idimension.net> #325
vi...@vinoaj.com <vi...@vinoaj.com> #326
ni...@gmail.com <ni...@gmail.com> #327
ju...@qingmang.me <ju...@qingmang.me> #328
[Deleted User] <[Deleted User]> #329
[Deleted User] <[Deleted User]> #330
ma...@streamanalyze.com <ma...@streamanalyze.com> #331
ca...@gmail.com <ca...@gmail.com> #332
le...@gmail.com <le...@gmail.com> #333
da...@gmail.com <da...@gmail.com> #334
[Deleted User] <[Deleted User]> #335
ma...@gmail.com <ma...@gmail.com> #336
ph...@gtempaccount.com <ph...@gtempaccount.com> #337
sa...@gmail.com <sa...@gmail.com> #338
su...@adster.ca <su...@adster.ca> #339
[Deleted User] <[Deleted User]> #340
on...@avast.com <on...@avast.com> #341
[Deleted User] <[Deleted User]> #342
fr...@gmail.com <fr...@gmail.com> #343
na...@gmail.com <na...@gmail.com> #344
be...@gmail.com <be...@gmail.com> #345
dj...@gmail.com <dj...@gmail.com> #346
Imagine, having all "flagged" releases from GTM annotated in GA... EG/ the addition of click event tracking OR a custom dimension would be extremely useful in enterprise solutions (as well as start ups etc)...
On the opposite side of the spectrum, being able to identify an issue created by a GTM publish that suppressed (or over-inflated) data could be made by analysts being able to associate a data anomaly to a GTM publish.
It encourages GTM use and adoption within businesses and automates what is a rare manual process.
dj...@gmail.com <dj...@gmail.com> #347
using events and measurement protocol... I don't like it (cos it's not annotations, damn it)... But some of you could get some use out it... It also may upset the Google devs into action, as this is not what event & MP was built for! hehehe
tj...@gmail.com <tj...@gmail.com> #348
ph...@gtempaccount.com <ph...@gtempaccount.com> #349
gr...@gmail.com <gr...@gmail.com> #350
ad...@intention.al <ad...@intention.al> #351
dm...@internetrix.com.au <dm...@internetrix.com.au> #352
mf...@gmail.com <mf...@gmail.com> #353
I believed that I had turned off email notifications when someone commented
on this issue, but I am still getting them. How do I turn off emails?
Cheers,
Mark
On Fri, 17 Aug 2018 at 00:32, <buganizer-system@google.com> wrote:
sa...@endsleigh.co.uk <sa...@endsleigh.co.uk> #354
ra...@gmail.com <ra...@gmail.com> #355
im...@gmail.com <im...@gmail.com> #356
You can take a look here -->
Invitations request period for the private beta is already open!
Thanks in advance!
Iñaki
tj...@gmail.com <tj...@gmail.com> #357
im...@gmail.com <im...@gmail.com> #358
You're right! That's what I meant. Sorry if it wasn't clear enough. We couldn't find the way to do it the other way around... :P
ig...@gmail.com <ig...@gmail.com> #359
da...@gmail.com <da...@gmail.com> #360
jo...@kogneta.com <jo...@kogneta.com> #361
[Deleted User] <[Deleted User]> #362
Can't believe this hasn't been added yet. I would like to pull campaign launch dates from SFDC and Marketo and bring back into GA.
je...@gmail.com <je...@gmail.com> #363
dw...@ezoic.com <dw...@ezoic.com> #364
ti...@gmail.com <ti...@gmail.com> #365
[Deleted User] <[Deleted User]> #366
bl...@bobit.com <bl...@bobit.com> #367
je...@hcahealthcare.com <je...@hcahealthcare.com> #368
[Deleted User] <[Deleted User]> #369
he...@gmail.com <he...@gmail.com> #370
[Deleted User] <[Deleted User]> #371
all hoping our kids will take over the watch someday.
Welcome on board !
Best Regards,
Aurélien Bard
Technical Director
On Wed, 28 Nov 2018 at 23:00, <buganizer-system@google.com> wrote:
[Deleted User] <[Deleted User]> #372
[Deleted User] <[Deleted User]> #373
w....@hokata.de <w....@hokata.de> #374
[Deleted User] <[Deleted User]> #375
jo...@gmail.com <jo...@gmail.com> #376
pa...@gmail.com <pa...@gmail.com> #377
ma...@gmail.com <ma...@gmail.com> #378
jg...@gmail.com <jg...@gmail.com> #379
st...@lingoda.com <st...@lingoda.com> #380
All I want for Christmas.... :-)
br...@gmail.com <br...@gmail.com> #381
st...@lingoda.com <st...@lingoda.com> #382
jo...@hickies.com <jo...@hickies.com> #383
sa...@gtempaccount.com <sa...@gtempaccount.com> #384
ti...@ideawake.com <ti...@ideawake.com> #385
[Deleted User] <[Deleted User]> #386
gl...@gmail.com <gl...@gmail.com> #387
ma...@gmail.com <ma...@gmail.com> #388
[Deleted User] <[Deleted User]> #389
I mean this is a very special moment for me, I've been dreaming about adding annotations through API for deployments done automatically for 9 years now and imagining how life would be simpler in debugging when/what went wrong with those annotations in there. I really believe we should do something special next year for the big 10 year anniversary.
Considering the widespread use of Analytics and how often this information in annotations would be useful to properly identify issues and fix them and how much time it would save I truly believe this ticket getting solved would create a significant impact on world's productivity as a whole and could even slightly influence the economy of the world.
ba...@gmail.com <ba...@gmail.com> #390
pm...@gmail.com <pm...@gmail.com> #391
dr...@gmail.com <dr...@gmail.com> #392
a lot of peeps are hanging on here :p (been here since 2011)
the longest unresolved ticket/issue/request ever?
let's try on twitter? #annotationsAPI
dr...@gmail.com <dr...@gmail.com> #393
ar...@first10marketing.com <ar...@first10marketing.com> #394
ch...@gmail.com <ch...@gmail.com> #395
ur...@gmail.com <ur...@gmail.com> #396
ma...@gmail.com <ma...@gmail.com> #397
ma...@croissant.io <ma...@croissant.io> #398
ch...@gmail.com <ch...@gmail.com> #399
li...@gmail.com <li...@gmail.com> #400
Like a ritual.
And definitely down for joining the celebration party.
Heck, I even changed two jobs and my kid was born during this time, haha.
wa...@gmail.com <wa...@gmail.com> #401
bh...@google.com <bh...@google.com> #402
We hope to have an update on our plans in this space later in the year.
ko...@idimension.net <ko...@idimension.net> #403
jo...@gmail.com <jo...@gmail.com> #404
+1
go...@gmail.com <go...@gmail.com> #405
lo...@firebrand.net <lo...@firebrand.net> #406
It's incredibly important that you annotate the timeline so we can track cause-and-effect.
No. We have have to do it manually. Yes, "seriously."
ti...@gmail.com <ti...@gmail.com> #407
""/:-.
ne...@gmail.com <ne...@gmail.com> #408
mp...@rent.com <mp...@rent.com> #409
[Deleted User] <[Deleted User]> #410
sq...@gmail.com <sq...@gmail.com> #411
da...@vocus.com.au <da...@vocus.com.au> #412
ME: Just reflecting on all the things I've done in that time. Got married, bought a house, had two kids, many jobs, bought another house
GA: :cricket: :cricket: :cricket:
lu...@gmail.com <lu...@gmail.com> #413
[Deleted User] <[Deleted User]> #414
jy...@oikio.fi <jy...@oikio.fi> #415
da...@gmail.com <da...@gmail.com> #416
[Deleted User] <[Deleted User]> #417
d....@gmail.com <d....@gmail.com> #418
ni...@gmail.com <ni...@gmail.com> #419
sp...@insuit.cz <sp...@insuit.cz> #420
[Deleted User] <[Deleted User]> #421
fo...@gmail.com <fo...@gmail.com> #423
pa...@fcpeuro.com <pa...@fcpeuro.com> #424
[Deleted User] <[Deleted User]> #425
ro...@gmail.com <ro...@gmail.com> #426
[Deleted User] <[Deleted User]> #427
gi...@intarget.net <gi...@intarget.net> #428
[Deleted User] <[Deleted User]> #429
[Deleted User] <[Deleted User]> #430
pi...@typology.com <pi...@typology.com> #431
ha...@nethit.fi <ha...@nethit.fi> #432
[Deleted User] <[Deleted User]> #433
ni...@gmail.com <ni...@gmail.com> #434
le...@doctissimo.fr <le...@doctissimo.fr> #435
ed...@gmail.com <ed...@gmail.com> #436
Hello Google?
It think it is a simple but important feature.
ko...@idimension.net <ko...@idimension.net> #437
da...@vocus.com.au <da...@vocus.com.au> #438
10yrs on the 19th Jan... it's an important date to acknowledge zero action from Google on this!
[Deleted User] <[Deleted User]> #439
sq...@gmail.com <sq...@gmail.com> #440
2. Twitter party #addAnnotationsToGoogleAnalyticsAPI
3. Make sure you link to the URL too
4. Make sure you tag @google
I don't know how many of us are on here but we might be able to raise enough awareness about this issue.
gu...@joingsg.com <gu...@joingsg.com> #441
I hope the initial creator of this issue will live long enough to see the API
ko...@idimension.net <ko...@idimension.net> #442
[Deleted User] <[Deleted User]> #443
[Deleted User] <[Deleted User]> #444
[Deleted User] <[Deleted User]> #445
ko...@idimension.net <ko...@idimension.net> #446
On Thu, Jan 9, 2020 at 12:54 PM <buganizer-system@google.com> wrote:
[Deleted User] <[Deleted User]> #447
ko...@idimension.net <ko...@idimension.net> #448
pf...@google.com <pf...@google.com> #449
jg...@gmail.com <jg...@gmail.com> #450
Though to be honest, I'll be kinda sad to see this party die out.
vi...@gmail.com <vi...@gmail.com> #451
ar...@gmail.com <ar...@gmail.com> #452
pa...@fcpeuro.com <pa...@fcpeuro.com> #453
ra...@alludo.com <ra...@alludo.com> #454
da...@vocus.com.au <da...@vocus.com.au> #455
** STOP! Hammer Time! **
Now that I have your attention, can I draw your attention to the form Google has offered for feedback on this Issue... See
Spend the time and fill this in... My alerts on this issue were like the boy who cried wolf, and I missed the initial send... Thx Google, look forward to hearing from you soon!
ph...@towa.at <ph...@towa.at> #456
da...@hireahelper.com <da...@hireahelper.com> #457
dj...@gmail.com <dj...@gmail.com> #458
☝️
[Deleted User] <[Deleted User]> #460
ko...@idimension.net <ko...@idimension.net> #461
soooooo... this still isn't assigned to anyone... any updates, Google?
de...@jobsmediagroup.com <de...@jobsmediagroup.com> #462
ja...@idealgroupuk.co.uk <ja...@idealgroupuk.co.uk> #463
[Deleted User] <[Deleted User]> #464
ko...@idimension.net <ko...@idimension.net> #465
I'm on the trusted-tester program for the admin API. Is this on the roadmap
at all?
—
Kevin O'Connor, Digital Marketing Analyst
+1 (866) 524.3733
On Thu, Nov 5, 2020 at 5:21 AM <buganizer-system@google.com> wrote:
fe...@gaannotations.com <fe...@gaannotations.com> #466
I'm happy to share with you our new Chrome extension -
Now you can easily:
* Automate your annotations via API
* Add annotation in bulk via CSV
* Arrange all you annotations from a simple dashboard.
And the annotations are more noticeable which makes it much more useful and actionable.
Enjoy :)
be...@patrivia.net <be...@patrivia.net> #467
co...@northcutt.com.c-00ta0fl3.appstempdomain.goog <co...@northcutt.com.c-00ta0fl3.appstempdomain.goog> #468
ko...@idimension.net <ko...@idimension.net> #469
11 years strong! Maybe this issue will make it to adulthood someday! lol
ma...@docsity.com <ma...@docsity.com> #470
bo...@fexy.com <bo...@fexy.com> #471
js...@my.bristol.ac.uk <js...@my.bristol.ac.uk> #472
sa...@gmail.com <sa...@gmail.com> #473
su...@wiris.com <su...@wiris.com> #474
Hello,
Thank you for reaching out! This auto-reply is just to let you know…
We received your email and will get back to you with a (human) response as
soon as possible within our business hours from Monday to Friday.
If you have general questions about our products, please check out
and our documentation and FAQs at
If you have any additional information that you think will help us to
assist you, please feel free to reply to this email.
We look forward to chatting soon!
This email is a service from WIRIS Support. Delivered by Zendesk
<
[QGGMW3-30E7]
--
<
<
<
<
<
<
MathType is now available for
Google Slides! Install it now here
<
su...@wiris.com <su...@wiris.com> #475
Hello,
Thank you for reaching out! This auto-reply is just to let you know…
We received your email and will get back to you with a (human) response as
soon as possible within our business hours from Monday to Friday.
If you have general questions about our products, please check out
and our documentation and FAQs at
If you have any additional information that you think will help us to
assist you, please feel free to reply to this email.
We look forward to chatting soon!
This email is a service from WIRIS Support. Delivered by Zendesk
<
[QGGMW3-30E7]
--
<
<
<
<
<
<
MathType is now available for
Google Slides! Install it now here
<
su...@wiris.com <su...@wiris.com> #476
Hello,
Thank you for reaching out! This auto-reply is just to let you know…
We received your email and will get back to you with a (human) response as
soon as possible within our business hours from Monday to Friday.
If you have general questions about our products, please check out
and our documentation and FAQs at
If you have any additional information that you think will help us to
assist you, please feel free to reply to this email.
We look forward to chatting soon!
This email is a service from WIRIS Support. Delivered by Zendesk
<
[QGGMW3-30E7]
--
<
<
<
<
<
<
MathType is now available for
Google Slides! Install it now here
<
mh...@einsteinmedical.com <mh...@einsteinmedical.com> #477
su...@wiris.com <su...@wiris.com> #478
Hello,
Thank you for reaching out! This auto-reply is just to let you know…
We received your email and will get back to you with a (human) response as
soon as possible within our business hours from Monday to Friday.
If you have general questions about our products, please check out
and our documentation and FAQs at
If you have any additional information that you think will help us to
assist you, please feel free to reply to this email.
We look forward to chatting soon!
This email is a service from WIRIS Support. Delivered by Zendesk
<
[VGGELV-E329]
--
<
<
<
<
<
<
MathType is now available for
Google Slides! Install it now here
<
su...@wiris.com <su...@wiris.com> #479
Hello,
Thank you for reaching out! This auto-reply is just to let you know…
We received your email and will get back to you with a (human) response as
soon as possible within our business hours from Monday to Friday.
If you have general questions about our products, please check out
and our documentation and FAQs at
If you have any additional information that you think will help us to
assist you, please feel free to reply to this email.
We look forward to chatting soon!
This email is a service from WIRIS Support. Delivered by Zendesk
<
[VGGELV-E329]
--
<
<
<
<
<
<
MathType is now available for
Google Slides! Install it now here
<
su...@wiris.com <su...@wiris.com> #480
Hello,
Thank you for reaching out! This auto-reply is just to let you know…
We received your email and will get back to you with a (human) response as
soon as possible within our business hours from Monday to Friday.
If you have general questions about our products, please check out
and our documentation and FAQs at
If you have any additional information that you think will help us to
assist you, please feel free to reply to this email.
We look forward to chatting soon!
This email is a service from WIRIS Support. Delivered by Zendesk
<
[VGGELV-E329]
--
<
<
<
<
<
<
MathType is now available for
Google Slides! Install it now here
<
sq...@gmail.com <sq...@gmail.com> #481
fe...@gmail.com <fe...@gmail.com> #482
su...@wiris.com <su...@wiris.com> #483
Hello,
Thank you for reaching out! This auto-reply is just to let you know…
We received your email and will get back to you with a (human) response as
soon as possible within our business hours from Monday to Friday.
If you have general questions about our products, please check out
and our documentation and FAQs at
If you have any additional information that you think will help us to
assist you, please feel free to reply to this email.
We look forward to chatting soon!
This email is a service from WIRIS Support. Delivered by Zendesk
<
[MMMW4X-DPOY]
--
<
<
<
<
<
<
MathType Add-In for Microsoft
365 is now available. Install it now *here
<
he...@telnyx.com <he...@telnyx.com> #484
What the heck is going on. There are multiple companies writing blog posts about the sheer ridiculousness of this comment thread.
Description
NOTE: This issue tracking system is for developer products only. If you
are not a developer/programmer and have a problem with a Google web site,
please report the problem to the appropriate group. More information can
be found here:
--------------------------------------------------------------------------
Name of API affected:
Analytics Data Export API
Request summary:
Allow annotations to be added/updated via an API.
Use Cases:
When we release new builds/changes to our sites, we'd utilize the API to
add annotations as part of our release.