June (Actions) Destination

Destination Info
Partner Owned
  • This integration is partner owned. Please reach out to the partner's support for any issues.

Additional versions of this destination are available

This page is about the June (Actions) Destination. See below for information about other versions of the June destination:

June is a product analytics tool for B2B SaaS companies. June auto-generates reports that focus on how companies use your product.

June maintains this destination. For any issues with the destination, contact the June Support team.

Getting started

  1. Go to the June settings page and click Add your first source. To add more instances of the June Destination, click on the Segment integration card and click on Create new key and copy the key.
  2. From the Segment web app, navigate to Connections > Catalog, and select the Destinations tab in the catalog.
  3. Search for June (Actions) and select it.
  4. Click Configure June (Actions).
  5. Select the source you want to connect the destination to.
  6. Configure your settings.
  7. Click the toggle to enable the destination.

Connection modes for June (Actions) destination

June (Actions) does not offer a device-mode connection. All events generated in a browser or app are sent to June through Segment’s servers.

Destination Settings

Setting Description
API Key Required.

Your June API Key

Available Presets

June (Actions) has the following presets:

Preset Name Trigger Default Action
Group Calls Event type = "group"
Group
Page Calls Event type = "page"
Page Event
Identify Calls Event type = "identify"
Identify
Track Calls Event type = "track"
Track Event

Available Actions

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

Mapping limits per destination

Individual destination instances have support a maximum of 50 mappings.

Identify

Identify user in June

Identify is a Cloud action. The default Trigger is: type = "identify"

Click to show / hide fields

Field Description
Anonymous ID Type: STRING

An anonymous identifier

User ID Type: STRING

The ID associated with the user

Traits Type: OBJECT

Traits to associate with the user

Timestamp* Type: STRING

The timestamp of the event

MessageId* Type: STRING

The Segment messageId

Page Event

Send a page event to June. Learn more about Events in June

Page Event is a Cloud action. The default Trigger is: type = "page"

Click to show / hide fields

Field Description
Anonymous ID Type: STRING

An anonymous identifier

User ID Type: STRING

The ID associated with the user

Properties Type: OBJECT

Page properties

Page Name Type: STRING

The name of the page

Context properties Type: OBJECT

Context properties to send with the event

Timestamp* Type: STRING

The timestamp of the event

MessageId Type: STRING

The Segment messageId

Group

Group user in June

Group is a Cloud action. The default Trigger is: type = "group"

Click to show / hide fields

Field Description
Anonymous ID Type: STRING

Anonymous id

User ID Type: STRING

The ID associated with the user

Group ID* Type: STRING

The group id

Traits Type: OBJECT

Traits to associate with the group

Timestamp* Type: STRING

The timestamp of the event

MessageId* Type: STRING

The Segment messageId

In the default configuration, June (Actions) triggers this action when it receives a Group call.

This action sets or updates the properties of specific groups. Use this when you want to update properties on a June company profile.

Track Event

Send an event to June. Learn more about Events in June

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

Click to show / hide fields

Field Description
Event Name* Type: STRING

The event name

Event properties Type: OBJECT

Properties to send with the event

Timestamp* Type: STRING

The timestamp of the event

Anonymous ID Type: STRING

The anonymous ID associated with the user

User ID Type: STRING

The ID associated with the user

Context properties Type: OBJECT

Context properties to send with the event

MessageId* Type: STRING

The Segment messageId

Migration from June Classic

If you’re already using Segment cloud-mode, you’re not expected to have breaking changes when upgrading to the June (Actions) destination. With the exception of a few new properties added to your events in the new Actions destination, there’s no difference in the data received in June when using either of the June destinations.

You can configure the new destination to point to a different June workspace and connect it to the same source(s) as the Classic destination and manually verify it before fully switching over.

Contact June support if you find features missing from the June (Actions) destination that were available in the classic June destination.

This page was last modified: 06 Dec 2023



Get started with Segment

Segment is the easiest way to integrate your websites & mobile apps data to over 300 analytics and growth tools.
or
Create free account