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.

June (Actions) Destination


Destination Info
  • Accepts Page, Alias, Group, Identify and Track calls.
  • Refer to it as June (Actions) in the Integrations object
  • This integration is partner owned. Please reach out to the partner's support for any issues.
(information)

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(link takes you to an external page) 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

getting-started page anchor
  1. Go to the June settings page(link takes you to an external 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

connection-modes-for-june-actions-destination page anchor

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.


Property nameTypeRequiredDescription
API Keystring
required

Your June API Key


June (Actions) has the following presets

Preset NameTriggerDefault Action
Group CallsEvent type = "group"Group
Page CallsEvent type = "page"Page Event
Identify CallsEvent type = "identify"Identify
Track CallsEvent type = "track"Track Event

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

(information)

Mapping limits per destination

Individual destination instances have support a maximum of 50 mappings.

Identify user in June

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

Property nameTypeRequiredDescription
Anonymous IDSTRING

Optional

An anonymous identifier


User IDSTRING

Optional

The ID associated with the user


TraitsOBJECT

Optional

Traits to associate with the user


TimestampSTRING
required

The timestamp of the event


MessageIdSTRING
required

The Segment messageId

Send a page event to June. Learn more about Events in June(link takes you to an external page)

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

Property nameTypeRequiredDescription
Anonymous IDSTRING

Optional

An anonymous identifier


User IDSTRING

Optional

The ID associated with the user


PropertiesOBJECT

Optional

Page properties


Page NameSTRING

Optional

The name of the page


Context propertiesOBJECT

Optional

Context properties to send with the event


TimestampSTRING
required

The timestamp of the event


MessageIdSTRING

Optional

The Segment messageId

Group user in June

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

Property nameTypeRequiredDescription
Anonymous IDSTRING

Optional

Anonymous id


User IDSTRING

Optional

The ID associated with the user


Group IDSTRING
required

The group id


TraitsOBJECT

Optional

Traits to associate with the group


TimestampSTRING
required

The timestamp of the event


MessageIdSTRING
required

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.

Send an event to June. Learn more about Events in June(link takes you to an external page)

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

Property nameTypeRequiredDescription
Event NameSTRING
required

The event name


Event propertiesOBJECT

Optional

Properties to send with the event


TimestampSTRING
required

The timestamp of the event


Anonymous IDSTRING

Optional

The anonymous ID associated with the user


User IDSTRING

Optional

The ID associated with the user


Context propertiesOBJECT

Optional

Context properties to send with the event


MessageIdSTRING
required

The Segment messageId


Migration from June Classic

migration-from-june-classic page anchor

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.

(information)

Info

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