Skip to content

Commit bf45cb9

Browse files
stayseesongstayseesong
authored
Merge pull request #5302 from segmentio/unlocking-attribution
Unlocking Attribution source
2 parents a5a1f01 + fb2d7a6 commit bf45cb9

File tree

1 file changed

+120
-2
lines changed
  • src/connections/sources/catalog/cloud-apps/unlocking-attribution

1 file changed

+120
-2
lines changed

‎src/connections/sources/catalog/cloud-apps/unlocking-attribution/index.md

Lines changed: 120 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,122 @@
11
---
2-
title: 'Unlocking Attribution Source'
2+
title: Unlocking Attribution Source
33
hidden: true
4-
---
4+
private: true
5+
---
6+
7+
The [Unlocking Attribution](https://unlockinggrowth.co/products/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} source is a powerful solution designed to model attribution data, aiding marketers in identifying the most effective inbound channels for driving conversions. This documentation will guide you through the process of setting up and utilizing the "Unlocking Attribution" source within your Twilio Segment environment. Unlocking Attribution is built on top of your pre-existing Segment implementation, ensuring you can be up and running in under an hour.
8+
9+
Additionally, it provides a way to bring in critical event and object data from key systems such as:
10+
- Marketo Event Streaming - This ensures that all key events occurring in Marketo are fed in real-time to Segment. These include events such as "Email Sent", "Email Opened", "Link Clicked", etc
11+
- LinkedIn, Twitter, Capterra Paid Media Data - Similar to the Segment-provided Google and Facebook paid media sources, this brings in the paid media spend data for these other paid media networks
12+
- SaaSOptics Object Source - Bringing in object data from SaaSOptics
13+
14+
This source generates both [Events and Objects](/docs/connections/sources). Event data can be streamed into your downstream tools and written to the data warehouse while the Object sources can be written to your data warehouse. This means this data can be used both within the Unlocking Attribution tool itself, or from reporting/analytics tools which read from your data warehouse.
15+
16+
This source is maintained by Unlocking Attribution. For any issues with the source, [contact the Unlocking Attribution team](mailto:[email protected]).
17+
18+
> info ""
19+
> The Unlocking Attribution Source is currently in beta. If you're interested in joining the beta program or have any feedback to help improve the Unlocking Attribution source and its documentation, [let the team know](mailto:[email protected]).
20+
21+
## Getting Started
22+
1. Navigate to **Connections > Catalog** and select the **Sources** tab of the catalog.
23+
2. Search for *Unlocking Attribution* in the Sources Catalog.
24+
3. Select **Unlocking Attribution** and click **Add Source**.
25+
4. Give the Source a nickname.
26+
- The nickname is used as a label in the Segment app, and Segment creates a related schema name in your warehouse. The nickname can be anything, but we recommend using something that reflects the source itself and distinguishes amongst your environments (eg. SourceName_Prod, SourceName_Staging, SourceName_Dev).
27+
5. Enter the configuration settings.
28+
6. Click **Add Source** to save your settings.
29+
7. Navigate to **Settings > Workspace Settings**
30+
8. Select the **Access Management** tab.
31+
7. Select the **Tokens** tab.
32+
8. Click **+ Create Token**.
33+
9. Enter a description such as *Unlocking Attribution*, select **Workspace Owner** and click **Create**.
34+
10. Copy the token that is presented on the screen.
35+
11. Switch to your account in Unlocking Attribution and within the onboarding wizard, paste the token you copied.
36+
12. Click **Connect** and follow the remaining steps within the onboarding wizard.
37+
38+
39+
### Sync
40+
41+
The Unlocking Attribution source is built with a sync component, which means that Unlocking Attribution writes to Segment on a regular basis when modeling is re-performed on your customer data (typically on a daily basis). In the initial sync, all historical modeling is performed and written according to the Collections structure below. The objects are written into a separate schema, corresponding to the source instance's schema name you designated upon creation (for example, `ug_attribution.media_spend_items`).
42+
43+
Segment's sync component uses an upsert API, so the data in your warehouse loaded using sync reflects the latest state of the corresponding resource in Unlocking Attribution. For example, if `conversions.value` goes from `0` to `212` between syncs, on its next sync, that conversion's value will be `212`.
44+
45+
The source syncs and warehouse syncs are independent processes. Source runs pull your data into the Segment Hub, and warehouse runs flush that data to your warehouse. Sources sync with Segment daily. Depending on your Warehouses plan, Segment pushes the Source data to your warehouse on the interval associated with your billing plan.
46+
47+
48+
## Collections
49+
Collections are the groupings of resources that Segment pulls from your source. In your warehouse, each collection gets its own table.
50+
51+
Collection | Type | Description
52+
---------- | ---- | ----------
53+
`conversions` | object | This collection contains each identified conversion event, as configured in Unlocking Attribution and detected by the modeling.
54+
`conversion_touch_lookup` | object | This collection contains a cross-reference between each conversion and all the pre-conversion touches the end-user had.
55+
`touches` | object | A touch is any interaction that a user had leading up to the conversion event. This generally means website visits, but can sometimes have broader definitions, based on the exact implementation.
56+
`media_spend_items` | object | All cost data from the various media platforms is downloaded and stored in the the Media Spend Items and Media Spend Daily Spend collections.
57+
`media_spend_daily_spend` | object | This collection captures the daily spend for each campaign (and is sometimes broken down by Ad Collective or Ad Id).
58+
59+
## Collection Properties
60+
Below are tables outlining the properties included in the collections listed above.
61+
62+
### conversions
63+
64+
Property Name | Description
65+
---------------- | ------------
66+
`id` | The unique ID of the conversion event.
67+
`anonymous_id` | The `anonymous_id` of the user who performed the conversion event.
68+
`user_id` | The `user_id` of the user who performed the conversion event.
69+
`conversiontype` | The name of the conversion event.
70+
`timestamp` | The date and time that the conversion event occurred.
71+
`value` | The value of the conversion event. This is typically revenue.
72+
73+
### conversion_touch_lookup
74+
75+
Property Name | Description
76+
--------------- | ------------
77+
`conversion` | The unique ID of the conversion event.
78+
`touch_id` | The unique ID of the specific touch.
79+
80+
### touches
81+
82+
Property Name | Description
83+
--------------- | -------------
84+
`timestamp` | The time that the touch occurred.
85+
`id` | The unique ID of the touch.
86+
`context_page_url` | The full URL of the page viewed.
87+
`context_page_path` | The path of the page viewed.
88+
`context_page_title` | The title of the page viewed.
89+
`context_page_referrer` | The referrer from where the user clicked from to get to the page.
90+
`context_campaign_source` | The contents of the `utm_source` query parameter in the URL.
91+
`context_campaign_medium` | The contents of the `utm_medium` query parameter in the URL.
92+
`context_campaign_name` | The contents of the `utm_campaign` query parameter in the URL.
93+
`context_campaign_content` | The contents of the `utm_content` query parameter in the URL.
94+
`context_campaign_terms` | The contents of the `utm_terms` query parameter in the URL.
95+
`campaign` | The unique ID of the **Media Spend Item** object which the touch was mapped to.
96+
`search_narrative` | The description of how the touch was mapped to campaign cost data.
97+
98+
99+
### media_spend_items
100+
All cost data from the various media platforms are downloaded and stored in the the Media Spend Items and Media Spend Daily Spend collections. Regardless of the media platform, the data is formatted to have a consistent set of key identifiers and attributes as shown in the table below.
101+
102+
Each row in the Media Spend Items collection represents a unique combination of the 4 key attributes(`campaign_name`,`ad_collective_name`, `campaign_id`, `ad_collective_id`). After matching a touch against a campaign, the `campaign` identifier in the `touches` collection points to a row from this collection.
103+
104+
105+
Property Name | Description
106+
--------------- | --------------
107+
`campaign_name` | The name of the campaign as defined the media platform. In some platforms, this could be derived from the **Category** field or **Campaign Group** field
108+
`campaign_id` | The unique ID of the campaign, as determined by the media platform.
109+
`id` | The unique ID of the item.
110+
`ad_collective_name` | The name of the Ad Collective (also known as Ad Set, or Ad Group across various platforms).
111+
`ad_collective_id` | The unique ID of the Ad Collective. This is set by the paid media platform.
112+
`media_source` | The platform of the media item.
113+
`type` | The type of the media item (Paid, Organic).
114+
115+
116+
### media_spend_daily_spend
117+
118+
Property Name | Description
119+
--------------- | -------------
120+
`campaign` | The unique ID of the `media_spend_items` item, which the spend row corresponds to.
121+
`date_start` | The date of the spending item.
122+
`spend` | The amount spent on that day.

0 commit comments

Comments
 (0)