Skip to content

Commit e3bc603

Browse files
Update event specs containing existing app ids (#1002)
1 parent 145f8cd commit e3bc603

File tree

4 files changed

+13
-3
lines changed

4 files changed

+13
-3
lines changed

docs/understanding-tracking-design/defining-the-data-to-collect-with-data-poducts/index.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -27,8 +27,8 @@ With data products, you can:
2727
- **Event specifications**
2828
* **Name;** a descriptive name for the event
2929
* **Description;** a description to help people understand what action the event is capturing
30-
* **Applications;** the application/s that the event will be tracked on
31-
* ** Triggers;** specific instructions on where the event gets triggered (e.g. when a user clicks the "Add to basket" button)
30+
* **Source Applications;** the source application(s) inherited from the data product containing the Application ID(s) that will be sent with this event
31+
* **Triggers;** specific instructions on where the event gets triggered (e.g. when a user clicks the "Add to basket" button)
3232
* **Event data structure;** the event data structure that this event will validate against as it is processed by your pipeline
3333
* **Entities;** the entities that should be attached to this event (e.g. user, product)
3434
* **Properties;** any specific rules for each property of the event

docs/understanding-tracking-design/defining-the-data-to-collect-with-data-poducts/ui/index.md

+11-1
Original file line numberDiff line numberDiff line change
@@ -46,4 +46,14 @@ In the image below, you can see an example of a data product. It not only provid
4646

4747
![Event specification details](images/event-specification-details.png)
4848

49-
If you need to edit a data product at any time, simply select it from the data products listing accessible from the main menu.
49+
If you need to edit a data product at any time, simply select it from the data products listing accessible from the main menu.
50+
51+
#### Updating existing Data Products following the release of Source Applications
52+
53+
Data Products created prior to the release of [Source Applications](../../organize-data-sources-with-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 data product.
54+
55+
![Updating existing Data Products](images/edit-existing-data-product.png)
56+
57+
Event specifications which contain previously added application IDs will need to be updated to use the identifiers inherited from the Source Applications selected at Data Product 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 our Snowplow [BDP Console](https://console.snowplowanalytics.com/) or by directly emailing [support@snowplow.io](mailto:support@snowplow.io).
58+
59+
![Updating existing Event Specifications](images/edit-existing-event-specification.png)

0 commit comments

Comments
 (0)