-
Notifications
You must be signed in to change notification settings - Fork 14
Analytics event tracking
Dave Kaplan edited this page Aug 13, 2019
·
7 revisions
We have these events as of this PR:
-
event:
formSubmission -
formType:
${actionName} Feedback Test
${actionName} can be launch, close, or reopen.
-
event:
formSubmission -
formType:
Audience targeted with a test
-
event:
formSubmission -
formType:
Create ${collectionType}
collectionType can be a Submission Box, Foamcore (Board), Test Collection, etc.
Collection <-- normal collection
Collection::SubmissionBox
Collection::Board
Collection::TestCollection
-
event:
formSubmission -
formType:
Create ${type}, -
parentType:
this.props.parent.isBoard ? 'foamcore' : 'anywhere'
${type} will be one of the item types like Link, Text, etc.
Item::TextItem
Item::FileItem
Item::VideoItem
Item::LinkItem
Item::ExternalImageItem
Item::DataItem <-- data report
Item::QuestionItem <-- in a test collection
-
event:
formSubmission -
formType:
Create Audience
-
event:
formSubmission -
formType:
Create ${ITEM_TYPES.QUESTION}
-
event:
formSubmission -
formType:
Added Payment Method
Using "Preview" from GTM allows you to use the debugger to track your events and see how they are firing, as well as any tags that were triggered (or none):
- While there are some queries we can write against the database to track user behavior, there are some fields google analytics provides that we aren't storing in postgres, such as location, ip, timestamp, etc.
- When traffic gets redirected from one host to another, ie:
shape.space/signuptoprofile.ideo.comand vice-versa. TODO: How are we making sure that the whole flow is tracked from the source to its destination?
- Curious to know how data card items work? Here's a spreadsheet.
