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: docs/event-studio/tracking-plans/ui/index.md
+9-19Lines changed: 9 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,15 +15,13 @@ A modal will appear on the page, giving you the possibility to quickly create a
15
15
16
16

17
17
18
-
After selecting "Create from scratch" a form will appear on the page. Enter your tracking plan information and click "Create and continue" to navigate to the event specification page.
18
+
After selecting "Create new" a form will appear on the page. Enter your tracking plan information and click "Create and continue" to navigate to the event specification page.
19
19
20
20
:::note
21
-
_The name of your tracking plan must be unique to ensure proper identification and avoid conflicts._
21
+
The name of your tracking plan must be unique to ensure proper identification and avoid conflicts.
This page allows you to create multiple event specifications. You can click on any row to enter the details on this screen, or you can complete the information later.
24
+
The next page allows you to create multiple event specifications. You can click on any row to enter the details on this screen, or you can complete the information later.
27
25
28
26
When clicking on an event specification row, a page will allow you to enter additional information into separate modals:
29
27
@@ -41,23 +39,15 @@ In the image below, you can see an example of a tracking plan. It not only provi
41
39
-**Subscribe**; receive notifications of any changes in the tracking plan
42
40
-**Implement tracking**; automatically generate the code for your tracking plan to be included in your application (to learn more visit [Code Generation - automatically generate code for Snowplow tracking SDKs](/docs/event-studio/snowtype/index.md))
43
41
44
-
*Notes: sharing and subscribing is only available for users registered in Snowplow Console.*
42
+
:::note
43
+
Sharing and subscribing is only available for users registered in Snowplow Console.
44
+
:::
45
45
46
46

If you need to edit a tracking plan at any time, simply select it from the tracking plans listing accessible from the main menu.
51
-
52
-
## Updating existing Tracking Plans for Source Applications
53
-
54
-
Tracking Plans created prior to the release of [Source Applications](/docs/event-studio/source-applications/index.md) in September 2024 will need to be updated to assign Source Applications in which the events will be tracked on. The selected Source Applications will add the relevant application IDs to each of the event specifications in the tracking plan.
Event specifications which contain previously added application IDs will need to be updated to use the identifiers inherited from the Source Applications selected at Tracking Plan level. This process can be done manually but you can reach out to our Support team to help you with that by either logging a request through Snowplow [Console](https://console.snowplowanalytics.com/) or by directly emailing [support@snowplow.io](mailto:support@snowplow.io).
@@ -97,7 +87,7 @@ At the bottom, a button will allow users to confirm the upgrade. One of two thin
97
87
If the new version of the Data Structure introduces incompatibilities with the existing Event Specification instructions, the system will flag the conflicting properties.
98
88
99
89
- The UI will prompt the user to resolve these conflicts before the Event Specification can be upgraded.
100
-
- The conflict resolution UI provides options to the user tp modify or delete each instruction depending on the type of incompatibility:
90
+
- The conflict resolution UI provides options to the user to modify or delete each instruction depending on the type of incompatibility:
101
91
-**Remove conflicting instructions**: If a specific property is no longer present in the new Data Structure.
102
92
-**Modify conflicting instructions**: If a property in the new Data Structure has been changed in an incompatible way (e.g., type change, added/removed enum values, added pattern, etc.).
0 commit comments