# June (Actions) Destination

## Destination Info

* Accepts [Page](/docs/segment/connections/spec/page), [Alias](/docs/segment/connections/spec/alias), [Group](/docs/segment/connections/spec/group), [Identify](/docs/segment/connections/spec/identify), [Track](/docs/segment/connections/spec/track) calls.
* Refer to it as **June (Actions)** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object)
* This integration is **partner owned.** Please reach out to the partner's support for any issues.

> \[!NOTE]
>
> This page is about the June (Actions) Destination. See below for information about other versions of the June destination:
>
> * [June (Classic)](/docs/segment/connections/destinations/catalog/june)

[June](https://june.so/?utm_source=segmentio\&utm_medium=docs\&utm_campaign=partners) 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](mailto:ferruccio@june.so).

## Getting started

1. Go to the [June settings page](https://app.june.so/redirect-to-my-workspace/settings) 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

| Field   | Description       | Required | Type     |
| ------- | ----------------- | -------- | -------- |
| API Key | Your June API Key | Yes      | password |

## Available Presets

June (Actions) has the following presets

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

## Available Actions

Build your own Mappings. Combine supported [triggers](/docs/segment/connections/destinations/actions/#components-of-a-destination-action) with the following June-supported actions:

> \[!NOTE]
>
> Individual destination instances have support a maximum of 50 mappings.

* [Identify](#identify-1)
* [Page Event](#page-event)
* [Group](#group-1)
* [Track Event](#track-event-1)

### Identify

Identify user in June

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

| Field        | Description                       | Required | Type   |
| ------------ | --------------------------------- | -------- | ------ |
| Anonymous ID | An anonymous identifier           | No       | STRING |
| User ID      | The ID associated with the user   | No       | STRING |
| Traits       | Traits to associate with the user | No       | OBJECT |
| Timestamp    | The timestamp of the event        | Yes      | STRING |
| MessageId    | The Segment messageId             | Yes      | STRING |

### Page Event

Send a page event to June. [Learn more about Events in June](https://www.june.so/docs/users/track)

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

| Field              | Description                               | Required | Type   |
| ------------------ | ----------------------------------------- | -------- | ------ |
| Anonymous ID       | An anonymous identifier                   | No       | STRING |
| User ID            | The ID associated with the user           | No       | STRING |
| Properties         | Page properties                           | No       | OBJECT |
| Page Name          | The name of the page                      | No       | STRING |
| Context properties | Context properties to send with the event | No       | OBJECT |
| Timestamp          | The timestamp of the event                | Yes      | STRING |
| MessageId          | The Segment messageId                     | No       | STRING |

### Group

Group user in June

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

| Field        | Description                        | Required | Type   |
| ------------ | ---------------------------------- | -------- | ------ |
| Anonymous ID | Anonymous id                       | No       | STRING |
| User ID      | The ID associated with the user    | No       | STRING |
| Group ID     | The group id                       | Yes      | STRING |
| Traits       | Traits to associate with the group | No       | OBJECT |
| Timestamp    | The timestamp of the event         | Yes      | STRING |
| MessageId    | The Segment messageId              | Yes      | STRING |

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](https://www.june.so/docs/users/track)

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

| Field              | Description                               | Required | Type   |
| ------------------ | ----------------------------------------- | -------- | ------ |
| Event Name         | The event name                            | Yes      | STRING |
| Event properties   | Properties to send with the event         | No       | OBJECT |
| Timestamp          | The timestamp of the event                | Yes      | STRING |
| Anonymous ID       | The anonymous ID associated with the user | No       | STRING |
| User ID            | The ID associated with the user           | No       | STRING |
| Context properties | Context properties to send with the event | No       | OBJECT |
| MessageId          | The Segment messageId                     | Yes      | STRING |

## 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.

> \[!NOTE]
>
> Contact June support if you find features missing from the June (Actions) destination that were available in the classic June destination.