Merge pull request #2547 from segmentio/develop

Release 22.9.1

Author: pwseg

src/_data/catalog/destinations.yml

@@ -20913,7 +20913,7 @@ items:
   display_name: GraphJSON
   name: GraphJSON
   slug: graphjson
-  hidden: true
+  hidden: false
   regional:
   - us-west
   url: connections/destinations/catalog/graphjson

src/connections/destinations/add-destination.md

@@ -114,6 +114,12 @@ Some destinations do not support having multiple instances connected to the same
 
 You can create unique destination filters for each destination instance connected to the same source.
 
+
+### Connect multiple sources to one instance of a destination
+
+It is not possible to connect multiple instances of one source (for example, two website sources) to the same destination. However, you can create another instance of the destination for the other sources, and click **Copy Settings From Other Destination**  to save yourself time entering the settings values again.
+
+
 ### Connect to more than one instance of a destination using the Config API
 
 You can add multiple instances of a destination using the Segment Config API. See the Segment Config [API documentation](https://reference.segmentapis.com/?version=latest#39ce0439-0969-48c3-ba49-b22a46c41060). If a destination does not support multi-instance, the Config API throws an appropriate error.

src/connections/destinations/catalog/google-analytics/index.md

@@ -195,6 +195,8 @@ For this example these event attributes are sent to Google Universal Analytics:
 | **Event Category** | All       |
 | **Event Action**   | Logged In |
 
+> info ""
+> **Note**: In device-mode only, if you pass `category` to the [`page`](/docs/connections/destinations/catalog/google-analytics/#page-and-screen) call, Segment will use the `category` from `page` instead of setting default **Event Category** to `All`.
 
 And another Track call example, this time with all Google Universal Analytics event parameters:
 

src/connections/destinations/catalog/graphjson/index.md

@@ -1,6 +1,67 @@
 ---
+rewrite: true
 title: 'GraphJSON Destination'
-hidden: true
-published: false
 beta: true
 ---
+[GraphJSON](https://www.graphjson.com/guides/segment){:target="_blank"} provides self-serve analytics to better help you understand your business.
+
+This destination is maintained by GraphJSON. For any issues with the destination, [contact the GraphJSON Support team](mailto:[email protected]).
+
+
+## Getting Started
+
+1. From the Destinations catalog page in the Segment App, click Add Destination.
+2. Search for “GraphJSON” in the Destinations Catalog, and select the “GraphJSON” destination.
+3. Choose which Source should send data to the “GraphJSON” destination.
+4. Go to the `https://graphjson.com/dashboard/integrations/segment`, find and copy the “API key”.
+5. Enter the “API Key” in the “GraphJSON” destination settings in Segment.
+6. Go to `https://graphjson.com/dashboard/integrations/segment` and finish the setup on the GraphJSON side.
+
+## Supported methods
+
+GraphJSON supports the following methods, as specified in the [Segment Spec](/docs/connections/spec).
+
+### Page
+
+Send [Page](/docs/connections/spec/page) calls to GraphJSON. For example:
+
+```js
+analytics.page()
+```
+
+Segment sends Page calls to GraphJSON as a `pageview`.
+
+
+### Screen
+
+Send [Screen](/docs/connections/spec/screen) calls to GraphJSON. For example:
+
+```obj-c
+[[SEGAnalytics sharedAnalytics] screen:@"Home"];
+```
+
+Segment sends Screen calls to GraphJSON as a `screenview`.
+
+
+### Identify
+
+Send [Identify](/docs/connections/spec/identify) calls to GraphJSON. For example:
+
+```js
+analytics.identify('userId123', {
+  email: '[email protected]'
+});
+```
+
+Segment sends Identify calls to GraphJSON as an `identify` event.
+
+
+### Track
+
+Send [Track](/docs/connections/spec/track) calls to GraphJSON. For example:
+
+```js
+analytics.track('Login Button Clicked')
+```
+
+Segment sends Track calls to GraphJSON as a `track` event.