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
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/woopra/index.md
+14-13Lines changed: 14 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,10 @@
1
1
---
2
2
title: Woopra Destination
3
3
id: 54521fdc25e721e32a72ef05
4
+
cmode-override: true
4
5
---
5
-
Our Woopra destination code is all open-source on GitHub if you want to check it out: [Javascript](https://github.com/segment-integrations/analytics.js-integration-woopra), [Server](https://github.com/segmentio/integration-woopra).
6
+
Segment's Woopra destination code is open-source on GitHub:
@@ -11,26 +13,25 @@ When you enable Woopra in the Segment web app, your changes appear in the Segmen
11
13
12
14
Woopra is supported on client-side and server-side.
13
15
14
-
- - -
15
-
16
16
## Page
17
17
18
-
When you call `.page()` in the browser, we will pass all the properties of the page such as `url`, `referrer`, `path`, and etc. If you pass a `name` in your `.page()` call, we will send that as `title` to Woopra.
18
+
When you call `.page()` in the browser, Segment passes the properties of the page such as `url`, `referrer`, `path`, and etc. If you pass a `name` in your `.page()` call, Segment sends that as `title` to Woopra.
19
19
20
-
*Note*: `.page()` calls are not supported when sending those events server side or using mobile libraries.
20
+
> info ""
21
+
> `.page()` calls are not supported when sending those events server side or using mobile libraries.
21
22
22
23
23
24
## Identify
24
25
25
26
26
27
### Client Side
27
28
28
-
When you call `identify` on analytics.js, we call Woopra's `woopraTracker.addVisitorProperty` for each trait that you pass in. These traits are stored in the Woopra cookie, and will be sent on the next page load.
29
+
When you call `identify` on analytics.js, Segment calls Woopra's `woopraTracker.addVisitorProperty` for each trait that you pass in. These traits are stored in the Woopra cookie, and will be sent on the next page load.
29
30
30
31
31
32
### Server Side
32
33
33
-
When you call `identify` from the server-side languages, we call Woopra's [HTTP REST API](https://docs.woopra.com/reference/intro-http-tracking) with the traits that you pass in.
34
+
When you call `identify` from the server-side languages, Segment calls Woopra's [HTTP REST API](https://docs.woopra.com/reference/intro-http-tracking){:target="_blank"} with the traits that you pass in.
34
35
35
36
36
37
## Group
@@ -43,20 +44,20 @@ Woopra does not accept data sent using the Segment `group` method.
43
44
44
45
### Client Side
45
46
46
-
When you call `track` on analytics.js, we call Woopra's `woopraTracker.pushEvent` with the a single `settings` object where the `event` parameter you pass is set as `settings.name` for the Woopra event.
47
+
When you call `track` on analytics.js, Segment calls Woopra's `woopraTracker.pushEvent` with the a single `settings` object where the `event` parameter you pass is set as `settings.name` for the Woopra event.
47
48
48
49
49
50
### Server Side
50
51
51
-
When you call `track` from the server-side languages, we call Woopra's HTTP REST API with the event properties that you pass in.
52
+
When you call `track` from the server-side languages, Segment calls Woopra's HTTP REST API with the event properties that you pass in.
52
53
53
-
The default Woopra `online`[timeout](https://docs.woopra.com/reference/intro-http-tracking) is set to 60 seconds, but is adjustable with `context.Woopra.timeout`.
54
+
The default Woopra `online`[timeout](https://docs.woopra.com/reference/intro-http-tracking){:target="_blank"} is set to 60 seconds, but is adjustable with `context.Woopra.timeout`.
54
55
55
56
## Features
56
57
57
58
### Tying server side events to client side sessions
58
59
59
-
If you want your server side events to be seen as part of the same "source" or session as your client side events, all you have to do is pass us the `wooTracker` value inside your cookie. Luckily, you can easily retrieve this value by:
60
+
If you want your server side events to be seen as part of the same "source" or session as your client side events, all you have to do is pass the `wooTracker` value inside your cookie. Luckily, you can easily retrieve this value by:
60
61
61
62
```js
62
63
analytics.ready(function(){
@@ -66,7 +67,7 @@ analytics.ready(function(){
66
67
});
67
68
```
68
69
69
-
Now from the serverside, you can attach it to the `integrations.Woopra.cookie` property:
70
+
For server-side integrations, you can attach it to the `integrations.Woopra.cookie` property:
70
71
71
72
(Ruby example)
72
73
@@ -88,7 +89,7 @@ This should let Woopra know that this server side event is part of the same sess
88
89
89
90
### Split user profiles
90
91
91
-
If you are seeing split user profiles, the most likely culprit is that you are calling `.identify()` only on the backend using one of our server side libraries but **NOT** on the client side with `analytics.js`.
92
+
If you are seeing split user profiles, the most likely culprit is that you are calling `.identify()` only on the backend using one of Segment's server side libraries but **NOT** on the client side with `analytics.js`.
92
93
93
94
Calling `.identify()` in the browser will effectively map the `userId` you passed in with the `wooTracker` cookie value. So in the event that you call `.identify()` on the server side first, you **MUST** call `.identify()` on the client side as well to tie the `wooTracker` cookie to that `userId`.
0 commit comments