Available Data to Send to Segment
User Traits
Once enabled, Attribution can automatically start sending the following data as user traits into Segment for both anonymous and/or identified users:
| User Trait | Description |
|---|---|
| LTV | LTV for the user based on click costs and revenue. |
| First Purchase | Has the user completed a revenue conversion event. |
| Repeat Purchase | Does the user have repeat revenue conversion events. |
| Purchase Count | Number of revenue conversion events. |
| First Touch Time | Timestamp for the user's first touch. |
| First Touch Filter | Filter id for the user's first touch. |
| First Touch Filter Name | The filter name of the user's first touch. |
| First Touch Channel Name | Channel name of the user's first touch. |
| First Touch Source Name | UTM source for the user's first touch. |
| Last Touch Time | Timestamp of the user's last touch before a specific conversion event. |
| Last Touch filter | Filter ID of the user's last touch before a specific conversion event. |
| Last Touch filter name | Filter name of the user's last touch before a specific conversion event. |
| Last Touch UTM medium | UTM medium of the user's last touch before a specific conversion event. |
| Last Touch UTM source | UTM Source of the user's last touch before a specific conversion event. |
| Last Conversion LTV | LTV of the user from the last conversion. Used when users have multiple revenue conversion events. Based on click cost - revenue. |
| Customer Path | Names of the filters of the full customer path before a conversion event. |
| Cost of Clicks | The total cost of clicks for a user. |
| Last Conversion Gclid | The last interaction with GCLID was from a Google Ad a user clicked on before a conversion event. |
| Last Conversion Google Percentage | The attribution percentage is based on an attribution model based on a conversion event. |
| Last Conversion Google LTV | The LTV is based on the latest conversion event for Google based on click cost minus total revenue. |
| Last Conversion Google Attributed LTV | The LTV is based on the latest conversion event for Google based on click cost minus attributed revenue. |
| Traits Last Updated At | The timestamp is when the user traits are updated by Attributin reverse integration. |
Example of the user traits being sent to Segment via an identify call:
If you want to send a user trait from Attribution to Segment that is not listed, reach out to [email protected]
Events
Once enabled, Attribution can automatically start sending the following data as new events into Segment for both anonymous and/or identified users:
| Event | Description |
|---|---|
| All CRM Stage Changes | If you are using Salesforce, Hubspot or any other CRM integration, Attribution can automatically push stage changes as events into Segment. For example, a user moving into 'MQL' can have Attribution fire an event named 'MQL' into Segment. |
| All Track Events | If you are using Attribution tracking events, any tracked events can be sent to Segment with the same name and timestamp. |
| All E-commerce Spec Events | If you are using Shopify as your website. Attribution can send all events based on the e-commerce spec to Segment. Read here for the full list of events . |
If interested, please contact [email protected].
If you have a lot of data in Attribution enabling Segment Reverse integration could result in a lot of identify and/or event calls sent to Segment. This could result in additional charges in Segment, please consult before enabling integration.
Updated 4 months ago