Skip to contentSkip to navigationSkip to topbar
On this page
Looking for more inspiration?Visit the
(information)
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

PlayerZero Web (Actions)


Destination Info
  • Accepts Page, Alias, Group, Identify and Track calls.
  • Refer to it as PlayerZero Web in the Integrations object
  • This destination is not compatible with Destination Insert Functions.
  • This integration is partner owned. Please reach out to the partner's support for any issues.

PlayerZero(link takes you to an external page) is an application monitoring platform that measures the impact of engineering issues on important product outcomes (for example: successful onboardings, checkouts, or conversions).

The Segment integration for PlayerZero automatically instruments your web application to send engineering and product analytics events to PlayerZero.


Getting started

getting-started page anchor
  1. From the Segment web app, navigate to Connections > Catalog > Destinations.
  2. Under Categories select Destination Actions.
  3. Select PlayerZero Web (Actions), then click Configure PlayerZero Web.
  4. Select an existing Source to connect to PlayerZero Web.
  5. Click the toggle under Enable Destination to enable the destination, and click Save Changes.
  6. PlayerZero collects data from Segment as soon as it arrives. You can set up a View in the PlayerZero dashboard to enable notifications and be alerted when the first high impact issue surfaces.

Property nameTypeRequiredDescription
PlayerZero Project IDstring
required

The Project ID where you want to send data. You can find this ID on the Project Data Collection(link takes you to an external page) page.


PlayerZero Web has the following presets

Preset NameTriggerDefault Action
Track EventEvent type = "track"Track Event
Identify UserEvent type = "identify"Identify User

Build your own Mappings. Combine supported triggers with the following PlayerZero Web-supported actions:

(information)

Mapping limits per destination

Individual destination instances have support a maximum of 50 mappings.

Identify User

identify-user page anchor

Sets the user identity

Identify User is a Web action. The default Trigger is type = "identify"

Property nameTypeRequiredDescription
User IDSTRING

Optional

The user's id


Anonymous IDSTRING

Optional

The user's anonymous id


Display NameSTRING

Optional

The user's name


EmailSTRING

Optional

The user's email


TraitsOBJECT

Optional

The Segment traits to be included as metadata in PlayerZero

Track events

Track Event is a Web action. The default Trigger is type = "track"

Property nameTypeRequiredDescription
Event nameSTRING
required

The name of the event.


PropertiesOBJECT

Optional

A JSON object containing more information about the event.


Segment lets you change these destination settings from the Segment app without having to touch any code.

Property nameTypeRequiredDescription
PlayerZero Project IDstring
required

The Project ID where you want to send data. You can find this ID on the Project Data Collection(link takes you to an external page) page.