Attribution (Actions) Destination

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.

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

Attribution (Actions) has the following presets

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

• 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"

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.

Attribution supports the following methods, as specified in the Segment Spec.

Send 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:

analytics.page()

Send 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:

1
analytics.identify('userId123', {
2
  email: 'john.doe@example.com'
3
});

Send Track calls to track custom events. Each event acts as a conversion in Attribution and can include important properties like revenue. For example:

1
analytics.track('Order Completed', {
2
  orderId: 'orderId123',
3
  revenue: 19.50
4
});

Send Group calls to identify accounts or organizations in Attribution. For example:

1
analytics.group('groupId123', {
2
  name: 'Initech'
3
});

Send Alias calls to tie a user's anonymous ID to their established user ID or merge two existing users. For example:

analytics.alias('previousId', 'userId123')

Send 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:

analytics.screen('Home')