mirror of
https://github.com/noodlapp/noodl-docs.git
synced 2026-01-11 23:02:54 +01:00
Chore/cleanup before open source (#55)
* Chore: Cleanup * Updated some urls to images and removed parts of documentation that is no longer valid * Removal of some documentation that is no longer valid * Removed PDF Export module --------- Co-authored-by: Johan Olsson <johan@noodl.net>
This commit is contained in:
@@ -2,6 +2,7 @@
|
||||
title: Setting up Google Analytics
|
||||
hide_title: true
|
||||
---
|
||||
|
||||
# Setting up Google Analytics
|
||||
|
||||
## What you will learn in this guide
|
||||
@@ -12,11 +13,11 @@ This guide will show you how to add basic tracking with Google Analytics. After
|
||||
|
||||
We will go through the following topics:
|
||||
|
||||
- Beginners guide to Google Analytics
|
||||
- Set up Google Analytics
|
||||
- Set up the Noodl Module
|
||||
- Allow tracking
|
||||
- Next steps
|
||||
- Beginners guide to Google Analytics
|
||||
- Set up Google Analytics
|
||||
- Set up the Noodl Module
|
||||
- Allow tracking
|
||||
- Next steps
|
||||
|
||||
## Beginners guide to Google Analytics
|
||||
|
||||
@@ -55,7 +56,7 @@ Make sure that you are using _Google Analytics 4_ and **NOT** _Universal Analyti
|
||||
|
||||
So what is a **Data Stream**? Simply put, it's a connection that will stream data from your app to Google Analytics. You can have multiple **Data Streams** in your **Property**, but in most cases you will only need one.
|
||||
|
||||
Let's set up our first **Data Stream**. As Noodl outputs Web Apps, we will need to select the [**Web** option](https://support.google.com/analytics/answer/9304153#stream&zippy=%2Cweb). When asked for the URL of the primary website, this needs to be the URL for your app [when it's deployed](/docs/guides/deploy/deploying-an-app-on-sandbox). `example.com` works for testing purposes as well.
|
||||
Let's set up our first **Data Stream**. As Noodl outputs Web Apps, we will need to select the [**Web** option](https://support.google.com/analytics/answer/9304153#stream&zippy=%2Cweb). When asked for the URL of the primary website, this needs to be the URL for your app when it's deployed. `example.com` works for testing purposes as well.
|
||||
|
||||
!> Make sure to disable [_Enhanced Measurement_](https://support.google.com/analytics/answer/9216061), as this might send double page views.
|
||||
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: Scanning for QR Codes in a camera feed
|
||||
hide_title: true
|
||||
---
|
||||
|
||||
# Scanning for QR Codes in a camera feed
|
||||
|
||||
This example enables you to scan a camera feed for Quick Response (QR) Codes and fetch the resulting data in the QR Code. To scan for QR Codes via uploaded images, see the documentation on the [Image QR Scanner](/library/modules/qr-scanner/guides/image-upload).
|
||||
@@ -33,4 +34,4 @@ Since we are using a **Video** node to display the camera feed, you might want t
|
||||
## No camera stream in viewer? HTTP vs. HTTPS
|
||||
|
||||
For security reasons, the camera feed can generally only be accessed through a secure connection, i.e. an URL beginning with <code>https://</code>, and not <code>http://</code>. This means that on some platforms (depending on OS and browser) the camera feed of the **Camera QR Scanner** will not work inside of the Noodl viewer. Furthermore, connecting to http://localhost:8574/ might have the same issue. However, on some platforms localhost is exempted from the rule and the camera works without problems in the viewer.
|
||||
If you run into this problem you will have to deploy to a secure server via <code>https://</code>. The easiest way to do that is to use the [Noodl Sandbox Deploy](/docs/guides/deploy/deploying-an-app-on-sandbox) which uses <code>https://</code> protocols.
|
||||
If you run into this problem you will have to deploy to a secure server via <code>https://</code>.
|
||||
|
||||
Reference in New Issue
Block a user