https://github.com/MarkEdmondson1234/edmonlytica-server-side-tag
Edmonlytica is a proof of concept for making your own digital analytics stream using GTM Server Side and BigQuery.
https://github.com/MarkEdmondson1234/edmonlytica-server-side-tag
gtm-custom-template gtm-server-side
Last synced: 3 months ago
JSON representation
Edmonlytica is a proof of concept for making your own digital analytics stream using GTM Server Side and BigQuery.
- Host: GitHub
- URL: https://github.com/MarkEdmondson1234/edmonlytica-server-side-tag
- Owner: MarkEdmondson1234
- License: apache-2.0
- Created: 2021-03-30T21:08:17.000Z (almost 4 years ago)
- Default Branch: master
- Last Pushed: 2021-03-31T15:31:12.000Z (almost 4 years ago)
- Last Synced: 2024-10-28T00:25:06.082Z (4 months ago)
- Topics: gtm-custom-template, gtm-server-side
- Language: Smarty
- Homepage: https://code.markedmondson.me/edmondlytica/
- Size: 31.3 KB
- Stars: 2
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- jimsghstars - MarkEdmondson1234/edmonlytica-server-side-tag - Edmonlytica is a proof of concept for making your own digital analytics stream using GTM Server Side and BigQuery. (Smarty)
README
# Edmonlytica - Server Side Tag
Edmonlytica is a proof of concept for making your own digital analytics stream using GTM Server Side and BigQuery. See the blog post for details:
https://code.markedmondson.me/edmondlytica/## Dependencies
This is the server side tag to be imported into GTM Browser Side. It works in conjunction with the [Edmonlytica GTM Server Side Client](https://github.com/MarkEdmondson1234/edmonlytica-server-side-client) and the [Edmonlytica GTM Browser Tag](https://github.com/MarkEdmondson1234/edmonlytica-browser-template), which need to be installed as well to work.
## Functionality
This takes the event data passed to it from the GTM Server Side Client, and does the BigQuery API call to write that event data to BigQuery.
You will need to configure the BigQuery table to have the following schema:
* event: STRING
* referrer: STRING
* ts: STRING
* eventId: STRING
* custom: STRING
* sessionId: STRING
* event_name: STRING
* page: STRING