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
**Avo lets you find, fix, and prevent data quality issues upstream.** World class data and product teams at companies like Fender, IKEA, Wolt use Avo to guarantee event data quality upstream, so they can focus on building great user experiences. With Avo you get reliable data with less effort, by moving from reactive damage control to proactive data management and addressing your data quality issues at the source, where the data is created.
8
+
**Avo lets you find, fix, and prevent data quality issues upstream.** World class data and product teams at companies like Fender, IKEA, and Wolt use Avo to guarantee event data quality upstream, so they can focus on building great user experiences. With Avo you get reliable data with less effort, by moving from reactive damage control to proactive data management and addressing your data quality issues at the source, where the data is created.
9
9
10
10
With [Avo](https://avo.app){:target="\_blank”} Inspector, data quality is no longer a dream, it’s a workflow.
11
11
[Inspector](https://www.avo.app/data-observability){:target="\_blank”} lets you find, triage, fix, and prevent data quality issues in your event based data. Launch Inspector to discover all your data quality issues and systematically work towards better data, one resolved issue at a time.
@@ -51,9 +51,9 @@ This Track call is translated into an event signature that is sent to Avo's Insp
51
51
4. Select a source to connect to Avo (Actions) and click **Next**.
52
52
5. Enter a name for your Avo (Actions) destination and click **Create destination**.
53
53
54
-
## Configure Avo Setup
54
+
## Configure Avo
55
55
56
-
### Getting Avo API key
56
+
### Get the Avo API key
57
57
58
58
Before connecting the Segment source to Avo, you will need an API key for your source.
59
59
@@ -67,7 +67,7 @@ Before connecting the Segment source to Avo, you will need an API key for your s
67
67
68
68
### Configure Destination
69
69
70
-
#### Avo Inspector API Key
70
+
#### Avo Inspector API key
71
71
72
72
You can copy the API key from your source in Avo. The API key allows Avo to map the events from your Segment source to the Avo source, to accurately compare your source’s event schemas to your Tracking Plan in Avo.
73
73
@@ -78,11 +78,11 @@ Avo only generates issues for events in your `Production` environment, but you c
78
78
79
79
#### App Version Property
80
80
81
-
App Version Property is an optional **(but recommended!)** field. Having accurate app release versions in Avo Inspector allows you to see how events change across releases. This helps you identify which releases an issue is impacting, and monitor for regressions in future releases after an issue has been resolved.
81
+
App Version Property is an optional **(but recommended)** field. Having accurate app release versions in Avo Inspector allows you to see how events change across releases. This helps you identify which releases an issue is impacting, and monitor for regressions in future releases after an issue has been resolved.
82
82
83
83
Without app versions, the inspector has no way of differentiating between old and new releases, and might surface irrelevant issues based on old releases. Learn more about how Inspector uses releases in [Avo's documentation](https://www.avo.app/docs/inspector/inspector-issues-view#release-and-source-breakdown){:target="\_blank”}.
84
84
85
-
For most mobile sources, Avo automatically fetches the app version from Segment Context. If you have an event property describing the app release version of your source (“E.g “app_version”) you can provide it under App Version.
85
+
For most mobile sources, Avo automatically fetches the app version from Segment Context. If you have an event property describing the app release version of your source (for example, “app_version”) you can provide it under App Version.
86
86
87
87
If you are unsure of whether this applies to your source, or if you don’t know which event property to use, you can proceed with setting up the source and add this information later.
0 commit comments