June (Actions) 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

Available Presets

June (Actions) has the following presets:

Available Actions

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

• Identify

• Page Event

• Group

• Track Event

Identify

Identify user in June

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

Click to show / hide fields

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

Group

Group user in June

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

Click to show / hide fields

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

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.