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 10.1
edited by Admin
on 2020/01/05 19:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Segment Manager
1 +Utilities - Target Engine
Parent
... ... @@ -1,1 +1,0 @@
1 -System Utilities
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.admin
1 +XWiki.Admin
Content
... ... @@ -1,12 +1,14 @@
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 -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.
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.
6 6  
7 7  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.
8 8  
9 -The following lesson will provide details on how to use the **Segment Manager**.
11 +The following lesson will provide details on how to use the **Segment Manager**, **Action Manager**, and **Target Engine**.
10 10  
11 11  === Please Note: ===
12 12  
... ... @@ -16,174 +16,49 @@
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 +=== CREATING A NEW SEGMENT ===
20 20  
21 -{{id name="CreateSegment"/}}CREATING A NEW SEGMENTFrom the left hand side navigation bar, select Activation → Segment Manager :
23 +From the Segment Manager menu, select Segment Manager:**
24 +**
22 22  
23 - [[image:attach:image2021-10-25_15-3-35.png||thumbnail="true" height="250"]]
26 +[[image:attach:segment manager menu.png||width="800"]]
24 24  
28 +\\
25 25  
26 -Under "User Defined Segments" tab, you will see a list of existing segments.
30 +You will see a list of existing segments. Click "Create Segment" in the upper right-hand corner.
27 27  
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.
32 +[[image:attach:manage segments.png||height="250"]]
29 29  
34 +\\
30 30  
31 -[[image:attach:image2021-10-25_15-11-53.png||height="250"]]
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.
32 32  
38 +[[image:attach:segment-definion.png||height="250"]]
33 33  
34 -[[image:attach:SegmentTableCharts2.png||width="794"]]
40 +\\
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 +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.
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 -)))
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.
86 86  
87 -If user has been added successfully to the segment, a popup confirming the same - including segment name and id - appears, as shown:
46 +=== CREATE A DEMOGRAPHIC SEGMENT ===
88 88  
89 -[[image:attach:SegmentUserAddedMsg.png||width="538"]]
48 +of 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.
90 90  
50 +[[image:attach:segment-demos.png||height="250"]]
91 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.
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.
93 93  
94 -[[image:attach:SegmentTableChartsDoc.png||width="794"]]
95 -
96 -
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 -
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.
100 -
101 -Demographics, IP Address, Behavior tabs allow us to define the segment rules.
102 -
103 -**1. Definition Tab:**
104 -
105 -Define your segment by giving it a name and a brief description.
106 -
107 -Title is a mandatory field. It should not be blank. Without providing title, you cannot navigate to other tabs.
108 -
109 -Description is an optional field and can have any types of values.
110 -
111 -[[image:attach:Screen Shot 2022-03-31 at 14.42.25.png||width="800"]]
112 -
113 -
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 -
116 -Give your segment a descriptive name. You can also add a brief description to the segment with more details.
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).
119 -
120 -
121 -**2. Demographics Tab:**
122 -
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 -
125 -[[image:attach:image2021-10-25_15-51-28.png||width="794"]]
126 -
127 -=== ===
128 -
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 -
131 -[[image:attach:image2021-10-25_15-55-34.png||width="794"]]
132 -
133 -
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 -
136 136  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.
137 137  
138 138  In this way, you can create a demographic segment of users who are Pediatricians who live in Arizona, for example.
139 139  
140 -If you are creating purely a demographic segment, hit "Save" and ONEcount will save your segment.
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.
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.
60 +\\
143 143  
62 +[[image:attach:segment-content.png||height="250"]]
144 144  
145 -**3. IP Address Tab:**
146 -
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 -
149 -=== ===
150 -
151 -{{id name="CreateAccountSegment"/}}
152 -
153 -(% style="margin-left: 30.0px;" %)
154 -=== CREATE AN IP Address-BASED SEGMENT ===
155 -
156 -(% style="margin-left: 30.0px;" %)
157 -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.
158 -
159 - [[image:attach:image2021-10-25_16-57-14.png||width="794"]]
160 -
161 -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.
162 -
163 -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...
164 -
165 -Note that in IP Address based segmenting you can enter multiple IP addresses and user agents in each field.
166 -
167 -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.
168 -
169 -If you are creating purely a IP Address based segment, hit "Save" and ONEcount will save your segment.
170 -
171 -
172 -4. **Behavior Tab:**
173 -
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 -
176 -(((
177 -
178 -)))
179 -
180 -=== ===
181 -
182 -{{id name="CreateBehaviorSegment"/}}CREATE A BEHAVIOR-BASED SEGMENT
183 -
184 -[[image:attach:image2021-10-25_16-35-1.png||width="794"]]
185 -
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  
189 189  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.
... ... @@ -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.
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.
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,251 +204,72 @@
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 -**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).
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.
212 212  
213 213  **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.
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:~/~/).
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.
218 218  
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.
219 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 -**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 -
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  
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. 
96 +Once you have defined your First Party (demographic) and Behavioral criteria for your segment, be sure to **HIT SAVE.**
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. 
98 +\\
235 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.
100 +(% style="margin-left: 30.0px;" %)
101 +=== CREATE AN ACCOUNT-BASED SEGMENT ===
237 237  
238 -[[image:attach:add-url.png||height="121"]]
103 +(% style="margin-left: 30.0px;" %)
104 +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.
239 239  
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.**
106 +(% style="margin-left: 30.0px;" %)
107 +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.
241 241  
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.**
109 +(% style="margin-left: 30.0px;" %)
110 +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...
243 243  
244 -ONEcount uses specific logic for demographic and behavioral-based criteria. If you select any demographic field as part of your segment (other than e-mail, which is a special case), ONEcount will only select known users has part of the segment. This is because an unknown user has not been matched to a profile, and therefore ONEcount has no way of knowing the user's response to that demographic question. Put another way, if you include State is Alabama in your segment criteria, ONEcount will exclude all unknown users because there is no way for ONEcount to know the state of an unknown user.
112 +(% style="margin-left: 30.0px;" %)
113 +Note that only OR logic is used in Account segmenting and that you can enter multiple IP addresses and user agents in each field.
245 245  
246 -The following Segment Impact Matrix illustrates the types of users who can be selected with each demographic and behavioral criteria:
115 +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.
247 247  
248 -(% class="wrapped" %)
249 -|(((
250 -**DEMOS**
251 -)))|(((
252 -**VALUE**
253 -)))|(((
254 -**Selects (KNOWN/UNKNOWN/BOTH)**
255 -)))
256 -|(((
257 -Any demo
258 -)))|(((
259 -ANY VALUE
260 -)))|(((
261 -KNOWN
262 -)))
263 -|(((
264 -E-mail DEMO
265 -)))|(((
266 -IS BLANK
267 -)))|(((
268 -BOTH
269 -)))
270 -|(((
271 -
272 -)))|(((
273 -IS NOT BLANK
274 -)))|(((
275 -KNOWN
276 -)))
277 -|(% colspan="1" %)(% colspan="1" %)
278 -(((
279 -
280 -)))|(% colspan="1" %)(% colspan="1" %)
281 -(((
282 -
283 -)))|(% colspan="1" %)(% colspan="1" %)
284 -(((
285 -
286 -)))
287 -|(((
288 -**BEHAVIOR**
289 -)))|(((
290 -**VALUE**
291 -)))|(((
292 -**Selects (KNOWN/UNKNOWN/BOTH)**
293 -)))
294 -|(((
295 -Banner
296 -)))|(((
297 -Clicked/Viewed
298 -)))|(((
299 -BOTH
300 -)))
301 -|(((
302 -Content
303 -)))|(((
304 -Viewed
305 -)))|(((
306 -BOTH
307 -)))
308 -|(((
309 -EMAIL
310 -)))|(((
311 -Opened
312 -)))|(((
313 -KNOWN
314 -)))
315 -|(((
316 -
317 -)))|(((
318 -Clicked/Viewed
319 -)))|(((
320 -KNOWN
321 -)))
322 -|(((
323 -
324 -)))|(((
325 -Not clicked
326 -)))|(((
327 -KNOWN
328 -)))
329 -|(((
330 -Form
331 -)))|(((
332 -Completed
333 -)))|(((
334 -KNOWN
335 -)))
336 -|(((
337 -
338 -)))|(((
339 -Abandoned
340 -)))|(((
341 -BOTH
342 -)))
343 -|(((
344 -Package Status
345 -)))|(((
346 -
347 -)))|(((
348 -KNOWN
349 -)))
350 -|(((
351 -Package Transaction
352 -)))|(((
353 -
354 -)))|(((
355 -KNOWN
356 -)))
357 -|(((
358 -Source Code
359 -)))|(((
360 -Selected
361 -)))|(((
362 -KNOWN
363 -)))
364 -|(((
365 -Web
366 -)))|(((
367 -Viewed
368 -)))|(((
369 -BOTH
370 -)))
371 -|(((
372 -Product Transaction
373 -)))|(((
374 -Subscribed
375 -)))|(((
376 -KNOWN
377 -)))
378 -|(((
379 -
380 -)))|(((
381 -Currently Subscribed
382 -)))|(((
383 -KNOWN
384 -)))
385 -|(((
386 -
387 -)))|(((
388 -Not Subscribed
389 -)))|(((
390 -BOTH
391 -)))
392 -|(((
393 -
394 -)))|(((
395 -Unsubscribed
396 -)))|(((
397 -KNOWN
398 -)))
399 -|(((
400 -GEO
401 -)))|(((
402 -IS IN
403 -)))|(((
404 -BOTH
405 -)))
406 -|(((
407 -Engagement Metric
408 -)))|(((
409 -
410 -)))|(((
411 -KNOWN
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 -)))
117 +== **CREATE AN ACTION** ==
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.
119 +From 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
425 425  
121 +\\
426 426  
427 -**5. Action tab: **
123 +[[image:attach:Action-manager menu.png||width="800"]]
428 428  
429 -Any action to be associated for segment targeting is defined in this tab.
125 +\\
430 430  
431 -Date range is a mandatory field (both start and end dates) to add any form of action. You can select any form of action from the dropdown. Once you provide action details, you can save the changes made.
127 +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.
432 432  
433 - [[image:attach:image2021-10-25_16-59-19.png||width="794"]]
129 +\\
434 434  
435 -== ==
131 +[[image:attach:action-manager.png||height="250"]]
436 436  
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.
133 +\\
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.
135 +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.
440 440  
441 -=== ===
137 +\\
442 442  
443 -=== ===
139 +[[image:attach:define-action.png||height="250"]]
444 444  
445 -{{id name="CreateAdAction"/}}
141 +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.
446 446  
447 -=== **ADD AN AD ACTION** ===
143 +=== **CREATE AN AD TARGET** ===
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.
147 +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.
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,38 +460,24 @@
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  
159 +[[image:attach:Define-banner-target.png||height="250"]]
463 463  
464 - [[image:attach:image2021-10-25_17-16-33.png||width="794"]]
465 -
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 -* 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
476 -
477 477  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.
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 -=== ===
169 +=== CREATE A POP-UP TARGET ===
482 482  
483 -=== ===
171 +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.
484 484  
485 -{{id name="CreatePopupAction"/}}
173 +Choose Pop-Up from the Action pull-down at the top.
486 486  
487 -=== ADD A POP-UP ACTION ===
175 +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.
488 488  
489 -You can also create a pop-up target for your segments. Any pop-up created under form-builder section od ONEcount cxan be used for pop-up action for segment.
490 -
491 -Choose Pop-Up from the Action Type pull-down.
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.
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  
497 497  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.
... ... @@ -502,128 +502,176 @@
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.
187 +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  
189 +[[image:attach:pop-up-action.png||width="800"]]
507 507  
508 - [[image:attach:Action-Tab.png||width="600"]]
191 +Next we determine the priority of this pop-up relative
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.
193 +\\
511 511  
512 -[[image:attach:add-url.png||height="121"]]
195 +(% style="margin-left: 30.0px;" %)
196 +===== A. Create Pop-Up =====
513 513  
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.
198 +(% style="margin-left: 30.0px;" %)
199 +~1. Click "New action".
200 +2. Give the action a name and description (optional).
201 +3. Click "Next".
202 +4. Complete the fields as shown below.
203 +5. Click "Next".
515 515  
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.
205 +(% style="margin-left: 30.0px;" %)
206 +[[image:attach:media_1442611132544.png||align="center"]]
517 517  
518 -Last, select the pop-up (it can be any pop-up form builder pop-up or A/B test pop-up).
208 +(% style="margin-left: 30.0px;" %)
209 +Upon clicking "Next", you'll have an opportunity to review the action and "Save" or go "Back" to make changes.
519 519  
520 -Review your Action details and finally click Save to save it.
211 +(% style="margin-left: 30.0px;" %)
212 +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.)
521 521  
214 +(% style="margin-left: 30.0px;" %)
215 +Click "Next" to continue to Step 4 – Review and Save.
522 522  
523 523  (% style="margin-left: 30.0px;" %)
524 -=== **ADD A SOCIAL TARGET ACTION** ===
218 +[[image:attach:media_1443034475680.png||align="center"]]
525 525  
526 -In order to target your users on social networks, ONEcount will need to log into the social network and create a segment containing the users you want to target. Once that segment is created, ONEcount will automatically populate the segment in the social platform as users qualify for that segment in ONEcount.
220 +(% style="margin-left: 30.0px;" %)
221 +When a pop-up action is in effect, a pop-up will appear for the specified target segment in the designated domains and sections at the set frequency and priority level. Please see example below.
527 527  
528 -To do this, ONEcount needs API access to your social account. This account should be the one you run your social ad campaigns through. You will need to provide the credentials for these accounts to the ONEcount team to configure your installation. Just open a ticket with our Help Desk and include the credentials and platform you would like to be connected to, and we''ll take care of it.
223 +(% style="margin-left: 30.0px;" %)
224 +[[image:attach:media_1443033012905.png||align="center"]]
529 529  
530 -**To advertise on Google**: Your account will need to meet the criteria mentioned in below link. We need API access that meets this criteria. If your account does not meet these criteria, we can send a file containing the hashed e-mails of users who fit into the segmnt, so that you can load the data into Google's Customer Match tool manually.
226 +(% style="margin-left: 30.0px;" %)
227 +Note that the display opt-out will appear only if checked when creating the pop-up action.
531 531  
532 -[[https:~~/~~/support.google.com/adspolicy/answer/6299717>>url:https://support.google.com/adspolicy/answer/6299717||shape="rect"]]
229 +(% style="margin-left: 30.0px;" %)
230 +===== B. Create Redirect =====
533 533  
534 -**To advertise on LinkedIn**: Your account will need API access that has “Marketing Developer Platform” access. If your account does not have this capability, we can send a file containing the hashed e-mails of users who fit into the segment, so that you can load the data into LinkedIn's Matched Audience too manually. You can follow steps in below link to get “Marketing Developer Platform” access.
232 +(% style="margin-left: 60.0px;" %)
233 +~1. Click "New action".
234 +2. Give the action a name and description (optional).
235 +3. Click "Next".
236 +4. Complete the fields as shown below.
237 +5. Click "Next".
535 535  
536 -[[https:~~/~~/www.linkedin.com/help/linkedin/topics/6400/6401/112188>>url:https://www.linkedin.com/help/linkedin/topics/6400/6401/112188||shape="rect"]]
239 +(% style="margin-left: 60.0px;" %)
240 +[[image:attach:media_1442947217827.png||align="center"]]
537 537  
242 +(% style="margin-left: 60.0px;" %)
243 +Upon clicking "Next", you'll have an opportunity to review the action and "Save" or go "Back" to make changes.
538 538  
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.
245 +(% style="margin-left: 60.0px;" %)
246 +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.)
540 540  
541 -The URLs ONEcount generates will be the ones you place in the banner system on the social platform. When the user clicks on the URL, they will be sent to the URL you entered in this box, with two important advantages: 1) ONEcount will record the click and capture it for your analysis, and 2) if the user is known to ONEcount, the analytics will show the identity of the user who clicked–even if the link you enter here is not on your web site.
248 +(% style="margin-left: 60.0px;" %)
249 +Click "Next" to continue to Step 4 – Review and Save.
542 542  
543 -[[image:attach:Screen Shot 2021-11-17 at 18.36.23.png||height="250"]]
251 +(% style="margin-left: 60.0px;" %)
252 +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.
544 544  
254 +(% style="margin-left: 30.0px;" %)
255 +===== C. Create Ad Target =====
545 545  
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.
257 +(% style="margin-left: 30.0px;" %)
258 +In order for ad targeting to work, the ad code on your site must be updated so that it will accept and process Key and Value variables. GCN will provide you with the correct code.
547 547  
260 +(% style="margin-left: 30.0px;" %)
261 +~1. Click "New action".
262 +2. Give the action a name and description (optional).
263 +3. Click "Next".
264 +4. Complete the fields as shown below.
265 +5. Click "Next".
548 548  
549 -[[image:attach:Screen Shot 2021-11-17 at 18.48.18.png||width="800"]]
267 +(% style="margin-left: 30.0px;" %)
268 +[[image:attach:media_1446742365693.png||align="center"]]
550 550  
270 +(% style="margin-left: 30.0px;" %)
271 +Upon clicking "Next", you'll have an opportunity to review the action and "Save" or go "Back" to make changes.
551 551  
552 552  (% style="margin-left: 30.0px;" %)
553 -=== ===
274 +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.)
554 554  
555 -{{id name="CreateRedirectAction"/}}
276 +(% style="margin-left: 30.0px;" %)
277 +Click "Next" to continue to Step 4 – Review and Save.
556 556  
557 557  (% style="margin-left: 30.0px;" %)
558 -=== **ADD A REDIRECT ACTION** ===
280 +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.
559 559  
560 -Choose redirect from the list of Type of Action. 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.
282 +*
283 +** 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 numbers.
561 561  
562 -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.
285 +(% style="margin-left: 30.0px;" %)
286 +[[image:attach:media_1443036194948.png||align="center"]]
563 563  
564 -As with pop-up and ad targeting, the Target Domain and Section parameters are optional.
288 +(% style="margin-left: 30.0px;" %)
289 +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.
565 565  
291 +(% style="margin-left: 30.0px;" %)
292 +===== D. Create Email =====
566 566  
567 - [[image:attach:image2021-10-25_18-2-56.png||height="250"]]
294 +(% style="margin-left: 30.0px;" %)
295 +~1. Click "New action".
296 +2. Give the action a name and description (optional).
297 +3. Click "Next".
298 +4. Complete the fields as shown below.
299 +5. Click "Next".
568 568  
301 +(% style="margin-left: 30.0px;" %)
302 +[[image:attach:media_1442946953775.png||align="center"]]
569 569  
570 570  (% style="margin-left: 30.0px;" %)
571 -=== ===
305 +Upon clicking "Next", you'll have an opportunity to review the action and "Save" or go "Back" to make changes.
572 572  
573 -{{id name="CreateEmailAction"/}}
307 +(% style="margin-left: 30.0px;" %)
308 +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.)
574 574  
575 575  (% style="margin-left: 30.0px;" %)
576 -=== ADD EMAIL ACTION ===
311 +Click "Next" to continue to Step 4 – Review and Save.
577 577  
578 578  (% style="margin-left: 30.0px;" %)
579 -To send a transactional e-mail to a user, choose Email from the Action Type  pull-down.
314 +[[image:attach:media_1443035194695.png||align="center"]]
580 580  
581 -
582 582  (% style="margin-left: 30.0px;" %)
583 -[[image:attach:image2021-10-25_18-6-13.png||width="794"]]
317 +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.
584 584  
319 +==== Step 4 – Review and Save ====
585 585  
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.
321 +[[image:attach:media_1446742842763.png||align="center"]]
587 587  
323 +Review all of the information for your persona, and click "Save Persona" to save.
588 588  
589 -If you wish to cancel the changes, click the "Cancel" button to go to the segment listing page.
325 +If you wish to make changes, click the "Back" button to move backward through the steps.
590 590  
591 591  
592 -== ==
593 593  
594 -== ==
329 +{{id name="End ScreenSteps Content"/}}
330 +{{/layout-cell}}
595 595  
596 -{{id name="CreateTarget"/}}
332 +{{layout-cell}}
333 +{{panel title="Search All Documentation:"}}
597 597  
598 598  
336 +{{livesearch/}}
337 +{{/panel}}
599 599  
339 +{{panel title="Search USER OPERATIONS Documentation:"}}
600 600  
601 601  
342 +{{pagetreesearch rootPage="User Operations - Managing Your Data"/}}
343 +{{/panel}}
602 602  
345 +{{panel title="On this page:"}}
603 603  
604 604  
605 -
606 -
607 -
608 -
609 -
610 -
611 -{{id name="End ScreenSteps Content"/}}
612 -{{/layout-cell}}
613 -
614 -{{layout-cell}}
615 -{{panel title=""}}{{/panel}}
616 -
617 -{{panel title=""}}{{/panel}}
618 -
619 -{{panel title="On this page:"}}
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**
352 +{{expand}}
353 + **Add Users
354 +**
626 626  
356 +(% 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  
365 +(% style="margin-left: 60.0px;" %)
635 635  
636 636  
637 637  (% style="margin-left: 60.0px;" %)
... ... @@ -668,19 +668,30 @@
668 668  **Target Audience Segments**
669 669  
670 670  (% style="margin-left: 60.0px;" %)
671 -(% style="color:#003366" %)
402 +(% style="color: rgb(0,51,102);" %) __
403 +__
672 672  
405 +\\
673 673  
674 -
407 +\\
675 675  {{/expand}}
676 676  {{/panel}}
677 677  
411 +\\
678 678  
413 +\\
679 679  
415 +\\
680 680  
417 +\\
681 681  
419 +\\
682 682  
683 -
421 +\\
684 684  {{/layout-cell}}
685 685  {{/layout-section}}
686 686  {{/layout}}
425 +
426 +\\
427 +
428 +\\
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 +23331690
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/23331690/Utilities - Target Engine