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
If you are experiencing data loss from your {{ currentIntegration.display_name }} source, you may be experiencing one or more of the following common errors:
7
+
8
+
-**Payload is too large**: If you attempt to send events larger than 32KB per normal API request or batches of events larger than 500KB per request, Segment’s tracking API responds with `400 Bad Request`. Try sending smaller events (or smaller batches) to correct this error.
9
+
10
+
-**Identifier is not present**: Segment's tracking API requires that each payload has a `userId` and/or `anonymousId`. If you send events without either the `userId` or `anonymousId`, Segment's tracking API responds with an `no_user_anon_id` error. Check the event payload and client instrumentation for more details.
11
+
12
+
-**Track event is missing name**: All Track events to Segment must have a name in string format.
13
+
14
+
-**Event dropped during deduplication**: Segment automatically adds a `messageId` field to all payloads and uses this value to deduplicate events. If you're manually setting a `messageId` value, ensure that each event has a unique value.
15
+
16
+
-**Incorrect credentials**: Double check your credentials for your downstream destination(s).
17
+
18
+
-**Destination incompatibility**: Make sure that the destination you are troubleshooting can accept server-side API calls. You can see compatibility information on the [Destination comparison by category](/docs/connections/destinations/category-compare/) page and in the documentation for your specific destination.
19
+
20
+
-**Destination-specific requirements**: Check out the [destination's documentation](/docs/connections/destinations/) to see if there are other requirements for using the method and destination that you're trying to get working.
Copy file name to clipboardExpand all lines: src/connections/sources/catalog/libraries/server/clojure/index.md
+25-27Lines changed: 25 additions & 27 deletions
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ The clojure library lets you record analytics data from your clojure code. The r
10
10
11
11
The library is open-source and was contributed by [CircleCI](https://circleci.com/){:target="_blank"}. You can [check it out on GitHub](https://github.com/circleci/analytics-clj){:target="_blank"}. The clojure library is a wrapper around Segment's [Java library](https://github.com/segmentio/analytics-java){:target="_blank"}.
12
12
13
-
The clojure library (like our other server side libraries) is built for high-performance, so you can use them in your web server controller code. This library uses an internal queue to make calls non-blocking and fast. It also batches messages and flushes asynchronously to our servers.
13
+
The Clojure library (like Segment's other server side libraries) is built for high-performance, so you can use them in your web server controller code. This library uses an internal queue to make calls non-blocking and fast. It also batches messages and flushes asynchronously to Segment's servers.
14
14
15
15
## Getting Started
16
16
@@ -54,19 +54,19 @@ The default initialization settings are production-ready.
54
54
55
55
## Identify
56
56
57
-
`identify` lets you tie a user to their actions and record traits about them. It includes a unique User ID and any optional traits you know about them.
57
+
Identify calls let you tie a user to their actions and record traits about them. It includes a unique User ID and any optional traits you know about them.
58
58
59
-
Segment recommends calling `identify` a single time when the user's account is first created, and only identifying again later when their traits are change.
59
+
Segment recommends calling Identify a single time when the user's account is first created, and only identifying again later when their traits are change.
This call is identifying the user by his unique User ID (the one you know him by in your database) and labeling him with an `email` trait.
68
68
69
-
The `identify` call has the following fields:
69
+
The Identify call has the following fields:
70
70
71
71
<tableclass="api-table">
72
72
<tr>
@@ -79,17 +79,17 @@ The `identify` call has the following fields:
79
79
</tr>
80
80
</table>
81
81
82
-
Find details on the **identify method payload** in our [Spec](/docs/connections/spec/identify/).
82
+
Find details on the **identify method payload** in the [Segment Spec](/docs/connections/spec/identify/).
83
83
84
84
## Track
85
85
86
-
`track` lets you record the actions your users perform. Every action triggers what we call an "event", which can also have associated properties.
86
+
Track calls let you record the actions your users perform. Every action triggers what Segment calls an "event", which can also have associated properties.
87
87
88
88
You'll want to track events that are indicators of success for your site, like **Signed Up**, **Item Purchased** or **Article Bookmarked**.
89
89
90
-
To get started, we recommend tracking just a few important events. You can always add more later!
90
+
To get started, Segment recommends tracking just a few important events. You can always add more later.
This example `track` call tells us that your user just triggered the **Signed Up** event on a "trial" plan.
104
+
This example Track call tells you that your user just triggered the **Signed Up** event on a "trial" plan.
105
105
106
-
`track` event properties can be anything you want to record. In this case, plan type.
106
+
Track event properties can be anything you want to record. In this case, plan type.
107
107
108
-
The `track` call has the following fields:
108
+
The Track call has the following fields:
109
109
110
110
<tableclass="api-table">
111
111
<tr>
@@ -114,19 +114,19 @@ The `track` call has the following fields:
114
114
</tr>
115
115
<tr>
116
116
<td>`event` _String_</td>
117
-
<td>The name of the event you're tracking. We recommend human-readable names like <strong>Song Played</strong> or <strong>Status Updated</strong>.</td>
117
+
<td>The name of the event you're tracking. Segment recommends human-readable names like <strong>Song Played</strong> or <strong>Status Updated</strong>.</td>
118
118
</tr>
119
119
<tr>
120
120
<td>`properties` _Map, optional_</td>
121
121
<td>A map of properties for the event. If the event was <strong>Added to Cart</strong>, it might have properties like <code>price</code> or <code>product</code>.</td>
122
122
</tr>
123
123
</table>
124
124
125
-
Find details on **best practices in event naming** as well as the **`track` method payload** in our [Spec](/docs/connections/spec/track/).
125
+
Find details on **best practices in event naming** as well as the **Track method payload** in the [Segment Spec](/docs/connections/spec/track/).
126
126
127
127
## Group
128
128
129
-
`group` lets you associate an [identified user](/docs/connections/sources/catalog/libraries/server/java/#identify) user with a group. A group could be a company, organization, account, project or team! It also lets you record custom traits about the group, like industry or number of employees.
129
+
Group lets you associate an [identified user](/docs/connections/sources/catalog/libraries/server/java/#identify) user with a group. A group could be a company, organization, account, project or team. It also lets you record custom traits about the group, like industry or number of employees.
130
130
131
131
This is useful for tools like [Intercom](/docs/connections/destinations/catalog/intercom/), [Preact](/docs/connections/destinations/catalog/preact/) and [Totango](/docs/connections/destinations/catalog/totango/), as it ties the user to a **group** of other users.
132
132
@@ -135,7 +135,7 @@ This is useful for tools like [Intercom](/docs/connections/destinations/catalog/
@@ -152,11 +152,11 @@ The `group` call has the following fields:
152
152
</tr>
153
153
</table>
154
154
155
-
Find more details about `group`, including the **`group` payload**, in our [Spec](/docs/connections/spec/group/).
155
+
Find more details about Group, including the **Group payload**, in the [Segment Spec](/docs/connections/spec/group/).
156
156
157
157
## Screen
158
158
159
-
The [`screen`](/docs/connections/spec/screen/) method lets you record whenever a user sees a screen of your mobile app, along with optional extra information about the page being viewed.
159
+
The [Screen](/docs/connections/spec/screen/) method lets you record whenever a user sees a screen of your mobile app, along with optional extra information about the page being viewed.
160
160
161
161
You'll want to record a screen event an event whenever the user opens a screen in your app.
162
162
@@ -166,7 +166,7 @@ Not all services support screen, so when it's not supported explicitly, the scre
@@ -175,7 +175,7 @@ The `screen` call has the following fields:
175
175
</tr>
176
176
<tr>
177
177
<td>`name` _String_</td>
178
-
<td>The webpage name you're tracking. We recommend human-readable names like **Login** or **Register**.</td>
178
+
<td>The webpage name you're tracking. Segment recommends human-readable names like **Login** or **Register**.</td>
179
179
</tr>
180
180
<tr>
181
181
<td>`properties` _Properties, optional_</td>
@@ -185,17 +185,17 @@ The `screen` call has the following fields:
185
185
186
186
## Alias
187
187
188
-
`alias` is how you associate one identity with another. This is an advanced method, but it is required to manage user identities successfully in *some* of our destinations.
188
+
Alias is how you associate one identity with another. This is an advanced method, but it is required to manage user identities successfully in *some* destinations.
189
189
190
190
In [Mixpanel](/docs/connections/destinations/catalog/mixpanel/#alias) it's used to associate an anonymous user with an identified user once they sign up. For [Kissmetrics](/docs/connections/destinations/catalog/kissmetrics/#alias), if your user switches IDs, you can use 'alias' to rename the 'userId'.
191
191
192
-
Example `alias` call:
192
+
Example Alias call:
193
193
194
194
```
195
195
(alias analytics "user-id" "real-id")
196
196
```
197
197
198
-
For more details about `alias`, including the **`alias` call payload**, check out our [Spec](/docs/connections/spec/alias/).
198
+
For more details about Alias, including the **Alias call payload**, check out the [Segment Spec](/docs/connections/spec/alias/).
199
199
200
200
---
201
201
@@ -234,8 +234,6 @@ You can set a custom logger on the client using:
234
234
235
235
1. Double check that you've set up the library correctly.
236
236
237
-
2. Make sure that you're calling one of our API methods once the library is successfully installed—[`identify`](#identify), [`track`](#track), etc.
237
+
2. Make sure that you're calling one of Segment's API methods once the library is successfully installed, like [Identify](#identify) or [Track](#track).
238
238
239
-
240
-
241
-
{% include content/troubleshooting-server-integration.md %}
239
+
{% include content/server-side-troubleshooting.md %}
0 commit comments