![]() With a GET request you can only send 2048 characters of data. This is really important to know, because the amount of data can change. They are a request for an invisible image and contain data in query string parameters. Regardless of the hit type, the hits are all formatted in a similar manner. If you are tracking a kiosk, then YOU generate the hits with the measurement protocol. If you are tracking a mobile app then an SDK (either Android or iOS) generates the hits. If you are tracing a website then JavaScript code, named analytics.js, generates the hits. The tracking code variation depends on what you are tracking. Custom timings must be implemented with additional code.Īll hit types are sent to Google Analytics via a tracking code. For example, you can measure the time between when a page loads and when the user clicks a button. If you want to know if people are clicking on social buttons then use this feature! Social interaction tracking must be manually implemented.Ĭustomized user timings: User timings provide a simple way to measure the actual time between two activities. Social interaction hit: A social interaction is whenever a user clicks on a ReTweet button, +1 button, or Like button. You can send all sorts of data related to the transaction including product information (ID, color, sku, etc.) and transactional information (shipping, tax, payment type, etc.) You must manually implement ecommerce tracking to collect transactions. Transactions: A transaction is sent when a user completes an ecommerce transaction. The key is that the user is interacting with content that is on a page or a screen. The action may be clicking on a button, clicking on a link, swiping a screen, etc. You usually trigger an event when the user takes some kind of action. Unlike a pageview which is automatically generated, an event must be manually implemented. It’s used to measure how often a user takes action on a piece of content. Time on Page.Įvents: An event is like a counter. It is used to calculate many other metrics, like Pageviews per Visit and Avg. A pageview is one of the fundamental metrics in digital analytics. Pageviews/Screenviews: A pageview (for web, or screenview for mobile) is usually automatically generated and measures a user viewing a piece of content. ![]() Here are some of the most common hits in Google Analytics: There are many different kinds of hits depending on your analytics tool. ![]() Most hits are actually the request for an invisible image file. If you open a "User Explorer" report, you will see one single App-Instance ID listed.All data is sent using a hit. You can verify this by creating a test property and firing only those example events for a single date. The standard reports will all show 1 single user. So How Many Users will the Example Scenario Create in my Reports? My recommended best practice is still to set the user ID once per authenticated session, but as long as the data is not deleted the User ID will actually persist in this way. As you recall, the User ID was not set in event #3, but it still appears in the data because it persisted on the mobile device. The User ID will persist across sessions on a mobile app automatically. Again, you can learn more about the various identifiers in my post on Setting the User ID. ![]() The User Pseudo ID is different on each device. There are two things to notice in this chart: Here’s an approximation of what these events will look like in BigQuery: Event Number The user closes the app and returns 2 hours later without authenticating again (no User ID is set).įinally, the same user opens your website where she is already authenticated and views the homepage (User ID is set again). The user authenticates and views a second screen (User ID is set to “ItsMyNewDevice”). The user opens your iOS app and views the home screen without being authenticated. Say that a user follows these steps to create 4 events over 3 unique sessions: Let’s walk through a more detailed example. Using the User ID Across Sessions & Platforms If you drill down into “12345” you will see two events, but if you drill down into “abc” you will see all 3 events. This next part can be counterintuitive: The first two events can be attributed to both of these App-instance IDs. In this example, the User Explorer report will show you two App-instance IDs: “12345”, and “abc”. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |