Woopra Connector Setup Guide

This article describes how to set up the Woopra connector.

Connector Actions

Action Name AudienceStream EventStream
Track Event
Update Visitor

Configure Settings

Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector.

After adding the connector, configure the following settings:

Action Settings - Parameters and Options

Click Next or go to the Actions tab. This is where you configure connector actions.

This section describes how to set up parameters and options for each action.

Action - Track Event

Parameters

Parameter Description
Project
Cookie
  • The cookie should be thought of as a device ID.
  • It can also be used for anonymous IDs.
  • Required if no cv_{Visitor Identifier}.
Event
  • The name of the custom event you are tracking.
Timestamp
  • Event timestamp, formatted in milliseconds since Unix epoch that the event occurred. (This can be back-dated, but not in the future.)
Visitor Identifier Type
  • Email, phone number, etc.
  • Required if using Visitor Identifier.
Visitor Identifier
  • An identifier or multiple identifiers to associate with this visitor.
  • For more information on this format, visit: Woopra’s documentation.
  • Required if no cookie.

    Each key must be prepended with cv_: for example, cv_email.

| |Visitor Properties|
  • Properties to set on the visitor's profile.
  • For more information on this format, visit: [Woopra's documentation](https://docs.woopra.com/reference#track-ce).
  • These can be strings, numbers, dates, etc.

    Each key must be prepended with cv_: for example, cv_first_name or cv_title.

| |Event Properties|
  • Properties to set on the custom event.
  • For more information on this format, visit: [Woopra's documentation](https://docs.woopra.com/reference#track-ce).
  • These can be strings, numbers, dates, etc.

    Each key must be prepended with ce_: for example, ce_total_value or ce_purchase_date.

| |Visit Properties|
  • Properties to set on the visit or session.
  • For more information on this format, visit: [Woopra's documentation](https://docs.woopra.com/reference#track-ce).
  • These can be strings, numbers, dates, etc.

    Each key must be prepended with cs_: for example, cs_is_work_computer or cs_mobile_web.

| |Referer|
  • Visit's referring URL.
  • Woopra servers will match the URL against a database of referrers, and will generate a referrer type and search terms when applicable.
  • The referrers data will be automatically accessible from the Woopra interface.
| |IP Address|
  • IP address of the visitor.
  • If defined, it overrides the physical IP address of the connection.
| |Timeout|
  • In milliseconds.
  • Defaults to 30000 (equivalent to 30 seconds), after which the event will expire and the visit will be marked as over, and the visitor as offline.
| |Browser|
  • User's browser.
  • If defined, it overrides the auto-detected browser from the request's user-agent.
  • You can also build your custom user-agent.
| |Operating System|
  • User's operating system.
  • If defined, it overrides the auto-detected browser from the request's user-agent.
  • You can also build your custom user-agent.
| |Device|
  • User's device type.
  • If defined, it overrides the auto-detected device type from user-agent. Common values are mobile, tablet and desktop.
|

Action - Update Visitor

Parameters

Parameter Description
Project
Cookie
  • The cookie should be thought of as a device ID.
  • It can also be used for anonymous IDs.
  • Required if no cv_{Visitor Identifier}.
Visitor Identifier Type
  • Email, phone number, etc.
  • Required if using Visitor Identifier.
Visitor Identifier
  • An identifier or multiple identifiers to associate with this visitor.
  • For more information on this format, visit: Woopra’s documentation.
  • Required if no cookie.

    Each key must be prepended with cv_: for example, cv_email.

| |Visitor Properties|
  • Properties to set on the visitor's profile.
  • These can be strings, numbers, dates, etc. Each key must be prepended with `cv_`: for example, `cv_first_name` or `cv_title`.
  • For more information on this format, visit: [Woopra's documentation](https://docs.woopra.com/reference#track-identify).
|

Was this page helpful?

This page was last updated: January 24, 2020