Changes for page Segment Manager

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

Summary

Details

Page properties
Parent
... ... @@ -1,0 +1,1 @@
1 +System Utilities
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Admin
1 +XWiki.admin
Content
... ... @@ -1,8 +1,6 @@
1 1  {{layout}}
2 2  {{layout-section ac:type="two_right_sidebar"}}
3 3  {{layout-cell}}
4 -
5 -
6 6  {{id name="Start ScreenSteps Content"/}}
7 7  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.
8 8  
... ... @@ -18,32 +18,88 @@
18 18  
19 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 20  
21 -=== ===
19 +=== ===
22 22  
23 -{{id name="CreateSegment"/}}CREATING A NEW SEGMENTFrom the left hand side navigation bar, select Activation → Segment Manager :**
24 -**
21 +{{id name="CreateSegment"/}}CREATING A NEW SEGMENTFrom the left hand side navigation bar, select Activation → Segment Manager :
25 25  
26 26   [[image:attach:image2021-10-25_15-3-35.png||thumbnail="true" height="250"]]
27 27  
28 -\\
29 29  
30 30  Under "User Defined Segments" tab, you will see a list of existing segments.
31 31  
32 32  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.
33 33  
34 -\\
35 35  
36 36  [[image:attach:image2021-10-25_15-11-53.png||height="250"]]
37 37  
38 -\\
39 39  
40 -[[image:attach:image2021-10-25_18-23-50.png||width="794"]]
34 +[[image:attach:SegmentTableCharts2.png||width="794"]]
41 41  
42 -\\
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:
43 43  
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 +
88 +If user has been added successfully to the segment, a popup confirming the same - including segment name and id - appears, as shown:
89 +
90 +[[image:attach:SegmentUserAddedMsg.png||width="538"]]
91 +
92 +
93 +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.
94 +
95 +[[image:attach:SegmentTableChartsDoc.png||width="794"]]
96 +
97 +
44 44  Click "Create Segment" in the upper right-hand corner. You'll be taken to a screen allowing you to define a new segment.
45 45  
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 +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.
47 47  
48 48  Demographics, IP Address, Behavior tabs allow us to define the segment rules.
49 49  
... ... @@ -57,14 +57,14 @@
57 57  
58 58  [[image:attach:Screen Shot 2022-03-31 at 14.42.25.png||width="800"]]
59 59  
60 -\\
61 61  
62 62   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.
63 63  
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 +Give your segment a descriptive name. You can also add a brief description to the segment with more details.
65 65  
66 -\\
119 +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).
67 67  
121 +
68 68  **2. Demographics Tab:**
69 69  
70 70  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.
... ... @@ -71,13 +71,12 @@
71 71  
72 72  [[image:attach:image2021-10-25_15-51-28.png||width="794"]]
73 73  
74 -=== ===
128 +=== ===
75 75  
76 76  {{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.
77 77  
78 78  [[image:attach:image2021-10-25_15-55-34.png||width="794"]]
79 79  
80 -\\
81 81  
82 82  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.
83 83  
... ... @@ -87,15 +87,14 @@
87 87  
88 88  If you are creating purely a demographic segment, hit "Save" and ONEcount will save your segment.
89 89  
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 +**~*~*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.
91 91  
92 -\\
93 93  
94 94  **3. IP Address Tab:**
95 95  
96 96  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.
97 97  
98 -=== ===
150 +=== ===
99 99  
100 100  {{id name="CreateAccountSegment"/}}
101 101  
... ... @@ -117,7 +117,6 @@
117 117  
118 118  If you are creating purely a IP Address based segment, hit "Save" and ONEcount will save your segment.
119 119  
120 -\\
121 121  
122 122  4. **Behavior Tab:**
123 123  
... ... @@ -124,16 +124,15 @@
124 124  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.
125 125  
126 126  (((
127 -\\
178 +
128 128  )))
129 129  
130 -=== ===
181 +=== ===
131 131  
132 -{{id name="CreateBehaviorSegment"/}}CREATE A BEHAVIOR-BASED SEGMENT\\
183 +{{id name="CreateBehaviorSegment"/}}CREATE A BEHAVIOR-BASED SEGMENT
133 133  
134 134  [[image:attach:image2021-10-25_16-35-1.png||width="794"]]
135 135  
136 -\\
137 137  
138 138  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.
139 139  
... ... @@ -141,8 +141,10 @@
141 141  
142 142  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.
143 143  
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 +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.
145 145  
196 +**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.
197 +
146 146  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).
147 147  
148 148  There is a wide range of behavioral criteria that can be used for behavioral segments:
... ... @@ -153,6 +153,8 @@
153 153  
154 154  **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.
155 155  
208 +**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.
209 +
156 156  **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.
157 157  
158 158  **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).
... ... @@ -161,16 +161,29 @@
161 161  
162 162  **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.
163 163  
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 +**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:~/~/).
165 165  
220 +
221 +[[image:attach:web-behavior-2.png||width="800"]]
222 +
223 +
224 +**~*~**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.
225 +
226 +[[image:attach:add-url.png||height="121"]]
227 +
228 +
166 166  **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).
167 167  
168 168  **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.
169 169  
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 -
172 172  **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. 
173 173  
235 +**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. 
236 +
237 +**~*~**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.
238 +
239 +[[image:attach:add-url.png||height="121"]]
240 +
174 174  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.**
175 175  
176 176  **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.**
... ... @@ -179,6 +179,7 @@
179 179  
180 180  The following Segment Impact Matrix illustrates the types of users who can be selected with each demographic and behavioral criteria:
181 181  
249 +(% class="wrapped" %)
182 182  |(((
183 183  **DEMOS**
184 184  )))|(((
... ... @@ -201,7 +201,7 @@
201 201  BOTH
202 202  )))
203 203  |(((
204 -\\
272 +
205 205  )))|(((
206 206  IS NOT BLANK
207 207  )))|(((
... ... @@ -209,20 +209,20 @@
209 209  )))
210 210  |(% colspan="1" %)(% colspan="1" %)
211 211  (((
212 -\\
280 +
213 213  )))|(% colspan="1" %)(% colspan="1" %)
214 214  (((
215 -\\
283 +
216 216  )))|(% colspan="1" %)(% colspan="1" %)
217 217  (((
218 -\\
286 +
219 219  )))
220 220  |(((
221 -**//BEHAVIOR//**
289 +**BEHAVIOR**
222 222  )))|(((
223 -**//VALUE//**
291 +**VALUE**
224 224  )))|(((
225 -//Selects **(KNOWN/UNKNOWN/BOTH)**//
293 +**Selects (KNOWN/UNKNOWN/BOTH)**
226 226  )))
227 227  |(((
228 228  Banner
... ... @@ -246,7 +246,7 @@
246 246  KNOWN
247 247  )))
248 248  |(((
249 -\\
317 +
250 250  )))|(((
251 251  Clicked/Viewed
252 252  )))|(((
... ... @@ -253,7 +253,7 @@
253 253  KNOWN
254 254  )))
255 255  |(((
256 -\\
324 +
257 257  )))|(((
258 258  Not clicked
259 259  )))|(((
... ... @@ -267,7 +267,7 @@
267 267  KNOWN
268 268  )))
269 269  |(((
270 -\\
338 +
271 271  )))|(((
272 272  Abandoned
273 273  )))|(((
... ... @@ -276,7 +276,7 @@
276 276  |(((
277 277  Package Status
278 278  )))|(((
279 -\\
347 +
280 280  )))|(((
281 281  KNOWN
282 282  )))
... ... @@ -283,25 +283,11 @@
283 283  |(((
284 284  Package Transaction
285 285  )))|(((
286 -\\
354 +
287 287  )))|(((
288 288  KNOWN
289 289  )))
290 290  |(((
291 -Quiz
292 -)))|(((
293 -Completed
294 -)))|(((
295 -BOTH
296 -)))
297 -|(((
298 -\\
299 -)))|(((
300 -Abandoned
301 -)))|(((
302 -BOTH
303 -)))
304 -|(((
305 305  Source Code
306 306  )))|(((
307 307  Selected
... ... @@ -323,7 +323,7 @@
323 323  KNOWN
324 324  )))
325 325  |(((
326 -\\
380 +
327 327  )))|(((
328 328  Currently Subscribed
329 329  )))|(((
... ... @@ -330,7 +330,7 @@
330 330  KNOWN
331 331  )))
332 332  |(((
333 -\\
387 +
334 334  )))|(((
335 335  Not Subscribed
336 336  )))|(((
... ... @@ -337,7 +337,7 @@
337 337  BOTH
338 338  )))
339 339  |(((
340 -\\
394 +
341 341  )))|(((
342 342  Unsubscribed
343 343  )))|(((
... ... @@ -353,11 +353,25 @@
353 353  |(((
354 354  Engagement Metric
355 355  )))|(((
356 -\\
410 +
357 357  )))|(((
358 358  KNOWN
359 359  )))
414 +|(% colspan="1" %)(% colspan="1" %)
415 +(((
416 +Referrer
417 +)))|(% colspan="1" %)(% colspan="1" %)
418 +(((
419 +IS/CONTAINS
420 +)))|(% colspan="1" %)(% colspan="1" %)
421 +(((
422 +BOTH
423 +)))
360 360  
425 +
426 +**~*~*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.
427 +
428 +
361 361  **5. Action tab: **
362 362  
363 363  Any action to be associated for segment targeting is defined in this tab.
... ... @@ -366,13 +366,16 @@
366 366  
367 367   [[image:attach:image2021-10-25_16-59-19.png||width="794"]]
368 368  
369 -== ==
437 +== ==
370 370  
371 371  {{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.
372 372  
373 -===
374 - ===
441 +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.
375 375  
443 +=== ===
444 +
445 +=== ===
446 +
376 376  {{id name="CreateAdAction"/}}
377 377  
378 378  === **ADD AN AD ACTION** ===
... ... @@ -379,7 +379,7 @@
379 379  
380 380  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.
381 381  
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.
453 +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.
383 383  
384 384  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.
385 385  
... ... @@ -391,14 +391,16 @@
391 391  
392 392  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.
393 393  
394 -\\
395 395  
396 396   [[image:attach:image2021-10-25_17-16-33.png||width="794"]]
397 397  
398 -\\
399 399  
400 400  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.
401 401  
471 +**~*~**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.
472 +
473 +[[image:attach:add-url.png||height="121"]]
474 +
402 402  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.
403 403  
404 404  * 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
... ... @@ -407,9 +407,10 @@
407 407  
408 408  NOTE: Prioritization of banners is done in Google Ad Manager (or DFP) based on rules you configure in GAM.
409 409  
410 -===
411 - ===
483 +=== ===
412 412  
485 +=== ===
486 +
413 413  {{id name="CreatePopupAction"/}}
414 414  
415 415  === ADD A POP-UP ACTION ===
... ... @@ -418,7 +418,7 @@
418 418  
419 419  Choose Pop-Up from the Action Type pull-down.
420 420  
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.
495 +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.
422 422  
423 423  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.
424 424  
... ... @@ -430,14 +430,15 @@
430 430  
431 431  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.
432 432  
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.
507 +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.
434 434  
435 -\\
436 436  
437 - [[image:attach:image2021-10-25_17-54-54.png||height="250"]]
510 + [[image:attach:Action-Tab.png||width="600"]]
438 438  
439 -\\
512 +**~*~**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.
440 440  
514 +[[image:attach:add-url.png||height="121"]]
515 +
441 441  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.
442 442  
443 443  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.
... ... @@ -446,7 +446,6 @@
446 446  
447 447  Review your Action details and finally click Save to save it.
448 448  
449 -\\
450 450  
451 451  (% style="margin-left: 30.0px;" %)
452 452  === **ADD A SOCIAL TARGET ACTION** ===
... ... @@ -463,7 +463,6 @@
463 463  
464 464  [[https:~~/~~/www.linkedin.com/help/linkedin/topics/6400/6401/112188>>url:https://www.linkedin.com/help/linkedin/topics/6400/6401/112188||shape="rect"]]
465 465  
466 -\\
467 467  
468 468  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.
469 469  
... ... @@ -471,18 +471,15 @@
471 471  
472 472  [[image:attach:Screen Shot 2021-11-17 at 18.36.23.png||height="250"]]
473 473  
474 -\\
475 475  
476 476  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.
477 477  
478 -\\
479 479  
480 480  [[image:attach:Screen Shot 2021-11-17 at 18.48.18.png||width="800"]]
481 481  
482 -\\
483 483  
484 484  (% style="margin-left: 30.0px;" %)
485 -=== ===
555 +=== ===
486 486  
487 487  {{id name="CreateRedirectAction"/}}
488 488  
... ... @@ -495,14 +495,12 @@
495 495  
496 496  As with pop-up and ad targeting, the Target Domain and Section parameters are optional.
497 497  
498 -\\
499 499  
500 500   [[image:attach:image2021-10-25_18-2-56.png||height="250"]]
501 501  
502 -\\
503 503  
504 504  (% style="margin-left: 30.0px;" %)
505 -=== ===
573 +=== ===
506 506  
507 507  {{id name="CreateEmailAction"/}}
508 508  
... ... @@ -512,49 +512,33 @@
512 512  (% style="margin-left: 30.0px;" %)
513 513  To send a transactional e-mail to a user, choose Email from the Action Type  pull-down.
514 514  
515 -(% style="margin-left: 30.0px;" %)
516 -\\
517 517  
518 518  (% style="margin-left: 30.0px;" %)
519 519  [[image:attach:image2021-10-25_18-6-13.png||width="794"]]
520 520  
521 -(% style="margin-left: 30.0px;" %)
522 -\\
523 523  
524 524   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.
525 525  
526 -\\
527 527  
528 528  If you wish to cancel the changes, click the "Cancel" button to go to the segment listing page.
529 529  
530 -\\
531 531  
532 -==
533 - ==
594 +== ==
534 534  
596 +== ==
597 +
535 535  {{id name="CreateTarget"/}}
536 536  
537 -\\
538 538  
539 -\\
540 540  
541 -\\
542 542  
543 -\\
544 544  
545 -\\
546 546  
547 -\\
548 548  
549 -\\
550 550  
551 -\\
552 552  
553 -\\
554 554  
555 -\\
556 556  
557 -\\
558 558  
559 559  
560 560  
... ... @@ -563,29 +563,21 @@
563 563  
564 564  {{layout-cell}}
565 565  {{panel title="Search All Documentation:"}}
566 -
567 -
568 568  {{livesearch/}}
569 569  {{/panel}}
570 570  
571 571  {{panel title="Search USER OPERATIONS Documentation:"}}
572 -
573 -
574 574  {{pagetreesearch rootPage="User Operations - Managing Your Data"/}}
575 575  {{/panel}}
576 576  
577 577  {{panel title="On this page:"}}
578 -
579 -
580 580  {{toc/}}
581 581  {{/panel}}
582 582  
583 583  {{panel title="More USER OPERATIONS Documentation"}}
584 -{{expand}}
585 - **Add Users
586 -**
630 +{{expand title="Click here to expand..."}}
631 + **Add Users**
587 587  
588 -(% style="margin-left: 60.0px;" %)
589 589  
590 590  
591 591  (% style="margin-left: 60.0px;" %)
... ... @@ -594,7 +594,6 @@
594 594  (% style="margin-left: 60.0px;" %)
595 595  [[doc:Pre-Import Checklist]]
596 596  
597 -(% style="margin-left: 60.0px;" %)
598 598  
599 599  
600 600  (% style="margin-left: 60.0px;" %)
... ... @@ -631,26 +631,19 @@
631 631  **Target Audience Segments**
632 632  
633 633  (% style="margin-left: 60.0px;" %)
634 -(% style="color: rgb(0,51,102);" %) __
635 -__
677 +(% style="color:#003366" %)
636 636  
637 -\\
638 638  
639 -\\
680 +
640 640  {{/expand}}
641 641  {{/panel}}
642 642  
643 -\\
644 644  
645 -\\
646 646  
647 -\\
648 648  
649 -\\
650 650  
651 -\\
652 652  
653 -\\
689 +
654 654  {{/layout-cell}}
655 655  {{/layout-section}}
656 656  {{/layout}}
Action-Tab.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +160.4 KB
Content
Action-manager menu.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +40.4 KB
Content
Define-banner-target.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +91.2 KB
Content
Screen Shot 2021-11-17 at 18.36.23.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +72.2 KB
Content
Screen Shot 2021-11-17 at 18.48.18.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +227.9 KB
Content
Screen Shot 2022-03-31 at 14.42.25.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +83.1 KB
Content
SegmentTableCharts2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +451.3 KB
Content
SegmentTableChartsDoc.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +514.2 KB
Content
SegmentUserAddedMsg.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +145.3 KB
Content
SegmentsKnownUnknown3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +577.2 KB
Content
Web-behavior.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +108.2 KB
Content
action-manager.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +220.8 KB
Content
add-url.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +14.5 KB
Content
adduserSegment.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +7.2 KB
Content
custom-popup-box.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +76.8 KB
Content
define-action.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +52.3 KB
Content
display data.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +6.8 KB
Content
expanded-target-list.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +189.3 KB
Content
image2021-10-25_15-11-53.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +106.1 KB
Content
image2021-10-25_15-2-52.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +155.3 KB
Content
image2021-10-25_15-3-35.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +155.3 KB
Content
image2021-10-25_15-42-47.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +56.7 KB
Content
image2021-10-25_15-50-49.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +84.0 KB
Content
image2021-10-25_15-51-28.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +84.0 KB
Content
image2021-10-25_15-55-34.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +37.3 KB
Content
image2021-10-25_15-8-42.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +453.3 KB
Content
image2021-10-25_16-35-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +69.8 KB
Content
image2021-10-25_16-57-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +190.5 KB
Content
image2021-10-25_16-59-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +150.2 KB
Content
image2021-10-25_16-59-19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +150.2 KB
Content
image2021-10-25_17-16-33.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +86.8 KB
Content
image2021-10-25_17-54-54.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +284.2 KB
Content
image2021-10-25_18-2-56.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +333.1 KB
Content
image2021-10-25_18-22-16.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +72.9 KB
Content
image2021-10-25_18-23-50.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +458.8 KB
Content
image2021-10-25_18-6-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +855.5 KB
Content
manage segments.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +107.7 KB
Content
media_1436816640442.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +21.7 KB
Content
media_1436816664853.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +23.4 KB
Content
media_1436816784643.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +57.8 KB
Content
media_1437059609834.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +33.0 KB
Content
media_1437064543783.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +107.8 KB
Content
media_1437064785909.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +31.5 KB
Content
media_1437065487760.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +28.2 KB
Content
media_1437075145033.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +66.1 KB
Content
media_1437079883697.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +45.6 KB
Content
media_1442601673145.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +24.7 KB
Content
media_1442602167866.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +120.4 KB
Content
media_1442611132544.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +83.1 KB
Content
media_1442946953775.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +54.1 KB
Content
media_1442947217827.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +48.9 KB
Content
media_1443033012905.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +124.4 KB
Content
media_1443034475680.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +16.3 KB
Content
media_1443035194695.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +13.7 KB
Content
media_1443036194948.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +15.3 KB
Content
media_1446742365693.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +34.6 KB
Content
media_1446742842763.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +40.7 KB
Content
pencil edit.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +8.3 KB
Content
pop-up-action.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +140.4 KB
Content
segment manager menu.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +41.0 KB
Content
segment-content.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +92.1 KB
Content
segment-definion.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +80.3 KB
Content
segment-demos.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +102.1 KB
Content
segmentKnownsUnknowns.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +357.3 KB
Content
target-definition.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +83.4 KB
Content
target-engine-menu.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +41.2 KB
Content
target-list.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +143.3 KB
Content
target-review-and-save.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +101.9 KB
Content
target-segment-action.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +81.3 KB
Content
trashcan delete.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +9.1 KB
Content
web-behavior-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +115.1 KB
Content
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -66715722
1 +66688
url
... ... @@ -1,1 +1,1 @@
1 -https://info.onecount.net//wiki/spaces/OD/pages/66715722/Segment Manager
1 +https://info.onecount.net//wiki/spaces/OD/pages/66688/Segment Manager