You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ The Snowplow Flutter Tracker is maintained by the Engineering team at Snowplow A
4
4
5
5
We are extremely grateful for all contributions we receive, whether that is reporting an issue or a change to the code which can be made in the form of a pull request.
6
6
7
-
For support requests, please use our community support Discourse forum: https://discourse.snowplowanalytics.com/.
7
+
For support requests, please use our community support Discourse forum: https://discourse.snowplow.io/.
8
8
9
9
## Setting up an Environment
10
10
@@ -16,7 +16,7 @@ You should ensure you are comfortable building and testing the existing release
16
16
17
17
### Creating an issue
18
18
19
-
The project contains an issue template which should help guiding you through the process. However, please keep in mind that support requests should go to our Discourse forum: https://discourse.snowplowanalytics.com/ and not GitHub issues.
19
+
The project contains an issue template which should help guiding you through the process. However, please keep in mind that support requests should go to our Discourse forum: https://discourse.snowplow.io/ and not GitHub issues.
20
20
21
21
It's also a good idea to log an issue before starting to work on a pull request to discuss it with the maintainers. A pull request is just one solution to a problem and it is often a good idea to talk about the problem with the maintainers first.
22
22
@@ -75,6 +75,6 @@ The @snowplowcla bot will guide you through the process.
75
75
76
76
### Community support requests
77
77
78
-
Please do not log an issue if you are asking for support, all of our community support requests go through our Discourse forum: https://discourse.snowplowanalytics.com/.
78
+
Please do not log an issue if you are asking for support, all of our community support requests go through our Discourse forum: https://discourse.snowplow.io/.
79
79
80
80
Posting your problem there ensures more people will see it and you should get support faster than creating a new issue on GitHub. Please do create a new issue on GitHub if you think you've found a bug though!
If using the tracker within a Flutter app for Web, you will also need to import the Snowplow JavaScript Tracker in your `index.html` file. Please load the JS tracker with the Snowplow tag as [described in the official documentation](https://docs.snowplowanalytics.com/docs/collecting-data/collecting-from-own-applications/javascript-trackers/javascript-tracker/javascript-tracker-v3/tracker-setup/loading/). Do not change the global function name `snowplow` that is used to access the tracker – the Flutter APIs assume that it remains the default as shown in documentation.
61
+
If using the tracker within a Flutter app for Web, you will also need to import the Snowplow JavaScript Tracker in your `index.html` file. Please load the JS tracker with the Snowplow tag as [described in the official documentation](https://docs.snowplow.io/docs/collecting-data/collecting-from-own-applications/javascript-trackers/javascript-tracker/javascript-tracker-v3/tracker-setup/loading/). Do not change the global function name `snowplow` that is used to access the tracker – the Flutter APIs assume that it remains the default as shown in documentation.
62
62
63
-
Make sure to use JavaScript tracker version `3.2` or newer. You may also refer to the [example project](https://github.com/snowplow-incubator/snowplow-flutter-tracker/tree/main/example) in the Flutter tracker repository to see this in action.
63
+
Make sure to use JavaScript tracker version `3.5` or newer. You may also refer to the [example project](https://github.com/snowplow-incubator/snowplow-flutter-tracker/tree/main/example) in the Flutter tracker repository to see this in action.
64
64
65
65
### Using the Tracker
66
66
@@ -223,8 +223,8 @@ limitations under the License.
Copy file name to clipboardExpand all lines: android/src/main/kotlin/com/snowplowanalytics/snowplow_tracker/readers/configurations/NetworkConfigurationReader.kt
+8-5Lines changed: 8 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -19,15 +19,18 @@ class NetworkConfigurationReader(values: Map<String, Any>) {
19
19
20
20
val endpoint:String by values
21
21
val method:String? by valuesDefault
22
+
val customPostPath:String? by valuesDefault
22
23
23
24
funtoConfiguration(): NetworkConfiguration {
24
-
if (method !=null) {
25
-
returnNetworkConfiguration(
26
-
endpoint,
27
-
if ("get".equals(method, true)) { HttpMethod.GET } else { HttpMethod.POST }
25
+
val networkConfig:NetworkConfiguration=if (method !=null) {
26
+
NetworkConfiguration(
27
+
endpoint,
28
+
if ("get".equals(method, true)) { HttpMethod.GET } else { HttpMethod.POST }
Copy file name to clipboardExpand all lines: doc/01-getting-started.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Getting started
2
2
3
-
Designing how and what to track in your app is an important decision. Check out our docs about tracking design [here](https://docs.snowplowanalytics.com/docs/understanding-tracking-design/introduction-to-tracking-design/).
3
+
Designing how and what to track in your app is an important decision. Check out our docs about tracking design [here](https://docs.snowplow.io/docs/understanding-tracking-design/introduction-to-tracking-design/).
4
4
5
5
The following steps will guide you through setting up the Flutter tracker in your project and tracking a simple event.
6
6
@@ -16,7 +16,7 @@ This will add a line with the dependency like to your pubspec.yaml:
If using the tracker within a Flutter app for Web, you will also need to import the Snowplow JavaScript Tracker in your `index.html` file. Please load the JS tracker with the Snowplow tag as [described in the official documentation](https://docs.snowplowanalytics.com/docs/collecting-data/collecting-from-own-applications/javascript-trackers/javascript-tracker/javascript-tracker-v3/tracker-setup/loading/). Do not change the global function name `snowplow` that is used to access the tracker – the Flutter APIs assume that it remains the default as shown in documentation.
30
+
If using the tracker within a Flutter app for Web, you will also need to import the Snowplow JavaScript Tracker in your `index.html` file. Please load the JS tracker with the Snowplow tag as [described in the official documentation](https://docs.snowplow.io/docs/collecting-data/collecting-from-own-applications/javascript-trackers/javascript-tracker/javascript-tracker-v3/tracker-setup/loading/). Do not change the global function name `snowplow` that is used to access the tracker – the Flutter APIs assume that it remains the default as shown in documentation.
31
31
32
-
Make sure to use JavaScript tracker version `3.2` or newer. You may also refer to the [example project](https://github.com/snowplow-incubator/snowplow-flutter-tracker/tree/main/example) in the Flutter tracker repository to see this in action.
32
+
Make sure to use JavaScript tracker version `3.5` or newer. You may also refer to the [example project](https://github.com/snowplow-incubator/snowplow-flutter-tracker/tree/main/example) in the Flutter tracker repository to see this in action.
33
33
34
34
## Initialization
35
35
@@ -66,4 +66,4 @@ Visit documentation about [tracking events](03-tracking-events.md) to learn abou
66
66
67
67
Testing that your event tracking is properly configured can be as important as testing the other aspects of your app. It confirms that you are generating the events you expect.
68
68
69
-
We provide two types of pipeline for testing and debugging. [Snowplow Mini](https://docs.snowplowanalytics.com/docs/understanding-your-pipeline/what-is-snowplow-mini/) is especially useful in manual schema and pipeline testing. [Snowplow Micro](https://docs.snowplowanalytics.com/docs/understanding-your-pipeline/what-is-snowplow-micro/) is a minimal pipeline designed to be used as part of your app's automated test suite.
69
+
We provide two types of pipeline for testing and debugging. [Snowplow Mini](https://docs.snowplow.io/docs/understanding-your-pipeline/what-is-snowplow-mini/) is especially useful in manual schema and pipeline testing. [Snowplow Micro](https://docs.snowplow.io/docs/understanding-your-pipeline/what-is-snowplow-micro/) is a minimal pipeline designed to be used as part of your app's automated test suite.
The method returns a `SnowplowTracker` instance. This can be later used for tracking events, or accessing tracker properties. However, all methods provided by the `SnowplowTracker` instance are also available as static functions in the `Snowplow` class but they require passing the tracker namespace as string.
17
16
18
-
The only required attributes of the `Snowplow.createTracker` method are `namespace` used to identify the tracker, and the Snowplow collector `endpoint`. Additionally, one can configure the HTTP method to be used when sending events to the collectorand provide configuration by instantiating classes for `TrackerConfiguration`, `SubjectConfiguration`, or `GdprConfiguration`. The following arguments are accepted by the `Snowplow.createTracker` method:
17
+
The only required attributes of the `Snowplow.createTracker` method are `namespace` used to identify the tracker, and the Snowplow collector `endpoint`. Additionally, one can configure the HTTP method to be used when sending events to the collector, as well as a custom POST path, and provide configuration by instantiating classes for `TrackerConfiguration`, `SubjectConfiguration`, or `GdprConfiguration`. By default, events are sent by POST. The following arguments are accepted by the `Snowplow.createTracker` method:
19
18
20
-
| Attribute | Type | Description |
21
-
|---|---|---|
22
-
|`namespace`|`String`| Tracker namespace to identify the tracker. |
23
-
|`endpoint`|`String`| URI for the Snowplow collector endpoint. |
24
-
|`method`|`Method?`| HTTP method to use. `Method.get` and `Method.post` options are available. |
25
-
|`trackerConfig`|`TrackerConfiguration?`| Configuration of the tracker and the core tracker properties. |
26
-
|`gdprConfig`|`GdprConfiguration?`| Determines the GDPR context that will be attached to all events sent by the tracker. |
27
-
|`subjectConfig`|`SubjectConfiguration?`| Subject information about tracked user and device that is added to events. |
|`namespace`|`String`| Tracker namespace to identify the tracker. |
22
+
|`endpoint`|`String`| URI for the Snowplow collector endpoint. |
23
+
|`method`|`Method?`| HTTP method to use: `Method.get` or `Method.post` (`Method.post` is default). |
24
+
|`customPostPath`|`String?`| Custom POST path. |
25
+
|`trackerConfig`|`TrackerConfiguration?`| Configuration of the tracker and the core tracker properties. |
26
+
|`gdprConfig`|`GdprConfiguration?`| Determines the GDPR context that will be attached to all events sent by the tracker. |
27
+
|`subjectConfig`|`SubjectConfiguration?`| Subject information about tracked user and device that is added to events. |
28
+
29
+
Setting a custom POST path can be useful in avoiding adblockers; it replaces the default "com.snowplowanalytics/snowplow/tp2". Your event collector must also be configured to accept the custom path.
28
30
29
31
## Configuration of tracker properties: `TrackerConfiguration`
30
32
@@ -63,7 +65,7 @@ Some of the properties are only configurable on iOS and Android and are automati
|`colorDepth`|`double?`| The color depth. | ✔ | ✔ | Non-configurable, auto-assigned. ||
65
67
66
-
The configured attributes are mapped to Snowplow event properties described in the [Snowplow Tracker Protocol](https://docs.snowplowanalytics.com/docs/collecting-data/collecting-from-own-applications/snowplow-tracker-protocol/). They are mapped as follows:
68
+
The configured attributes are mapped to Snowplow event properties described in the [Snowplow Tracker Protocol](https://docs.snowplow.io/docs/collecting-data/collecting-from-own-applications/snowplow-tracker-protocol/). They are mapped as follows:
0 commit comments