Changes for page Segment Manager

Last modified by Admin User on 2025/01/24 16:21
From version 34.1
edited by Admin User
on 2025/01/24 16:21
Change comment: There is no comment for this version
To version 22.1
edited by Admin
on 2022/03/31 14:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,0 @@
1 -System Utilities
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.admin
1 +XWiki.Admin
Content
... ... @@ -1,6 +1,8 @@
1 1  {{layout}}
2 2  {{layout-section ac:type="two_right_sidebar"}}
3 3  {{layout-cell}}
4 +
5 +
4 4  {{id name="Start ScreenSteps Content"/}}
5 5  The Targeting Engine is a powerful tool that allows 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.
6 6  
... ... @@ -16,87 +16,32 @@
16 16  
17 17  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.
18 18  
19 -=== ===
21 +=== ===
20 20  
21 -{{id name="CreateSegment"/}}CREATING A NEW SEGMENTFrom the left hand side navigation bar, select Activation → Segment Manager :
23 +{{id name="CreateSegment"/}}CREATING A NEW SEGMENTFrom the left hand side navigation bar, select Activation → Segment Manager :**
24 +**
22 22  
23 23   [[image:attach:image2021-10-25_15-3-35.png||thumbnail="true" height="250"]]
24 24  
28 +\\
25 25  
26 26  Under "User Defined Segments" tab, you will see a list of existing segments.
27 27  
28 28  Each segment created, is listed here and has edit and delete functionality available just next to it. The overview of the segment (effective date, action, segment size, stats for known and unknown users) is available on click of arrow button next to each segment.
29 29  
34 +\\
30 30  
31 31  [[image:attach:image2021-10-25_15-11-53.png||height="250"]]
32 32  
38 +\\
33 33  
34 -[[image:attach:SegmentTableCharts2.png||width="794"]]
40 +[[image:attach:image2021-10-25_18-23-50.png||width="794"]]
35 35  
36 -The list of segments created contains three columns.  The first column is Segment ID, the second shows Segment Name, and the third is a collection of icons with the following features:
42 +\\
37 37  
38 -(% class="wrapped" %)
39 -|=(((
40 -Image
41 -)))|=(((
42 -Icon
43 -)))|=(((
44 -Feature description
45 -)))
46 -|(((
47 -pencil
48 -)))|(((
49 -(% class="content-wrapper" %)
50 -(((
51 -[[image:attach:pencil edit.png||thumbnail="true" width="40"]]
52 -)))
53 -)))|(((
54 -is for editing segment
55 -)))
56 -|(((
57 -trash can
58 -)))|(((
59 -(% class="content-wrapper" %)
60 -(((
61 -[[image:attach:trashcan delete.png||thumbnail="true" width="40"]]
62 -)))
63 -)))|(((
64 -is for deleting segment
65 -)))
66 -|(((
67 -add user
68 -)))|(((
69 -(% class="content-wrapper" %)
70 -(((
71 -[[image:attach:adduserSegment.png||thumbnail="true" width="40"]]
72 -)))
73 -)))|(((
74 -adds user to the segment
75 -)))
76 -|(((
77 -down-triangle
78 -)))|(((
79 -(% class="content-wrapper" %)
80 -(((
81 -[[image:attach:display data.png||thumbnail="true" width="40"]]
82 -)))
83 -)))|(((
84 -displays data related to the segment such as Effective Date, Action, segment size.  It also shows a table with Knowns, Unknowns and Total users as recorded as of the 'Effective Date.'  At the bottom right is a bar graph with data for the last 7 days for Knowns and Unknowns.
85 -)))
86 -
87 -If user has been added successfully to the segment, a popup confirming the same - including segment name and id - appears, as shown:
88 -
89 -[[image:attach:SegmentUserAddedMsg.png||width="538"]]
90 -
91 -
92 -Below is an example of data displayed by clicking the 'down-triangle' button.  This button changes to 'up-triangle' after expansion.  On clicking this 'up-triangle' button, the display collapses.
93 -
94 -[[image:attach:SegmentTableChartsDoc.png||width="794"]]
95 -
96 -
97 97  Click "Create Segment" in the upper right-hand corner. You'll be taken to a screen allowing you to define a new segment.
98 98  
99 -The new segment creation screen consists of total 5 tabs – Definition, Demographics (previously named as First Party), IP Address (previously named as Account based), Behavior, Action. The panels are cumulative, meaning that in order for a user to be included in a segment, the rules on the Demographics, IP Address, and Behavior tabs must all match that user.
46 +The new segment creation screen consists of total 5 tabs – Definition, Demographics (previously named as First Party), IP Address (previously named as Account based), Behavior, Action.
100 100  
101 101  Demographics, IP Address, Behavior tabs allow us to define the segment rules.
102 102  
... ... @@ -110,14 +110,14 @@
110 110  
111 111  [[image:attach:Screen Shot 2022-03-31 at 14.42.25.png||width="800"]]
112 112  
60 +\\
113 113  
114 114   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 "IP addresses-based Segment.", which can also be called as account based segment.
115 115  
116 -Give your segment a descriptive name. You can also add a brief description to the segment with more details.
64 +Give your segment a descriptive name. You can also add a brief description to the segment with more details. On this panel you will see an option to include only unknown users in this segment. Many of the segment selection criteria can apply to both unknown (ie., unidentified) and known (identified) users. By changing this option to "Yes," you are telling ONEcount to only select users who are unknown for this segment. (See segment impact chart below).
117 117  
118 -On this panel you will see an option to include only unknown users in this segment. Many of the segment selection criteria can apply to both unknown (ie., unidentified) and known (identified) users. By changing this option to "Yes," you are telling ONEcount to only select users who are unknown for this segment. (See Segment Impact Matrix below).
66 +\\
119 119  
120 -
121 121  **2. Demographics Tab:**
122 122  
123 123  If you click the "Demographics" tab, you will have the opportunity to define demographic characteristics for the segment. Multiple rules can be added with And/OR conditions as per requirements.
... ... @@ -124,12 +124,13 @@
124 124  
125 125  [[image:attach:image2021-10-25_15-51-28.png||width="794"]]
126 126  
127 -=== ===
74 +=== ===
128 128  
129 129  {{id name="CreateDemoSegment"/}}CREATE A DEMOGRAPHIC SEGMENTDefine demographic rules of your segment based on the demographic questions you have built in your database. You can use any demographic question to define a segment.
130 130  
131 131  [[image:attach:image2021-10-25_15-55-34.png||width="794"]]
132 132  
80 +\\
133 133  
134 134  If you choose a demographic question that has a multiple choice response, simply click in the search text 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.
135 135  
... ... @@ -139,14 +139,15 @@
139 139  
140 140  If you are creating purely a demographic segment, hit "Save" and ONEcount will save your segment.
141 141  
142 -**~*~*NOTE: **E-mail is a special demographic field. Since demographic fields are part of a user's profile, a user who is unknown would not have any demographic information in the database. Therefore, when you select a demographic field as part of a segment definition, you are normally telling ONEcount you want known users included in this segment. ONEcount handles e-mail slightly differently. If you specify all users who have no e-mail address (ie., select e-mail but leave the Search Text box blank), ONEcount will automatically include unknown users in this segment. This is because a user who is unknown has no e-mail address. For further details, please see the Segment Impact Matrix below.
90 +**~*~*NOTE: **E-mail is a special demographic field. Since demographic fields are part of a user's profile, a user who is unknown would not have any demographic information in the database. Therefore, when you select a demographic field as part of a segment definition, you are normally telling ONEcount you want known users included in this segment. ONEcount handles e-mail slightly differently. If you specify all users who have no e-mail address (ie., select e-mail but leave the Search Text box blank), ONEcount will automatically include unknown users in this segment. This is because a user who is unknown has no e-mail address. For further details, please see the segment impact chart below.
143 143  
92 +\\
144 144  
145 145  **3. IP Address Tab:**
146 146  
147 147  The IP address-based segment can be created and targeted by providing the intended IP addresses here. There is no limit on number of IP addresses that can be added here.
148 148  
149 -=== ===
98 +=== ===
150 150  
151 151  {{id name="CreateAccountSegment"/}}
152 152  
... ... @@ -168,6 +168,7 @@
168 168  
169 169  If you are creating purely a IP Address based segment, hit "Save" and ONEcount will save your segment.
170 170  
120 +\\
171 171  
172 172  4. **Behavior Tab:**
173 173  
... ... @@ -174,15 +174,16 @@
174 174  If you would like to add behavioral characteristics to your segment (ie., Pediatricians who live in Arizona and have read at least two articles on pain), click on the Behavior tab.
175 175  
176 176  (((
177 -
127 +\\
178 178  )))
179 179  
180 -=== ===
130 +=== ===
181 181  
182 -{{id name="CreateBehaviorSegment"/}}CREATE A BEHAVIOR-BASED SEGMENT
132 +{{id name="CreateBehaviorSegment"/}}CREATE A BEHAVIOR-BASED SEGMENT\\
183 183  
184 184  [[image:attach:image2021-10-25_16-35-1.png||width="794"]]
185 185  
136 +\\
186 186  
187 187  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.
188 188  
... ... @@ -190,10 +190,8 @@
190 190  
191 191  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.
192 192  
193 -Define the frequency of the action in the Frequency box. This means how many times within the given date range this event has happened, and enter a date range for the given event.
144 +Define the frequency of the action in the Frequency box. This means how many times within the given date range this event has happened, and enter a date range for the given event.
194 194  
195 -**Date Range**: If 'Past,' the maximum allowed range is 3 months.  If 'Custom,' you can specify a start and end date.  If 'Future' option, allows to set a date range into the future (Currently, only the 'Package Transaction' Category has 'Future' option).  By not entering a value (or simply 0), the segment cannot be processed for that event.
196 -
197 197  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).
198 198  
199 199  There is a wide range of behavioral criteria that can be used for behavioral segments:
... ... @@ -204,8 +204,6 @@
204 204  
205 205  **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.
206 206  
207 -**Engagement Metric: **Users are selected based on the Engagement Metrics they have registered, such as webinar attendance, whitepaper downloads, etc. Please note that only SELECT and NUMERIC metrics appear here.
208 -
209 209  **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.
210 210  
211 211  **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. The selected date range will query on Request Date (Not Transaction Date).
... ... @@ -214,29 +214,16 @@
214 214  
215 215  **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.
216 216  
217 -**Web**: Users are selected based on the web URLs that they have visited. The sub-category is Viewed At Least. The target is a URL or URL fragment. When entering the URL, do not include the protocol (http:~/~/ or https:~/~/).
164 +**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.
218 218  
219 -
220 -[[image:attach:web-behavior-2.png||width="800"]]
221 -
222 -
223 -**~*~**IMPORTANT NOTE: **When you type a URL into the URL box, you will see an option beneath asking if you want to Add the text you are typing to the box. After you are done typing the URL, you must hit 'Enter' to confirm that you want to add the text you just typed into the box. You will see the URL you typed appear in the box in blue (as seen above). If you do not hit 'Enter' and just click the Save button, the URL field will be blank and your segment may not work correctly.
224 -
225 -[[image:attach:add-url.png||height="121"]]
226 -
227 -
228 228  **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. The selected date range will query on Request Date (Not Transaction Date).
229 229  
230 230  **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.
231 231  
170 +**Quiz: **Users are selected based on whether the quiz is completed. It has only one subcategory 'completed'. You can enter the target in the text box.
171 +
232 232  **Geo: **Users are selected based on specific geographic location from anywhere in the world. The sub-category is 'coordinate'. When this geo category is selected, the world map is popped up and you can select any region on that map, where you want to target your users. Once, the selection of region is made, you will see the corresponding geographic coordinates are added to the target field. This geo-based targeting is one of the important functionalities introduced recently. Like other behavior categories, geo can also be added any number of times along with any other rules, by using ‘Add’ button on the screen as per your requirements. 
233 233  
234 -**Referrer**: You can specify URL(s) that serve as a starting point, for an action to be triggered on the target domain (specified in the 'Action' tab). Multiple URLs can be entered in the URL field.  The URL is a web address - either its domain (www.Domain.com) or subdomain (.com).  The 'Action' field has two choices and is used to indicate if the URL values are to be considered as given (you choose 'IS'), or contains a part of it (you choose 'CONTAINS'). The Referrer URL can essentially be used to execute actions defined in the 'Action' tab.  This helps in targeting users specified by the Referrer.  For instance, if you put in '.com' in the URL field, and the target header (Action tab) had 'www.testMe.com' with 'Popup' as the Action Type, what happens is that if the user is currently visiting a webpage that contains '.com' in its URL, then clicks a link that takes them to 'www.Domain.com/testMe.html' the specified popup will show on the Target Domain. 
235 -
236 -**~*~**IMPORTANT NOTE: **When you type a URL into the URL box box for Referrer, you will see an option beneath asking if you want to Add the text you are typing to the box. After you are done typing the URL, you must hit 'Enter' to confirm that you want to add the text you just typed into the box. You will see the URL you typed appear in the box in blue (as seen above). If you do not hit 'Enter' and just click the Save button, the URL field will be blank and your segment may not work correctly.
237 -
238 -[[image:attach:add-url.png||height="121"]]
239 -
240 240  Once you have defined your Behavioral criteria for your segment and you do not wish to add any other rules/action, be sure to **HIT SAVE.**
241 241  
242 242  **Note: There can be only one rule for each criteria like web, banner. If you have multiple target values all of them can be added into 1 rule by adding multiple values into target box.**
... ... @@ -245,7 +245,6 @@
245 245  
246 246  The following Segment Impact Matrix illustrates the types of users who can be selected with each demographic and behavioral criteria:
247 247  
248 -(% class="wrapped" %)
249 249  |(((
250 250  **DEMOS**
251 251  )))|(((
... ... @@ -268,7 +268,7 @@
268 268  BOTH
269 269  )))
270 270  |(((
271 -
204 +\\
272 272  )))|(((
273 273  IS NOT BLANK
274 274  )))|(((
... ... @@ -276,20 +276,20 @@
276 276  )))
277 277  |(% colspan="1" %)(% colspan="1" %)
278 278  (((
279 -
212 +\\
280 280  )))|(% colspan="1" %)(% colspan="1" %)
281 281  (((
282 -
215 +\\
283 283  )))|(% colspan="1" %)(% colspan="1" %)
284 284  (((
285 -
218 +\\
286 286  )))
287 287  |(((
288 -**BEHAVIOR**
221 +**//BEHAVIOR//**
289 289  )))|(((
290 -**VALUE**
223 +**//VALUE//**
291 291  )))|(((
292 -**Selects (KNOWN/UNKNOWN/BOTH)**
225 +//Selects **(KNOWN/UNKNOWN/BOTH)**//
293 293  )))
294 294  |(((
295 295  Banner
... ... @@ -313,7 +313,7 @@
313 313  KNOWN
314 314  )))
315 315  |(((
316 -
249 +\\
317 317  )))|(((
318 318  Clicked/Viewed
319 319  )))|(((
... ... @@ -320,7 +320,7 @@
320 320  KNOWN
321 321  )))
322 322  |(((
323 -
256 +\\
324 324  )))|(((
325 325  Not clicked
326 326  )))|(((
... ... @@ -334,7 +334,7 @@
334 334  KNOWN
335 335  )))
336 336  |(((
337 -
270 +\\
338 338  )))|(((
339 339  Abandoned
340 340  )))|(((
... ... @@ -343,7 +343,7 @@
343 343  |(((
344 344  Package Status
345 345  )))|(((
346 -
279 +\\
347 347  )))|(((
348 348  KNOWN
349 349  )))
... ... @@ -350,11 +350,25 @@
350 350  |(((
351 351  Package Transaction
352 352  )))|(((
353 -
286 +\\
354 354  )))|(((
355 355  KNOWN
356 356  )))
357 357  |(((
291 +Quiz
292 +)))|(((
293 +Completed
294 +)))|(((
295 +BOTH
296 +)))
297 +|(((
298 +\\
299 +)))|(((
300 +Abandoned
301 +)))|(((
302 +BOTH
303 +)))
304 +|(((
358 358  Source Code
359 359  )))|(((
360 360  Selected
... ... @@ -376,7 +376,7 @@
376 376  KNOWN
377 377  )))
378 378  |(((
379 -
326 +\\
380 380  )))|(((
381 381  Currently Subscribed
382 382  )))|(((
... ... @@ -383,7 +383,7 @@
383 383  KNOWN
384 384  )))
385 385  |(((
386 -
333 +\\
387 387  )))|(((
388 388  Not Subscribed
389 389  )))|(((
... ... @@ -390,7 +390,7 @@
390 390  BOTH
391 391  )))
392 392  |(((
393 -
340 +\\
394 394  )))|(((
395 395  Unsubscribed
396 396  )))|(((
... ... @@ -406,24 +406,11 @@
406 406  |(((
407 407  Engagement Metric
408 408  )))|(((
409 -
356 +\\
410 410  )))|(((
411 411  KNOWN
412 412  )))
413 -|(% colspan="1" %)(% colspan="1" %)
414 -(((
415 -Referrer
416 -)))|(% colspan="1" %)(% colspan="1" %)
417 -(((
418 -IS/CONTAINS
419 -)))|(% colspan="1" %)(% colspan="1" %)
420 -(((
421 -BOTH
422 -)))
423 423  
424 -**~*~*NOTE: **Selecting "Only Unknown" on the first panel of the segment will cause any of the above options to be limited to unknowns. For example, e-mail is blank would return only unknowns, viewing a web page would be only unknowns, etc.
425 -
426 -
427 427  **5. Action tab: **
428 428  
429 429  Any action to be associated for segment targeting is defined in this tab.
... ... @@ -432,16 +432,13 @@
432 432  
433 433   [[image:attach:image2021-10-25_16-59-19.png||width="794"]]
434 434  
435 -== ==
369 +== ==
436 436  
437 437  {{id name="CreateAction"/}}ADD AN ACTIONGo to the Action tab of create/edit segment. 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, Email, Social Target, Subscribe to a Product, Unsubscribe to a Product, Subscribe to a Package, Unsubscribe to a Package, Add to Segment, Remove from Segment. Any action can be selected from action type dropdown.
438 438  
439 -Please Note: the 'Referrer' Category from the Behavior tab can be used to execute the 'Action Type' defined here.  Please read about this Category in the 'Create a Behavior-based Segment' section.
373 +===
374 + ===
440 440  
441 -=== ===
442 -
443 -=== ===
444 -
445 445  {{id name="CreateAdAction"/}}
446 446  
447 447  === **ADD AN AD ACTION** ===
... ... @@ -448,7 +448,7 @@
448 448  
449 449  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.
450 450  
451 -In the screen below, you'll see the options for an Ad Target. The first three options are Target Domain and Target Content, Section. These are used to// limit// the scope of this action, not to define it. It's important to understand the difference.
382 +In the screen below, you'll see the options for an Ad Target. The first three options are Target Domain and Target Content, Section. These are used to// limit// the scope of this action, not to define it. It's important to understand the difference.
452 452  
453 453  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.
454 454  
... ... @@ -460,16 +460,14 @@
460 460  
461 461  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.
462 462  
394 +\\
463 463  
464 464   [[image:attach:image2021-10-25_17-16-33.png||width="794"]]
465 465  
398 +\\
466 466  
467 467  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.
468 468  
469 -**~*~**IMPORTANT NOTE: **When you type a Target Domain or Section into the appropriate box, you will see an option beneath asking if you want to Add the text you are typing to the box. After you are done typing, you must hit 'Enter' to confirm that you want to add the text you just typed into the box. You will see the Domain or Section you typed appear in the box in blue (as seen above). If you do not hit 'Enter' and just click the Save button, the Domain and Section fields will be blank and your segment may not work correctly.
470 -
471 -[[image:attach:add-url.png||height="121"]]
472 -
473 473  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.
474 474  
475 475  * 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
... ... @@ -478,10 +478,9 @@
478 478  
479 479  NOTE: Prioritization of banners is done in Google Ad Manager (or DFP) based on rules you configure in GAM.
480 480  
481 -=== ===
410 +===
411 + ===
482 482  
483 -=== ===
484 -
485 485  {{id name="CreatePopupAction"/}}
486 486  
487 487  === ADD A POP-UP ACTION ===
... ... @@ -490,7 +490,7 @@
490 490  
491 491  Choose Pop-Up from the Action Type pull-down.
492 492  
493 -The next three options are Target Domain, Target Content and Section. These are used to// limit// the scope of this action, not to define it. It's important to understand the difference.
421 +The next three options are Target Domain, Target Content and Section. These are used to// limit// the scope of this action, not to define it. It's important to understand the difference.
494 494  
495 495  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.
496 496  
... ... @@ -502,15 +502,14 @@
502 502  
503 503  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.
504 504  
505 -The Target Domain and Section parameters are only required if you want to limit the pop-up If you leave them blank, the user will be targeted across all your web sites.
433 +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.
506 506  
435 +\\
507 507  
508 - [[image:attach:Action-Tab.png||width="600"]]
437 + [[image:attach:image2021-10-25_17-54-54.png||height="250"]]
509 509  
510 -**~*~**IMPORTANT NOTE: **When you type a Target Domain or Section into the appropriate box, you will see an option beneath asking if you want to Add the text you are typing to the box. After you are done typing, you must hit 'Enter' to confirm that you want to add the text you just typed into the box. You will see the Domain or Section you typed appear in the box in blue (as seen above). If you do not hit 'Enter' and just click the Save button, the Domain and Section fields will be blank and your segment may not work correctly.
439 +\\
511 511  
512 -[[image:attach:add-url.png||height="121"]]
513 -
514 514  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.
515 515  
516 516  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.
... ... @@ -519,6 +519,7 @@
519 519  
520 520  Review your Action details and finally click Save to save it.
521 521  
449 +\\
522 522  
523 523  (% style="margin-left: 30.0px;" %)
524 524  === **ADD A SOCIAL TARGET ACTION** ===
... ... @@ -535,6 +535,7 @@
535 535  
536 536  [[https:~~/~~/www.linkedin.com/help/linkedin/topics/6400/6401/112188>>url:https://www.linkedin.com/help/linkedin/topics/6400/6401/112188||shape="rect"]]
537 537  
466 +\\
538 538  
539 539  Choose Social Target from the list of Type of Action.  You can select multiple social platforms in a single action as shown in below screenshot.  Enter URL of target in Target URL field; this is the URL you want users to go to when they click on the ad in the social platform. ONEcount will generate a unique URL for each social platform.
540 540  
... ... @@ -542,15 +542,18 @@
542 542  
543 543  [[image:attach:Screen Shot 2021-11-17 at 18.36.23.png||height="250"]]
544 544  
474 +\\
545 545  
546 546  To get the URLs for pasting into the social system, go to your Segment List and expand the segment. The URLs will be shown. Simply click on the clip-board to the right and the URL will be copied to your browser's clipboard.
547 547  
478 +\\
548 548  
549 549  [[image:attach:Screen Shot 2021-11-17 at 18.48.18.png||width="800"]]
550 550  
482 +\\
551 551  
552 552  (% style="margin-left: 30.0px;" %)
553 -=== ===
485 +=== ===
554 554  
555 555  {{id name="CreateRedirectAction"/}}
556 556  
... ... @@ -563,12 +563,14 @@
563 563  
564 564  As with pop-up and ad targeting, the Target Domain and Section parameters are optional.
565 565  
498 +\\
566 566  
567 567   [[image:attach:image2021-10-25_18-2-56.png||height="250"]]
568 568  
502 +\\
569 569  
570 570  (% style="margin-left: 30.0px;" %)
571 -=== ===
505 +=== ===
572 572  
573 573  {{id name="CreateEmailAction"/}}
574 574  
... ... @@ -578,33 +578,49 @@
578 578  (% style="margin-left: 30.0px;" %)
579 579  To send a transactional e-mail to a user, choose Email from the Action Type  pull-down.
580 580  
515 +(% style="margin-left: 30.0px;" %)
516 +\\
581 581  
582 582  (% style="margin-left: 30.0px;" %)
583 583  [[image:attach:image2021-10-25_18-6-13.png||width="794"]]
584 584  
521 +(% style="margin-left: 30.0px;" %)
522 +\\
585 585  
586 586   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.
587 587  
526 +\\
588 588  
589 589  If you wish to cancel the changes, click the "Cancel" button to go to the segment listing page.
590 590  
530 +\\
591 591  
592 -== ==
532 +==
533 + ==
593 593  
594 -== ==
595 -
596 596  {{id name="CreateTarget"/}}
597 597  
537 +\\
598 598  
539 +\\
599 599  
541 +\\
600 600  
543 +\\
601 601  
545 +\\
602 602  
547 +\\
603 603  
549 +\\
604 604  
551 +\\
605 605  
553 +\\
606 606  
555 +\\
607 607  
557 +\\
608 608  
609 609  
610 610  
... ... @@ -612,18 +612,30 @@
612 612  {{/layout-cell}}
613 613  
614 614  {{layout-cell}}
615 -{{panel title=""}}{{/panel}}
565 +{{panel title="Search All Documentation:"}}
616 616  
617 -{{panel title=""}}{{/panel}}
618 618  
568 +{{livesearch/}}
569 +{{/panel}}
570 +
571 +{{panel title="Search USER OPERATIONS Documentation:"}}
572 +
573 +
574 +{{pagetreesearch rootPage="User Operations - Managing Your Data"/}}
575 +{{/panel}}
576 +
619 619  {{panel title="On this page:"}}
578 +
579 +
620 620  {{toc/}}
621 621  {{/panel}}
622 622  
623 623  {{panel title="More USER OPERATIONS Documentation"}}
624 -{{expand title="Click here to expand..."}}
625 - **Add Users**
584 +{{expand}}
585 + **Add Users
586 +**
626 626  
588 +(% style="margin-left: 60.0px;" %)
627 627  
628 628  
629 629  (% style="margin-left: 60.0px;" %)
... ... @@ -632,6 +632,7 @@
632 632  (% style="margin-left: 60.0px;" %)
633 633  [[doc:Pre-Import Checklist]]
634 634  
597 +(% style="margin-left: 60.0px;" %)
635 635  
636 636  
637 637  (% style="margin-left: 60.0px;" %)
... ... @@ -668,19 +668,26 @@
668 668  **Target Audience Segments**
669 669  
670 670  (% style="margin-left: 60.0px;" %)
671 -(% style="color:#003366" %)
634 +(% style="color: rgb(0,51,102);" %) __
635 +__
672 672  
637 +\\
673 673  
674 -
639 +\\
675 675  {{/expand}}
676 676  {{/panel}}
677 677  
643 +\\
678 678  
645 +\\
679 679  
647 +\\
680 680  
649 +\\
681 681  
651 +\\
682 682  
683 -
653 +\\
684 684  {{/layout-cell}}
685 685  {{/layout-section}}
686 686  {{/layout}}
Action-Tab.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -160.4 KB
Content
Action-manager menu.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -40.4 KB
Content
Define-banner-target.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -91.2 KB
Content
Screen Shot 2021-11-17 at 18.36.23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -72.2 KB
Content
Screen Shot 2021-11-17 at 18.48.18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -227.9 KB
Content
Screen Shot 2022-03-31 at 14.42.25.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -83.1 KB
Content
SegmentTableCharts2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -451.3 KB
Content
SegmentTableChartsDoc.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -514.2 KB
Content
SegmentUserAddedMsg.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -145.3 KB
Content
SegmentsKnownUnknown3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -577.2 KB
Content
Web-behavior.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -108.2 KB
Content
action-manager.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -220.8 KB
Content
add-url.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -14.5 KB
Content
adduserSegment.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -7.2 KB
Content
custom-popup-box.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -76.8 KB
Content
define-action.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -52.3 KB
Content
display data.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -6.8 KB
Content
expanded-target-list.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -189.3 KB
Content
image2021-10-25_15-11-53.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -106.1 KB
Content
image2021-10-25_15-2-52.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -155.3 KB
Content
image2021-10-25_15-3-35.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -155.3 KB
Content
image2021-10-25_15-42-47.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -56.7 KB
Content
image2021-10-25_15-50-49.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -84.0 KB
Content
image2021-10-25_15-51-28.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -84.0 KB
Content
image2021-10-25_15-55-34.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -37.3 KB
Content
image2021-10-25_15-8-42.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -453.3 KB
Content
image2021-10-25_16-35-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -69.8 KB
Content
image2021-10-25_16-57-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -190.5 KB
Content
image2021-10-25_16-59-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -150.2 KB
Content
image2021-10-25_16-59-19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -150.2 KB
Content
image2021-10-25_17-16-33.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -86.8 KB
Content
image2021-10-25_17-54-54.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -284.2 KB
Content
image2021-10-25_18-2-56.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -333.1 KB
Content
image2021-10-25_18-22-16.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -72.9 KB
Content
image2021-10-25_18-23-50.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -458.8 KB
Content
image2021-10-25_18-6-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -855.5 KB
Content
manage segments.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -107.7 KB
Content
media_1436816640442.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -21.7 KB
Content
media_1436816664853.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -23.4 KB
Content
media_1436816784643.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -57.8 KB
Content
media_1437059609834.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -33.0 KB
Content
media_1437064543783.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -107.8 KB
Content
media_1437064785909.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -31.5 KB
Content
media_1437065487760.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -28.2 KB
Content
media_1437075145033.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -66.1 KB
Content
media_1437079883697.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -45.6 KB
Content
media_1442601673145.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -24.7 KB
Content
media_1442602167866.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -120.4 KB
Content
media_1442611132544.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -83.1 KB
Content
media_1442946953775.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -54.1 KB
Content
media_1442947217827.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -48.9 KB
Content
media_1443033012905.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -124.4 KB
Content
media_1443034475680.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -16.3 KB
Content
media_1443035194695.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -13.7 KB
Content
media_1443036194948.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -15.3 KB
Content
media_1446742365693.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -34.6 KB
Content
media_1446742842763.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -40.7 KB
Content
pencil edit.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -8.3 KB
Content
pop-up-action.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -140.4 KB
Content
segment manager menu.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -41.0 KB
Content
segment-content.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -92.1 KB
Content
segment-definion.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -80.3 KB
Content
segment-demos.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -102.1 KB
Content
segmentKnownsUnknowns.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -357.3 KB
Content
target-definition.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -83.4 KB
Content
target-engine-menu.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -41.2 KB
Content
target-list.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -143.3 KB
Content
target-review-and-save.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -101.9 KB
Content
target-segment-action.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -81.3 KB
Content
trashcan delete.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -9.1 KB
Content
web-behavior-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -115.1 KB
Content
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -66688
1 +66715722
url
... ... @@ -1,1 +1,1 @@
1 -https://info.onecount.net//wiki/spaces/OD/pages/66688/Segment Manager
1 +https://info.onecount.net//wiki/spaces/OD/pages/66715722/Segment Manager