Merge pull request #6003 from avohq/avo-destination-docs

Avo destination docs

Author: forstisabella

src/connections/destinations/catalog/avo/images/api-key.png

@@ -0,0 +1,75 @@
+---
+title: Avo Destination
+id: 65c2465d0d7d550aa8e7e5c6
+beta: true
+hidden: true
+redirect_from: "/connections/destinations/catalog/actions-avo/"
+---
+
+With [Avo](https://avo.app){:target="\_blank”} Inspector, data quality is no longer a dream, it’s a workflow.
+
+[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.
+
+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**.
+
+
+{% include content/plan-grid.md name="actions" %}
+
+## Supported methods
+
+### Track events
+
+The Avo destination supports Track events.
+
+Example of Track call:
+
+```js
+analytics.track("Login", {
+  userName: "John",
+  city: "San Fransisco"
+  age: 32
+});
+```
+
+This Track call is translated into a event signature that is sent to Avo's Inspector API. 
+
+```js
+{
+  "eventName": "Login",
+  "properties": [
+    {"userName": "string"},
+    {"city": "string"}
+    {"age": "integer"}
+  ]
+}
+```
+
+## Getting started
+
+1. From the Segment web app, click **Catalog**, then click **Destinations**.
+2. Find the Destinations Actions item in the left navigation, and click it.
+3. Select Avo from the list of destinations, then click **Add destination**.
+4. Select a source to connect to Avo (Actions) and click **Next**. 
+5. Enter a name for your Avo (Actions) destination and click **Create destination**. 
+
+<!-- The line below renders a table of connection settings (if applicable), Pre-built Mappings, and available actions. -->
+
+{% include components/actions-fields.html %}
+
+## Getting Avo API key
+Before connecting the segment source to Avo, you will need an API key for your source.
+
+1. Create your Avo workspace at avo.app (If you don’t have one already).
+2. From the Avo workspace sidebar, select **Sources**.
+3. Select an existing source or create a new one. (Avo recommends naming your Avo sources the same as your Segment sources, for example "Web", "iOS", "Android")
+   ![Select a source](images/select-source.png)
+4. Click the **Inspector Setup** tab in the Avo source
+5. Copy the API Key
+   ![Copy API key](images/api-key.png)
+
+## Destination settings
+1. Copy the **API Key** from Avo into the field `API Key` in settings.
+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**)
+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.
+
+![Select a source](images/avo-destination.png)