Skip to content

Commit ca9eaf8

Browse files
authored
Update cross-channel-tracking.md
1 parent d4c130a commit ca9eaf8

File tree

1 file changed

+20
-20
lines changed

1 file changed

+20
-20
lines changed

src/guides/how-to-guides/cross-channel-tracking.md

Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -95,18 +95,18 @@ UTM parameters are only used when linking to your site from outside of your doma
9595

9696
UTM parameters contain three essential components:
9797

98-
* **utm\_campaign**: this is the name of your campaign. All marketing activities that support this campaign, needs to have the same utm\_campaign so that downstream analysis to measure performance for this specific campaign can be done off this primary key. (Example: "national-toastday")
98+
* **utm\_campaign**: This is the name of your campaign. All marketing activities that support this campaign, needs to have the same utm\_campaign so that downstream analysis to measure performance for this specific campaign can be done off this primary key. (Example: "national-toastday")
9999

100-
* **utm\_medium**: how the traffic is coming to your site. Is it through email, a display ad, or an online forum? This ensures Segment's downstream analysis can easily see which channel performs the best. (Examples: "email", "paid-display", "paid-social", "organic-social")
100+
* **utm\_medium**: How the traffic is coming to your site. Is it through email, a display ad, or an online forum? This ensures Segment's downstream analysis can easily see which channel performs the best. (Examples: "email", "paid-display", "paid-social", "organic-social")
101101

102-
* **utm\_source**: where is the traffic specifically coming from. You can be specific here. This ensures Segment's downstream analysis can measure which specific source brings the most conversions. (Examples: "twitter", "customer.io" (email tool), "facebook", "adroll")
102+
* **utm\_source**: Where the traffic is specifically coming from. You can be specific here. This ensures Segment's downstream analysis can measure which specific source brings the most conversions. (Examples: "twitter", "customer.io" (email tool), "facebook", "adroll")
103103

104104

105105
With these being optional:
106106

107-
* **utm\_content**: for multiple calls to action on a single page, utm\_content indicates which one. For example, on a website, there may be three different display ads. While the link on each display ad will have the same utm\_campaign, utm\_medium, and utm\_source, the utm\_content will be different. (Examples: "banner", "left-side", "bottom-side")
107+
* **utm\_content**: For multiple calls to action on a single page, utm\_content indicates which one. For example, on a website, there may be three different display ads. While the link on each display ad will have the same utm\_campaign, utm\_medium, and utm\_source, the utm\_content will be different. (Examples: "banner", "left-side", "bottom-side")
108108

109-
* **utm\_term**: this is the parameter suggested for paid search to identify keywords for your ad. If you're using Google Adwords and have enabled "autotagging", then you don't need to worry about this. Otherwise, you can manually pass the keywords from your search terms through this parameter so that you can see which keywords convert the most. Note that this parameter is reserved explicitly for search. (Examples: "toast", "butter", "jam")
109+
* **utm\_term**: This is the parameter suggested for paid search to identify keywords for your ad. If you're using Google Adwords and have enabled "autotagging", then you don't need to worry about this. Otherwise, you can manually pass the keywords from your search terms through this parameter so that you can see which keywords convert the most. Note that this parameter is reserved explicitly for search. (Examples: "toast", "butter", "jam")
110110

111111
If you'd like UTM parameters to persist in subsequent calls, you'll need to manually add those fields in the `context.campaign` object of your event call. For example:
112112

@@ -131,26 +131,26 @@ A marketing campaign is a single marketing message across several platforms, med
131131

132132
Since the marketing campaign is from off-domain to your storefront (on your property or domain), then it's critical to use the proper and consistent UTM params across all of your channels:
133133

134-
* emails
134+
* Emails
135135

136-
* paid acquisition
136+
* Paid acquisition
137137

138-
* guest blog post in partner's newsletter
138+
* Guest blog post in partner's newsletter
139139

140-
* article in the news
140+
* Article in the news
141141

142-
* offline events / in real life / meat space
142+
* Offline events / in real life / meat space
143143

144144

145-
Your UTM parameters would match a pattern such as
145+
Your UTM parameters would match a pattern such as:
146146

147-
* having the same utm\_campaign across all channels
147+
* Having the same utm\_campaign across all channels
148148

149-
* different utm\_source and utm\_medium depending on the channel
149+
* Different utm\_source and utm\_medium depending on the channel
150150

151-
* if you were on paid acquisition, the placement of the display ad would determine what goes in utm\_content
151+
* If you were on paid acquisition, the placement of the display ad would determine what goes in utm\_content
152152

153-
* if you were using paid search, the term would be utm\_term
153+
* If you were using paid search, the term would be utm\_term
154154

155155

156156
An example would be a National Toast Day campaign. This campaign would include emails, paid acquisition (with AdRoll and Facebook Ads), organic social (Twitter), and promotional content on partners' blogs.
@@ -186,11 +186,11 @@ Tracking with JavaScript in the browser has its benefits, such as using browser
186186

187187
If you do move key checkout events to the server side, you will have to manually send the data automatically collected by Segment's client-side JavaScript library to your server. These pieces of tracking data are still important for the following reasons:
188188

189-
* **UTM parameters**: collecting the UTM params will allow you to tie conversion events to your marketing campaign or activities. This is valuable in that you can immediately measure performance and calculate ROI on your campaigns.
189+
* **UTM parameters**: Collecting the UTM params will allow you to tie conversion events to your marketing campaign or activities. This is valuable in that you can immediately measure performance and calculate ROI on your campaigns.
190190

191-
* **IP address**: the IP address can provide location intelligence for your customers. This means you can personalize your shopping experience or engagement emails with inventory that might be more relevant depending on your customers' locations.
191+
* **IP address**: The IP address can provide location intelligence for your customers. This means you can personalize your shopping experience or engagement emails with inventory that might be more relevant depending on your customers' locations.
192192

193-
* **User Agent**: the User Agent will inform you of your customers' preferred device and shopping experience. Are they converting on a mobile web browser? Native app? Or on their laptop?
193+
* **User Agent**: The User Agent will inform you of your customers' preferred device and shopping experience. Are they converting on a mobile web browser? Native app? Or on their laptop?
194194

195195

196196
[Learn how to use`context`](/docs/connections/spec/common/#context) to manually send this information on the server side.
@@ -213,9 +213,9 @@ One of the biggest challenges for brick-and-mortar stores is to measure the impa
213213

214214
For Facebook advertisers, [Facebook Offline Conversions](https://www.facebook.com/business/help/1782327938668950){:target="_blank"} allow you to tie offline conversions to your campaigns. It's important to note that the offline data is labeled to an event set that has been assigned to a Facebook campaign. Here are the two ways to attribute offline conversions to Facebook advertisements:
215215

216-
* uploading offline event data about actions that aren't captured with Facebook Pixel or App Events to Facebook for them to match actions to your Facebook ads
216+
* Uploading offline event data about actions that aren't captured with Facebook Pixel or App Events to Facebook for them to match actions to your Facebook ads
217217

218-
* enable and configure [Segment's Facebook Offline Conversions destination](/docs/connections/destinations/catalog/facebook-offline-conversions/), which automates attributing offline events to your Facebook ads in real-time
218+
* Enable and configure [Segment's Facebook Offline Conversions destination](/docs/connections/destinations/catalog/facebook-offline-conversions/), which automates attributing offline events to your Facebook ads in real-time
219219

220220

221221
[Learn more about the benefits of Segment's Facebook Offline Conversions destination](https://segment.com/blog/facebook-offline-conversions-integration/){:target="_blank"}.

0 commit comments

Comments
 (0)