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
With [Avo](https://avo.app){:target="_blank”} Inspector, data quality is no longer a dream, it’s a workflow.
9
+
With [Avo](https://avo.app){:target="\_blank”} Inspector, data quality is no longer a dream, it’s a workflow.
9
10
10
-
[Inspector](https://www.avo.app/data-observability){:target="_blank”} lets you find, triage, fix, and prevent data quality issues in your product analytics. Launch Inspector to discover all your data quality issues and systematically work towards better data, one resolved issue at a time.
11
+
[Inspector](https://www.avo.app/data-observability){:target="\_blank”} lets you find, triage, fix, and prevent data quality issues in your product analytics. Launch Inspector to discover all your data quality issues and systematically work towards better data, one resolved issue at a time.
11
12
12
13
The Avo Inspector destination automatically extracts event schemas from your product events, sending only the signatures from the connected Segment sources to the Inspector API. **Avo Inspector receives no PII data from your source**.
13
14
14
15

15
16
16
-
17
17
{% include content/plan-grid.md name="actions" %}
18
18
19
-
<!-- Include a brief description of the destination here, along with a link to your website. -->
20
-
21
-
<!-- This include describes the requirement of A.js 2.0 or higher for Actions compatibility, and is required if your destination has a web component. -->
22
-
23
-
<!-- The section below explains how to enable and configure the destination. Include any configuration steps not captured below. For example, obtaining an API key from your platform and any configuration steps required to connect to the destination. →
24
-
25
19
### Track events
26
20
27
21
Currently the Integration only receives `Track` events.
@@ -36,7 +30,7 @@ analytics.track("Login", {
36
30
});
37
31
```
38
32
39
-
This track call is translated into a event signature that is sent to the inspector API
33
+
This track call is translated into a event signature that is sent to the Inspector API
40
34
41
35
```js
42
36
{
@@ -49,9 +43,6 @@ This track call is translated into a event signature that is sent to the inspect
49
43
}
50
44
```
51
45
52
-
53
-
54
-
55
46
## Getting started
56
47
57
48
1. From the Segment web app, click **Catalog**, then click **Destinations**.
@@ -63,14 +54,15 @@ This track call is translated into a event signature that is sent to the inspect
63
54
64
55
{% include components/actions-fields.html %}
65
56
66
-
67
57
## Destination Settings
68
58
69
59
1. Copy the **API Key** from Avo into the field `API Key` in settings.
70
60
71
61
2. Select an environment you'd like the data to go to within Avo. It should reflect from what environment the source is receiving data from. (**Production** / **Development** / **Staging**)
72
62
3.**(Optional):** If you have an event property describing the app release version of your source you can provide it under App Version. By default the destination attempts to extract your app release version from `{context.app.version}` which defaults to `unversioned` if that does not exist. Having accurate app release versions in Avo Inspector will help you identify which releases an issue is impacting, and monitor for regressions in future releases after you’ve resolved the issue.
73
63
64
+

65
+
74
66
## Getting Avo API key
75
67
76
68
Before connecting the segment source to Avo, you will need an api key for your source.
0 commit comments