Analytics
2.1K members online now
2.1K members online now
Dive into multiple domain (Cross/Sub) tracking, implementing Ecommerce and Enhanced Ecommerce, setting up Event tracking, and Universal Analytics code.
 
Guide Me
star_border
Reply

Tracking Community Events on Behalf of Customer

Visitor ✭ ✭ ✭
# 1
Visitor ✭ ✭ ✭

We have a website that displays community events (e.g. festivals, art shows, parades, etc.). Each community event is entered via form on our website. We would like to add Google Analytics tracking to each event when it is created. When the community event is completed, we would like to share the analytic information that we collected (on behalf of the event host) with them.

 

Can someone point us in the right direction to help get us started? We have advanced coding, scripting, and API skills but only moderate Google Analytics skills.

 

Many thanks!

Marked as Best Answer.
Solution
Accepted by topic author Mary S
October 2016

Tracking Community Events on Behalf of Customer

Follower ✭ ✭ ☆
# 2
Follower ✭ ✭ ☆

With your coding skills, the Embed API would a great way to create individual dashboards for your event hosts: https://developers.google.com/analytics/devguides/reporting/embed/v1/

 

You would want server-side authentication so you wouldn't have to give user permissions to all event hosts in GA: https://ga-dev-tools.appspot.com/embed-api/server-side-authorization/

 

As long as analytics is on every page (or as part of the framework/template) as soon as it is created, it shouldn't be too difficult and it sounds like a neat project.

 

The easiest thing to do would probably be to filter the dashboards based on the page path if the event name is available there.

 

If it isn't, another option could be to set a custom dimension (ie. 'eventName') either with on-page code or with the data layer/Tag Manager. Then, you can filter your dashboards to only include data for that custom dimension.

 

Re: Tracking Community Events on Behalf of Customer

Visitor ✭ ✭ ✭
# 3
Visitor ✭ ✭ ✭
The Embed API sounds like a perfect solution to our problem. Thank you for
your suggestion!