Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Patch #7984 - extended snowplow analytics #8227

Merged
merged 2 commits into from May 15, 2017

Conversation

ecoron
Copy link
Contributor

@ecoron ecoron commented Mar 17, 2017

  • extends amp-analytics vendor snowplow by adding more possible properties.

Closes #7984.

@googlebot
Copy link

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.


  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If you signed the CLA as a corporation, please let us know the company's name.

@ampprojectbot
Copy link
Member

Hi, ampproject bot here! Here are a list of the owners that can approve your files.

You may leave an issue comment stating "@ampprojectbot retry!" to force me to re-evaluate this Pull Request's status

/to avimehta dvoytenko

  • extensions/amp-analytics/0.1/test/vendor-requests.json
  • extensions/amp-analytics/0.1/vendors.js

For any issues please file a bug at https://github.com/google/github-owners-bot/issues

@ecoron
Copy link
Contributor Author

ecoron commented Mar 17, 2017

I signed it!

@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.

@ecoron
Copy link
Contributor Author

ecoron commented Mar 20, 2017

alternative address is signed too

@googlebot
Copy link

CLAs look good, thanks!

@ecoron
Copy link
Contributor Author

ecoron commented Apr 3, 2017

@ampprojectbot retry!

@jridgewell
Copy link
Contributor

@ecoron
Copy link
Contributor Author

ecoron commented May 15, 2017

i did it, sorry for delay.

@jridgewell jridgewell merged commit 7096240 into ampproject:master May 15, 2017
'tz=${timezone}&aid=${appId}&p=web&tv=${aaVersion}',
'tz=${timezone}&aid=${appId}&p=web&tv=${aaVersion}&' +
'cd=${screenColorDepth}&cs=${documentCharset}&' +
'duid=${clientId}&' +
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

clientId takes a required param as scope (cookie name). this right now throws exception on the analytics-vendors.amp.html example page. @ecoron could you fix that?

/cc @avimehta

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Filed an issue for this: #9383

Copy link
Contributor Author

@ecoron ecoron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, yes i can take a look on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants