Woopra Destination

Segment makes it easy to send your data to Woopra (and lots of other destinations). Once you've tracked your data through our open source libraries we'll translate and route your data to Woopra in the format they understand. Learn more about how to use Woopra with Segment.

Our Woopra destination code is all open-source on GitHub if you want to check it out: Javascript, Server.

Getting Started

When you toggle on Woopra in Segment, this is what happens:

  • Our CDN is updated within 5-10 minutes. Then our snippet will start asynchronously loading Woopra’s javascript onto your page. This means you should remove Woopra’s snippet from your page.
  • Woopra will start automatically collecting data on your site.

Woopra is supported on client-side and server-side.


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.

Note: .page() calls are not supported when sending those events server side or via mobile libraries.


Client Side

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.

Server Side

When you call identify from the server-side languages, we call Woopra’s HTTP REST API with the traits that you pass in.


Woopra does not accept data sent via the Segment group method.


Client Side

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.

Server Side

When you call track from the server-side languages, we call Woopra’s HTTP REST API with the event properties that you pass in.

The default Woopra online timeout is set to 60 seconds, but is adjustable with context.Woopra.timeout.


Tying server side events to client side sessions

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:

  var woopraCookie = window.woopra.cookie;

  // pass this value to your server

Now from the server side, you can attach it to the integrations.Woopra.cookie property:

(Ruby example)

    user_id: '019mr8mf4r',
    event: 'Purchased Item',
    properties: { revenue: 39.95, shipping: '2-day' },
    integrations: {
      Woopra: {
       cookie: <wooTracker value>

This should let Woopra know that this server side event is part of the same session as the client. Important: Make sure Woopra is capitalized!


Split user profiles

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.

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.

Doing so will ensure that duplicate profiles are not created.


You can send computed traits and audiences generated through Segment Personas to this destination as a user property. To learn more about Personas, reach out for a demo.

For user-property destinations, an identify call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property order_completed_last_30days: true, and when this user no longer satisfies we will set that value to false.

When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.

Supported Sources and Connection Modes

📱 Device-based
☁️ Cloud-based

To learn more about about Connection Modes and what dictates which we support, see here.


Segment lets you change these destination settings via your Segment dashboard without having to touch any code.

Domain scope of the Woopra cookie

Name of the cookie to identify the visitor.

Directory scope of the Woopra cookie


This is the name of your project in Woopra.

Download Pause

Time in millisecond to pause the browser to ensure that the event is tracked when visitor clicks on a download url.

Download Tracking

Track downloads on the web page

Hide Campaign

Enable if you want woopra to hide campaign properties from the URL

Idle Timeout

Idle time after which the user is considered offline

Ignore Query URL

Ignores the querystring when you page()

Outgoing Ignore Subdomains

Do not include links to subdomains as outgoing links

Outgoing Pause

Time in millisecond to pause the browser to ensure that the event is tracked when visitor clicks on an outgoing url.

Outgoing Tracking

Track external links clicks on the web page


Ping Woopra servers to ensure that the visitor is still on the webpage

Ping Interval

Time interval in milliseconds between each ping

Questions? Need help? Contact us!
Can we improve this doc?
Email us: docs-feedback@segment.com!