--- "@context": https://schema.org "@type": TechArticle "@id": https://www.twilio.com/docs/segment/connections/destinations/catalog/actions-attribution#article headline: Attribution (Actions) Destination url: https://www.twilio.com/docs/segment/connections/destinations/catalog/actions-attribution inLanguage: en dateModified: 2026-07-29T16:27:12.000Z author: "@type": Organization name: Twilio Developer Education Team publisher: "@type": Organization name: Twilio --- # Attribution (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 **Attribution (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. * This destination is **Beta.** [Attribution](https://www.attributionapp.com/?utm_source=segmentio\&utm_medium=docs\&utm_campaign=partners) is a multi-touch attribution platform that helps marketers measure and optimize the performance of their marketing campaigns across every channel. Attribution traces every visit, conversion, and revenue dollar back to its source, so marketers can understand what's working and where to invest. This destination is maintained by Attribution. For any issues with the destination, [contact the Attribution Support team](https://docs.attributionapp.com/docs/segment?utm_source=segmentio\&utm_medium=docs\&utm_campaign=partners). ## Benefits of Attribution (Actions) Attribution (Actions) provides the following benefits: * **Flexible mapping**. Map any Segment event to Attribution and customize the conditions under which events are sent. * **Full event coverage**. Page, Identify, Track, Group, Alias, and Screen are all supported through a single mapping. Attribution is fully Segment Spec compatible. * **Simple setup**. Connect with just your Attribution Project ID — no SDK changes required. ## Getting started 1. From the Segment web app, navigate to **Connections > Catalog**, then click **Destinations**. 2. Search for **Attribution (Actions)** in the Destinations Catalog and select it. 3. Click **Configure Attribution (Actions)**. 4. Select the source that will send data to Attribution (Actions) and follow the steps to name your destination. 5. On the **Settings** tab, enter your **Project ID**, then save. Segment validates the Project ID with Attribution when you connect. You can find your Project ID in your [Attribution Settings](https://dashboard.attributionapp.com/goto/settings/project-settings). 6. Enable the destination. The **Send Events** preset enables the **Send** mapping for all event types by default, so data starts flowing without additional mapping configuration. ## Destination Settings | Field | Description | Required | Type | | ---------- | ---------------------------- | -------- | ------ | | Project ID | Your Attribution project ID. | Yes | string | ## Available Presets Attribution (Actions) has the following presets | Preset Name | Trigger | Default Action | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------ | -------------- | | Send Events | Event type = "track", Event type = "identify", Event type = "page", Event type = "screen", Event type = "group", Event type = "alias" | Send | ## Available Actions Build your own Mappings. Combine supported [triggers](/docs/segment/connections/destinations/actions/#components-of-a-destination-action) with the following Attribution-supported actions: > \[!NOTE] > > Individual destination instances support a maximum of 5 mappings. * [Send](#send-1) ### Send Send Segment events to Attribution Send is a **Cloud** action. The default Trigger is `type = "track" or type = "page" or type = "screen" or type = "identify" or type = "group" or type = "alias"` | Field | Description | Required | Type | | ------------ | --------------------------------------------------------------------------- | -------- | ------ | | Message ID | The unique identifier for the event message. | Yes | STRING | | Timestamp | The timestamp of the event. If not provided, the current time will be used. | Yes | STRING | | Event Type | The type of event to send to Attribution. | Yes | STRING | | Event Name | The name of the event to send to Attribution. Required for track events. | No | STRING | | Name | The name of the page or screen. | No | STRING | | Properties | The properties of the event to send to Attribution. | No | OBJECT | | Traits | The traits of the user to send to Attribution. | No | OBJECT | | User ID | The ID of the user to send to Attribution. | No | STRING | | Anonymous ID | The anonymous ID of the user to send to Attribution. | No | STRING | | Group ID | The ID of the group to send to Attribution. | No | STRING | | Context | The context of the event to send to Attribution. | No | OBJECT | | Previous ID | The previous ID of the user to send to Attribution. | No | STRING | ### Connection modes Attribution (Actions) is a cloud-mode destination and does not offer a device-mode connection. If you're using one of Segment's libraries like Analytics.js, you don't need a device-mode connection. ## Supported methods Attribution supports the following methods, as specified in the [Segment Spec](/docs/segment/connections/spec). ### Page Send [Page](/docs/segment/connections/spec/page) calls to record pageviews on your website. Each pageview includes the full page URL, including all query parameters, and the referrer. Attribution uses this data to determine the source of each visit. For example: ```js analytics.page() ``` ### Identify Send [Identify](/docs/segment/connections/spec/identify) calls to identify users in Attribution. Each Identify call associates an anonymous user with a user ID. You can optionally include traits, such as `email` or `name`, which Attribution uses to build user profiles. For example: ```js analytics.identify('userId123', { email: 'john.doe@example.com' }); ``` ### Track Send [Track](/docs/segment/connections/spec/track) calls to track custom events. Each event acts as a conversion in Attribution and can include important properties like `revenue`. For example: ```js analytics.track('Order Completed', { orderId: 'orderId123', revenue: 19.50 }); ``` ### Group Send [Group](/docs/segment/connections/spec/group) calls to identify accounts or organizations in Attribution. For example: ```js analytics.group('groupId123', { name: 'Initech' }); ``` ### Alias Send [Alias](/docs/segment/connections/spec/alias) calls to tie a user's anonymous ID to their established user ID or merge two existing users. For example: ```js analytics.alias('previousId', 'userId123') ``` ### Screen Send [Screen](/docs/segment/connections/spec/screen) calls to record screen views in your mobile app. Attribution attaches each screen view to the user's profile as part of their activity history. For example: ```js analytics.screen('Home') ```