Wiki source code of Segment Manager

Version 12.1 by Admin on 2020/01/06 16:02
Show last authors
1 {{layout}}
2 {{layout-section ac:type="two_right_sidebar"}}
3 {{layout-cell}}
4
5
6 {{id name="Start ScreenSteps Content"/}}
7 The Targeting Engine is a powerful tool that allows to to quickly and easily define audience **Segments** and target them with specific **Actions**, e.g. target specific ads, display a pop-up, send an email, redirect to another page or site.
8
9 You can target segments by IP Address and User Agent. This functionality can be used to define a set of IP addresses that may be, for example, non-human traffic that you don't want to display paid banner ads to. By defining the target IP addresses and setting the action to serve only house ads, those IP addresses won't be counted as impressions/views/clicks for paid banner advertising. Or you could redirect to a page or a pop-up with a message that the IP address is suspected of being non-human traffic and a number to call if not the case. That IP could then be removed from the target segment.
10
11 The following lesson will provide details on how to use the **Segment Manager**, **Action Manager**, and **Target Engine**.
12
13 === Please Note: ===
14
15 Segments and targeting actions can be applied to both Known and Unknown users.
16
17 If the defined criteria for a target segment doesn't require a user be known, e.g. viewing a particular webpage or section 3 times, as soon as a user meets that criteria by viewing the defined webpage or section 3 times, he/she is included in that segment (whether a known user or not) and the targeting action will occur.
18
19 Also note that both users who fit the criteria for the defined segment as of the effective start date of an action and users who meet the criteria at any time during the effective date range will be targeted.
20
21 === ===
22
23 {{id name="CreateSegment"/}}CREATING A NEW SEGMENTFrom the Segment Manager menu, select Segment Manager:**
24 **
25
26 [[image:attach:segment manager menu.png||width="800"]]
27
28 \\
29
30 You will see a list of existing segments. Click "Create Segment" in the upper right-hand corner.
31
32 [[image:attach:manage segments.png||height="250"]]
33
34 \\
35
36 You'll be taken to a screen allowing you to define a new segment. Give your segment a descriptive name. You can enter a brief description of the segment as well.
37
38 [[image:attach:segment-definion.png||height="250"]]
39
40 \\
41
42 A segment is a group of people. You can define that group based on any number of demographic criteria, ie., "who" the user is, or based on behavioral criteria, ie., "what" the user has done. You can also create an "Account-based Segment." This is typically a group of IP Addresses that define a target company.
43
44 If you click the "First Party" tab, you will have the opportunity to define a segment. Click on the "User" button to define the segment based on demographic characteristics or select Account to define your segment based on an IP address range.
45
46 === ===
47
48 {{id name="CreateDemoSegment"/}}CREATE A DEMOGRAPHIC SEGMENTof your segment based on the demographic questions you have built in your database. You can use any demographic question to define a segment. Or choose Account to define an account-based segment.
49
50 [[image:attach:segment-demos.png||height="250"]]
51
52 If you choose a demographic question that has a multiple choice response, simply click in the target box and start typing one of the responses. ONEcount should pre-populate the box with the response. Multiple responses can be defined for a single question.
53
54 To add multiple demographic questions to a segment, simply click the Add button on the right-hand side and ONEcount will allow you to add another demographic question.
55
56 In this way, you can create a demographic segment of users who are Pediatricians who live in Arizona, for example.
57
58 If you are creating purely a demographic segment, hit "Save" and ONEcount will save your segment. If you would like to add behavioral characteristics to your segment (ie., Peditricians who live in Arizona and have read three articles on diabetes), click on the Behavior tab.
59
60 \\
61
62 [[image:attach:segment-content.png||height="250"]]
63
64 To define behavioral characteristics of your segment, choose a behavior type from the Category pull-down. The sub-category pull-down will change depending on the Category that was chosen. For the target, you can enter keywords in the Target box if the value(s) are free text.
65
66 If the Target values are multiple choice, you can put your cursor in the box, hit back-space, and then start typing possible values. ONEcount will show matching values, just hit enter and ONEcount will add the value to the target.
67
68 You can add multiple values to a single behavioral target; they will be "OR" values, meaning the segment will be true if any of the values is present.
69
70 Define the frequency of the action in the Freq./Days box. This means how many times within the given date range this even has happened, and enter a date range for the given event.
71
72 If you add multiple behavioral criteria to your segment (hit Add) to add more behavioral criteria, be sure to define whether this criteria is AND/OR, meaning, whether this segment will match when both criteria are met (AND), or when either of the criteria is met (OR).
73
74 There is a wide range of behavioral criteria that can be used for behavioral segments:
75
76 **Banner**: Users are selected based on the banner ads they have viewed on your site. The sub-category for Banners is Viewed or Clicked. Target is the name of the banner(s).
77
78 **Content**: Users are selected based on the meta keywords contained on the pages a user visits. The sub-category for Content is Viewed or Clicked. Target is the content keyword.
79
80 **Email**: Users are selected based on the emails (from your ONEcount-integrated ESP or ONEmail) that the user has engaged with. The sub-category for Email is Opened or Clicked. Target is the name or subject of the e-mail campaign.
81
82 **Form**: Users are selected based on the ONEcount form they have engaged with. The sub-category for Form is Completed. Target is the name of the form.
83
84 **Package Transaction**: Users are selected based on the ONEcount package transaction they have executed. The sub-categories for Package Transaction are Subscribed/Purchased, Currently Subscribed, Not Subscribed, Expired, Will Expire, Unsubscribed. The Target is the name of the package.
85
86 **Package Status**: Users are selected based on the status of a package they have purchased or subscribed to. Best when used with a Package Transaction criteria. The sub-categories for Package Status are any of the package Statuses that you've defined in the Package Status section under the Inventory menu in ONEcount. There are no targets for this option.
87
88 **Source Code**: Users are selected based on the source code for any transaction they have executed within ONEcount. The sub-category is Selected. The target is the specific source codes that are used. Possible options are the source codes defined in the Source Code manager under the Inventory section of ONEcount.
89
90 **Web**: Users are selected based on the web URLs that they have visited. The sub-category is Viewed. The target is a URL or URL fragment.
91
92 **Product Transaction**: Users are selected based on products that they have purchased. The sub-categories are Subscribed/Purchased, Currently Subscribed, Not Subscribed and Unsubscribed. The target is the product name.
93
94 **Product Attribute**: Users are selected based on specific attributes of the products they have purchased. The sub-categories are the attributes (ie., category, type, state, etc.) The target is the value of that attribute (ie., blue, edible, New York, etc.) If the sub-category is a multiple-choice list, then your target must be the name of one of those elements of the list. If the sub-category is a free text field, you can enter any value in the target box.
95
96 Once you have defined your First Party (demographic) and Behavioral criteria for your segment, be sure to **HIT SAVE.**
97
98 \\
99
100 (% style="margin-left: 30.0px;" %)
101 ===
102 ===
103
104 {{id name="CreateAccountSegment"/}}
105
106 (% style="margin-left: 30.0px;" %)
107 === CREATE AN ACCOUNT-BASED SEGMENT ===
108
109 (% style="margin-left: 30.0px;" %)
110 target segments by Account – which is IP Address and User Agent. A user agent is any software that retrieves and presents Web content for end users. User agents include Web browsers, media players, and plug-ins that help in retrieving, rendering and interacting with Web content.
111
112 (% style="margin-left: 30.0px;" %)
113 This functionality can be used, among other things, to define a set of IP addresses of invalid/non-human traffic that you don't want to display paid banner ads to. By defining the target IP addresses and setting the action to serve only house ads, those IP addresses won't be counted as impressions/views/clicks for sponsored banner advertising because they won't be served sponsored ads. Or you could redirect to a page or a pop-up with a message that the IP address is suspected of being non-human traffic and a number to call if not the case. That IP could then be removed from the target segment.
114
115 (% style="margin-left: 30.0px;" %)
116 So, in the example above, the segment will include all users coming from IP address xx.xxx.20.80 using Safari **OR** from IP address xx.xxx.145.194 or 24.xxx.xxx.10 using Mozilla 5.0 **OR,** etc...
117
118 (% style="margin-left: 30.0px;" %)
119 Note that only OR logic is used in Account segmenting and that you can enter multiple IP addresses and user agents in each field.
120
121 To create a segment of ALL users, both known and unknown, enter the IP address 1.0.0.0/1. This will include all possible IP addresses and, by extension, all users who visit your site.
122
123 == ==
124
125 {{id name="CreateAction"/}}CREATE AN ACTIONFrom the Segment Manager menu, select Action Manager. This is where you define the action to be taken for a segment, e.g. a website pop-up or ad targeting. Types of available Actions include: Pop-Up, Redirect, Ad Target, Transactional Email
126
127 \\
128
129 [[image:attach:Action-manager menu.png||width="800"]]
130
131 \\
132
133 You'll see a list of Actions that have been previously been created. To create a new Action, click "Create Action" in the upper right.
134
135 \\
136
137 [[image:attach:action-manager.png||height="250"]]
138
139 \\
140
141 You'll be asked to provide a name for your new segment. Make it descriptive. You can also provide a brief description for this action. Click Next.
142
143 \\
144
145 [[image:attach:define-action.png||height="250"]]
146
147 On the next screen, from the Action pull-down, choose the type of action you would like. Again, you have four choices: Ad Target (through Google Ad Manager or DFP), Pop-UP, Transactional Email, or Redirect.
148
149 ===
150 ===
151
152 {{id name="CreateAdAction"/}}
153
154 === **CREATE AN AD ACTION** ===
155
156 Here, we are defining an Ad Target. This will allow ONEcount to tell Google Ad Manager (DFP) what ad to target when a specific user is on your web site. The specific users will be defined in the Segment that you link to this target.
157
158 In the screen below, you'll see the options for an Ad Target. The first two options are Target Domain and Section. These are used to// limit// the scope of this action, not to define it. It's important to understand the difference.
159
160 In content-based targeting, you define a specific page or web site section (or a whole site) to be targeted with a banner or banner campaign. In effect you are saying, whenever someone comes to this section or this web site, show them this banner.
161
162 ONEcount targets ads based on identity. ONEcount is saying in effect, for this specific person (as defined by the Segment linked to this Action), show this ad. Period.
163
164 The Target Domain and Section options are used to limit this behavior. So what we are saying then is that for this specific person (as defined by the Segment linked to this Action) show this ad, but ONLY on these domains and in these specific sections of the site.
165
166 Why would we do that? Generally, this is limitation is used because we want to target a user with one ad campaign on one site, and a different campaign on another site.
167
168 For example, say we have a pediatrician who we want to target with an ad for a skin medicine on our dermatology site, but an ad for a different drug when he visits a site on diabetes.
169
170 [[image:attach:Define-banner-target.png||height="250"]]
171
172 The Target Domain and Section parameters are only required if you want to limit the banner. If you leave them blank, the user will be targeted across all your web sites.
173
174 The last property is the Key/Value pair that you will use to tell Google Ad Manager which banners or Line Items to target at this user. Consult for Google Ad Manager documentation on Key/value pair targeting. You may specify more than one Key/Value pair for this target. This allows Google Ad Manager or DFP to decide which banners to show.
175
176 * In Revive/OpenX, these variables are created under Inventory > Banner > Delivery Options > Add Delivery Limitation > Site-Variable > Add > enter Key and Value variables. These variables are of your choosing and can be text or num
177
178 For example, say you wanted to target users who read stories about high school basketball. You could create a segment of users who viewed content tagged "high school boys basketball." You could then create three Key/Value pairs for the action you link to that segment: one for high school boys basketball, one for high school sports, and one for high school boys sports. You could then use Google Ad Manager or DFP to determine how the user is targeted and the prioritization of each banner.
179
180 NOTE: Prioritization of banners is done in Google Ad Manager (or DFP) based on rules you configure in GAM.
181
182 ===
183 ===
184
185 {{id name="CreatePopupAction"/}}
186
187 === CREATE A POP-UP ACTION ===
188
189 You can also create a pop-up target for your segments. There are two different types of pop-ups that can be defined in the ONEcount Action Manager: A ONEcount pop-up, and a Custom HTML pop-up.
190
191 Choose Pop-Up from the Action pull-down at the top.
192
193 The next two options are Target Domain and Section. These are used to// limit// the scope of this action, not to define it. It's important to understand the difference.
194
195 In content-based targeting, you define a specific page or web site section (or a whole site) to be targeted with a pop-up. In effect you are saying, whenever someone comes to this section or this web site, show them this pop-up.
196
197 ONEcount targets pop-ups based on identity. ONEcount is saying in effect, for this specific person (as defined by the Segment linked to this Action), show this pop-up. Period.
198
199 The Target Domain and Section options are used to limit this behavior. So what we are saying then is that for this specific person (as defined by the Segment linked to this Action) show this pop-up, but ONLY on these domains and in these specific sections of the site.
200
201 Why would we do that? Generally, this is limitation is used because we want to target a user with pop-up campaign on one site, and a different campaign on another site.
202
203 For example, say we have a pediatrician who we want to target with a pop-up for a skin medicine on our dermatology site, but a pop-up for a conference when he visits our site on diabetes.
204
205 The Target Domain and Section parameters are only required if you want to limit the banner. If you leave them blank, the user will be targeted across all your web sites.
206
207 [[image:attach:pop-up-action.png||width="800"]]
208
209 Next we determine the priority of this pop-up relative to other pop-ups that may be targeted at this segment. It's possible that a user is in multiple segments and may be subject to multiple pop-ups. This setting will help ONEcount determine how important this pop-up is relative to other marketing efforts.
210
211 Frequency allows you determine how frequently this pop-up will appear to this user. Options include once, always (on every page load), daily (once per day), weekly, bi-weekly, monthly, or annually.
212
213 Last, define the pop-up.
214
215 ONEcount includes a simple pop-up builder that allows you to build a pop-up with buttons that link out to other actions like forms, web pages, etc.
216
217 Simply add the header or title for your pop-up, and then the text you want to appear in the box. Check the Display Opt out box if you want the pop-up to include an option to prevent future pop-ups. Choose how many action buttons you would like on the pop-up, and define the button text and the link that the user is sent to when they click on the button.
218
219 If you have pop-up code that your web team has built, you can click on the Custom HTML tab and paste your code in the box.
220
221 [[image:attach:custom-popup-box.png||width="800"]]
222
223 Click Next to review your Action definition, and finally Save to save it.
224
225 This is an example of ONEcount's built-in pop-ups:
226
227 (% style="margin-left: 30.0px;" %)
228 [[image:attach:media_1443033012905.png||align="center"]]
229
230 (% style="margin-left: 30.0px;" %)
231 Note that the display opt-out will appear only if checked when creating the pop-up action.
232
233 (% style="margin-left: 30.0px;" %)
234 ===
235 ===
236
237 {{id name="CreateRedirectAction"/}}
238
239 (% style="margin-left: 30.0px;" %)
240 === **CREATE A REDIRECT ACTION** ===
241
242 Choose redirect from the list of Actions. The redirect action is very similar to the Pop-Up action, except that instead of displaying a pop-up message, ONEcount will redirect the user to a URL of your choosing.
243
244 One use case for this might be users who have a subscription that is running out; you could create a segment of users whose subscription expires in the next 10 days, and target that segment with an Action that redirects them to your subscription form when they first come to your site.
245
246 As with pop-up and ad targeting, the Target Domain and Section parameters are optional.
247
248 \\
249
250 (% style="margin-left: 60.0px;" %)
251 [[image:attach:media_1442947217827.png||align="center"]]
252
253 (% style="margin-left: 60.0px;" %)
254 Upon clicking "Next", you'll have an opportunity to review the action and "Save" or go "Back" to make changes.
255
256 (% style="margin-left: 60.0px;" %)
257 Upon clicking "Save", you'll be returned to the "Define action to take" window where you'll see the name of the saved action in the action field. (See below.)
258
259 (% style="margin-left: 60.0px;" %)
260 Click "Next" to continue to Step 4 – Review and Save.
261
262 (% style="margin-left: 60.0px;" %)
263 When a redirect is in effect, the redirect will occur for the specified target segment in the designated domains and sections at the set frequency and priority level. There is user no opt-out option for this action.
264
265 (% style="margin-left: 30.0px;" %)
266 Click "Next" to continue to Step 4 – Review and Save.
267
268 (% style="margin-left: 30.0px;" %)
269 When an ad target is in effect, only those ads specified by Key and Value will display for the specified target segment on the designated domains and sections at the set frequency and priority level. There is user no opt-out option for this action.
270
271 (% style="margin-left: 30.0px;" %)
272 ===
273 ===
274
275 {{id name="CreateEmailAction"/}}
276
277 (% style="margin-left: 30.0px;" %)
278 === CREATE EMAIL ACTION ===
279
280 (% style="margin-left: 30.0px;" %)
281 To send a transactional e-mail to a user, choose Email from the Action pull-down.
282
283 (% style="margin-left: 30.0px;" %)
284 [[image:attach:media_1442946953775.png||align="center"]]
285
286 (% style="margin-left: 30.0px;" %)
287 Upon clicking "Next", you'll have an opportunity to review the action and "Save" or go "Back" to make changes.
288
289 (% style="margin-left: 30.0px;" %)
290 Upon clicking "Save", you'll be returned to the "Define action to take" window where you'll see the name of the saved action in the action field. (See below.)
291
292 (% style="margin-left: 30.0px;" %)
293 Click "Next" to continue to Step 4 – Review and Save.
294
295 (% style="margin-left: 30.0px;" %)
296 [[image:attach:media_1443035194695.png||align="center"]]
297
298 (% style="margin-left: 30.0px;" %)
299 When an email action is in effect, the email will be sent to the specified target segment on the designated domains and sections at the set frequency and priority level. There is user no opt-out option for this action.
300
301 Review and Save
302
303 [[image:attach:media_1446742842763.png||align="center"]]
304
305 Review all of the information for your persona, and click "Save Persona" to save.
306
307 If you wish to make changes, click the "Back" button to move backward through the steps.
308
309 \\
310
311 ==
312 ==
313
314 {{id name="CreateTarget"/}}
315
316 == **CREATE A TARGET: CONNECTING SEGMENTS TO ACTIONS** ==
317
318 So now you have created audience segments based on demographics, actions, or a host of other deterministic criteria. And you've created a handful of actions, including pop-ups, banner targets, transactional e-mails and redirects. How do you put it all together?
319
320 The Target Engine has a very simple task: It connects Segments to Actions. It is pretty easy to use. Simply select Target Engine from the Segment Manager menu,
321
322 \\
323
324 [[image:attach:target-engine-menu.png||width="800"]]
325
326 \\
327
328 \\
329
330 \\
331
332 [[image:attach:target-list.png||width="800"]]
333
334 \\
335
336 \\
337
338 [[image:attach:expanded-target-list.png||width="800"]]
339
340 \\
341
342 \\
343
344 \\
345
346 \\
347
348 [[image:attach:target-definition.png||width="800"]]
349
350 \\
351
352 \\
353
354 \\
355
356 [[image:attach:target-review-and-save.png||width="800"]]
357
358 \\
359
360 \\
361
362 \\
363
364 \\
365
366 \\
367
368 [[image:attach:target-segment-action.png||height="250"]]
369
370 \\
371
372 \\
373
374 \\
375
376 \\
377
378
379
380 {{id name="End ScreenSteps Content"/}}
381 {{/layout-cell}}
382
383 {{layout-cell}}
384 {{panel title="Search All Documentation:"}}
385
386
387 {{livesearch/}}
388 {{/panel}}
389
390 {{panel title="Search USER OPERATIONS Documentation:"}}
391
392
393 {{pagetreesearch rootPage="User Operations - Managing Your Data"/}}
394 {{/panel}}
395
396 {{panel title="On this page:"}}
397
398
399 {{toc/}}
400 {{/panel}}
401
402 {{panel title="More USER OPERATIONS Documentation"}}
403 {{expand}}
404 **Add Users
405 **
406
407 (% style="margin-left: 60.0px;" %)
408
409
410 (% style="margin-left: 60.0px;" %)
411 [[Preparing for Data Import>>doc:Getting Started - Preparing for Data Import]]
412
413 (% style="margin-left: 60.0px;" %)
414 [[doc:Pre-Import Checklist]]
415
416 (% style="margin-left: 60.0px;" %)
417
418
419 (% style="margin-left: 60.0px;" %)
420 [[How to Create an Import Mapping Template>>doc:Import - How to Create an Import Mapping Template]]
421
422 (% style="margin-left: 60.0px;" %)
423 [[How to Use an Import Mapping Template>>doc:Import - How to Use an Import Mapping Template]]
424
425 (% style="margin-left: 60.0px;" %)
426 [[doc:Add Audience]]
427
428 (% style="margin-left: 30.0px;" %)
429 **Batch Operations**
430
431 (% style="margin-left: 60.0px;" %)
432 [[doc:Bulk Operation - How to Perform a Batch Delete]]
433
434 (% style="margin-left: 60.0px;" %)
435 [[doc:Bulk Operation - How to Perform a Batch Product Change]]
436
437 (% style="margin-left: 60.0px;" %)
438 [[doc:Bulk Operation - How to Perform a Batch Status Change]]
439
440 (% style="margin-left: 60.0px;" %)
441 [[Bulk Operation - How to Perform a Batch Suscribe>>doc:Bulk Operation - How to Perform a Batch Subscribe]]
442
443 (% style="margin-left: 60.0px;" %)
444 [[Bulk Operation - How to Perform a Batch Unsubscribe>>doc:Bulk Operation - How to Perform a Batch UnsubscribeKill]]
445
446 (% style="margin-left: 60.0px;" %)
447 [[Bulk Operation - How to Perform a Merge of Duplicate Users>>doc:Bulk Operation - How to Perform a Bulk Merge of Duplicate Users]]
448
449 (% style="margin-left: 30.0px;" %)
450 **Target Audience Segments**
451
452 (% style="margin-left: 60.0px;" %)
453 (% style="color: rgb(0,51,102);" %) __
454 __
455
456 \\
457
458 \\
459 {{/expand}}
460 {{/panel}}
461
462 \\
463
464 \\
465
466 \\
467
468 \\
469
470 \\
471
472 \\
473 {{/layout-cell}}
474 {{/layout-section}}
475 {{/layout}}
476
477 \\
478
479 \\