Changes for page Segment Manager

Last modified by Admin User on 2025/01/24 16:21
From version 33.1
edited by Admin User
on 2024/09/26 10:49
Change comment: There is no comment for this version
To version 6.1
edited by melanie@one-count_com
on 2016/12/14 15:10
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 (v12.x)
Parent
... ... @@ -1,1 +1,0 @@
1 -System Utilities
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.admin
1 +XWiki.melanie@one-count_com
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 Targeting Engine / Persona Manager.
10 10  
11 11  === Please Note: ===
12 12  
... ... @@ -16,675 +16,300 @@
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 +=== OPEN THE TARGETING AUTOMATION & PERSONALIZATION (TAP) WINDOW ===
20 20  
21 -{{id name="CreateSegment"/}}CREATING A NEW SEGMENTFrom the left hand side navigation bar, select Activation → Segment Manager :
23 +=== Select UTILITIES from the main menu. ===
22 22  
23 - [[image:attach:image2021-10-25_15-3-35.png||thumbnail="true" height="250"]]
25 +[[image:attach:media_1436816640442.png||align="center"]]
24 24  
27 +=== Select TARGETING ENGINE from the sub-menu. ===
25 25  
26 -Under "User Defined Segments" tab, you will see a list of existing segments.
29 +[[image:attach:media_1436816664853.png||align="center"]]
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.
31 +This will open the Targeting Automation & Personalization (TAP) window displaying a list of existing personas, if any, as shown below.
29 29  
33 +[[image:attach:media_1436816784643.png||align="center"]]
30 30  
31 -[[image:attach:image2021-10-25_15-11-53.png||height="250"]]
35 +Expanding the details of a persona will show you the target segment and actions for that persona. (See screenshot below.)
32 32  
37 +[[image:attach:media_1437059609834.png||align="center"]]
33 33  
34 -[[image:attach:SegmentTableCharts2.png||width="794"]]
39 +Clicking on the "i" (information) icon will display a pop-up with details of the action to perform, as shown below.
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:
41 +[[image:attach:media_1437064543783.png||align="center"]]
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 -)))
43 +=== CREATE A NEW PERSONA ===
86 86  
45 +=== Click "Create Persona" button ===
87 87  
88 -If user has been added successfully to the segment, a popup confirming the same - including segment name and id - appears, as shown:
47 +[[image:attach:media_1437064785909.png||align="center"]]
89 89  
90 -[[image:attach:SegmentUserAddedMsg.png||width="538"]]
49 +This will open the Profile window, which is Step 1 in creating the persona.
91 91  
51 +You move forward through the creation process by clicking "Next" at each step, and you can move back to the previous step by clicking "Back".
92 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.
53 +**Note that if you click the "Back" button, the step you were working on won't be saved. All steps are saved only at Step 4: Review and Save.**
94 94  
95 -[[image:attach:SegmentTableChartsDoc.png||width="794"]]
55 +=== Step 1 – Profile ===
96 96  
57 +[[image:attach:media_1437065487760.png||align="center"]]
97 97  
98 -Click "Create Segment" in the upper right-hand corner. You'll be taken to a screen allowing you to define a new segment.
59 +Complete the Name, Description, and Effective Date Range fields for the persona, then click the "Next" button.
99 99  
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.
61 +=== Step 2 – Segment ===
101 101  
102 -Demographics, IP Address, Behavior tabs allow us to define the segment rules.
63 +A "Segment" is a subgroup of your user universe that you wish to target with a specific action.
103 103  
104 -**1. Definition Tab:**
65 +You can define a target segment by User – including Product, Demographics, Source Code, Newsletter, or Web filters – or by Account.
105 105  
106 -Define your segment by giving it a name and a brief description.
67 +**Product** – Allows you to segment based on a product subscription status
68 + **Demographics** – Allows you to segment based on whether a user meets or does not meet specified demographic criteria
69 + **Source Code** – Allows you to segment based on assigned or not assigned Source Code
70 + **Newsletter** – Allows you to segment based on whether a user has or has not opened or clicked on a specified newsletter
71 + **Web** – Allows you to segment based on whether a user has or has not visited a specified section or page on your web site. Note that this behavior-based filter needs to be used in conjunction with any of the other identity-based filters listed above (Product, Demographics, Source Code, Newsletter).
107 107  
108 -Title is a mandatory field. It should not be blank. Without providing title, you cannot navigate to other tabs.
73 +See directions for creating a segment of all users, both known and unkown, in //**B. Segment by Account**// below.
109 109  
110 -Description is an optional field and can have any types of values.
75 +You may select multiple filters and multiple options within filters.
111 111  
112 -[[image:attach:Screen Shot 2022-03-31 at 14.42.25.png||width="800"]]
77 +=== A. Segment by User ===
113 113  
79 +[[image:attach:media_1437075145033.png||align="center"]]
114 114  
115 - 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.
81 +The screenshot above is from v. 11.6. Prior versions do not have the "With"/"Without" option.
116 116  
117 -Give your segment a descriptive name. You can also add a brief description to the segment with more details.
83 +Notice the "AND" / "OR" logic that can be used to join different filters for the segment. Multiple selections //within// a filter use "OR" logic.
118 118  
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).
85 +**To add additional criteria to a segment, click the "And" or "Or" button.**
120 120  
87 +In the example above, the targeted segment is all users who:
121 121  
122 -**2. Demographics Tab:**
89 +A. are NOT ("Without") new //OR// renewal subscribers, with a product status of Qualified Print //OR// Qualified Digital //OR// Non-Qualified Digital, to the Magazine //OR// Digital Edition product;
123 123  
124 -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.
91 +**AND**
92 + B. have ('With") opened the "...ain Today" newsletter;
93 + **OR**
94 + C. have ("With") Primary Business Category that contains "Industrial Mfg., Including Plastics & Rubber... " _OR "_High-Tech Computers/Electronics".
125 125  
126 -[[image:attach:image2021-10-25_15-51-28.png||width="794"]]
96 +**That is, all users who fit criteria A AND fit either criteria B OR C** * Notice the separator line when AND is selected.
127 127  
128 -=== ===
98 +=== B. Segment by Account ===
129 129  
130 -{{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.
100 +[[image:attach:media_1437079883697.png||align="center"]]
131 131  
132 -[[image:attach:image2021-10-25_15-55-34.png||width="794"]]
102 +Version 11.6 and later have added functionality that allows you to 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.
133 133  
134 -
135 -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.
136 -
137 -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.
138 -
139 -In this way, you can create a demographic segment of users who are Pediatricians who live in Arizona, for example.
140 -
141 -If you are creating purely a demographic segment, hit "Save" and ONEcount will save your segment.
142 -
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.
144 -
145 -
146 -**3. IP Address Tab:**
147 -
148 -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.
149 -
150 -=== ===
151 -
152 -{{id name="CreateAccountSegment"/}}
153 -
154 -(% style="margin-left: 30.0px;" %)
155 -=== CREATE AN IP Address-BASED SEGMENT ===
156 -
157 -(% style="margin-left: 30.0px;" %)
158 -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.
159 -
160 - [[image:attach:image2021-10-25_16-57-14.png||width="794"]]
161 -
162 162  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.
163 163  
164 164  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...
165 165  
166 -Note that in IP Address based segmenting you can enter multiple IP addresses and user agents in each field.
108 +Note that only OR logic is used in Account segmenting and that you can enter multiple IP addresses and user agents in each field.
167 167  
168 -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.
110 +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.
169 169  
170 -If you are creating purely a IP Address based segment, hit "Save" and ONEcount will save your segment.
112 +=== Step 3 – Action ===
171 171  
114 +"Action" is where you define the action to be taken for the identified segment, e.g. a website pop-up or ad targeting.
172 172  
173 -4. **Behavior Tab:**
116 +Types of Actions include: Pop-Up, Redirect, Ad Target, Email
174 174  
175 -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.
118 +You can use any existing actions by clicking in the "Select Actions" field and selecting the action (see screenshot below) or create a new action (see A-D below).
176 176  
177 -(((
178 -
179 -)))
120 +[[image:attach:media_1442601673145.png||align="center"]]
180 180  
181 -=== ===
122 +Hover over an action to see details (see screenshot below).
182 182  
183 -{{id name="CreateBehaviorSegment"/}}CREATE A BEHAVIOR-BASED SEGMENT
124 +[[image:attach:media_1442602167866.png||align="center"]]
184 184  
185 -[[image:attach:image2021-10-25_16-35-1.png||width="794"]]
126 +=== A. Create Pop-Up ===
186 186  
128 +~1. Click "New action".
129 + 2. Give the action a name and description (optional).
130 + 3. Click "Next".
131 + 4. Complete the fields as shown below.
132 + 5. Click "Next".
187 187  
188 -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.
134 +[[image:attach:media_1442611132544.png||align="center"]]
189 189  
190 -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.
136 +Upon clicking "Next", you'll have an opportunity to review the action and "Save" or go "Back" to make changes.
191 191  
192 -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.
138 +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.)
193 193  
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.
140 +Click "Next" to continue to Step 4 – Review and Save.
195 195  
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.
142 +[[image:attach:media_1443034475680.png||align="center"]]
197 197  
198 -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).
144 +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.
199 199  
200 -There is a wide range of behavioral criteria that can be used for behavioral segments:
146 +[[image:attach:media_1443033012905.png||align="center"]]
201 201  
202 -**Banner**: Users are selected based on the banner ads they have viewed on your site. The sub-category for Banners is Viewed or Clicked. Target is the name of the banner(s).
148 +Note that the display opt-out will appear only if checked when creating the pop-up action.
203 203  
204 -**Content**: Users are selected based on the meta keywords contained on the pages a user visits. The sub-category for Content is Viewed or Clicked. Target is the content keyword.
150 +=== B. Create Redirect ===
205 205  
206 -**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.
152 +~1. Click "New action".
153 + 2. Give the action a name and description (optional).
154 + 3. Click "Next".
155 + 4. Complete the fields as shown below.
156 + 5. Click "Next".
207 207  
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.
158 +[[image:attach:media_1442947217827.png||align="center"]]
209 209  
210 -**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.
160 +Upon clicking "Next", you'll have an opportunity to review the action and "Save" or go "Back" to make changes.
211 211  
212 -**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).
162 +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.)
213 213  
214 -**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.
164 +Click "Next" to continue to Step 4 – Review and Save.
215 215  
216 -**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.
166 +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.
217 217  
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:~/~/).
168 +=== C. Create Ad Target ===
219 219  
170 +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.
220 220  
221 -[[image:attach:web-behavior-2.png||width="800"]]
172 +~1. Click "New action".
173 + 2. Give the action a name and description (optional).
174 + 3. Click "Next".
175 + 4. Complete the fields as shown below.
176 + 5. Click "Next".
222 222  
178 +[[image:attach:media_1446742365693.png||align="center"]]
223 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.
180 +Upon clicking "Next", you'll have an opportunity to review the action and "Save" or go "Back" to make changes.
225 225  
226 -[[image:attach:add-url.png||height="121"]]
182 +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.)
227 227  
184 +Click "Next" to continue to Step 4 – Review and Save.
228 228  
229 -**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).
186 +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.
230 230  
231 -**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.
188 +* 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.
232 232  
233 -**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. 
190 +[[image:attach:media_1443036194948.png||align="center"]]
234 234  
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. 
192 +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.
236 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.
194 +=== D. Create Email ===
238 238  
239 -[[image:attach:add-url.png||height="121"]]
196 +~1. Click "New action".
197 + 2. Give the action a name and description (optional).
198 + 3. Click "Next".
199 + 4. Complete the fields as shown below.
200 + 5. Click "Next".
240 240  
241 -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.**
202 +[[image:attach:media_1442946953775.png||align="center"]]
242 242  
243 -**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.**
204 +Upon clicking "Next", you'll have an opportunity to review the action and "Save" or go "Back" to make changes.
244 244  
245 -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.
206 +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.)
246 246  
247 -The following Segment Impact Matrix illustrates the types of users who can be selected with each demographic and behavioral criteria:
208 +Click "Next" to continue to Step 4 – Review and Save.
248 248  
249 -(% class="wrapped" %)
250 -|(((
251 -**DEMOS**
252 -)))|(((
253 -**VALUE**
254 -)))|(((
255 -**Selects (KNOWN/UNKNOWN/BOTH)**
256 -)))
257 -|(((
258 -Any demo
259 -)))|(((
260 -ANY VALUE
261 -)))|(((
262 -KNOWN
263 -)))
264 -|(((
265 -E-mail DEMO
266 -)))|(((
267 -IS BLANK
268 -)))|(((
269 -BOTH
270 -)))
271 -|(((
272 -
273 -)))|(((
274 -IS NOT BLANK
275 -)))|(((
276 -KNOWN
277 -)))
278 -|(% colspan="1" %)(% colspan="1" %)
279 -(((
280 -
281 -)))|(% colspan="1" %)(% colspan="1" %)
282 -(((
283 -
284 -)))|(% colspan="1" %)(% colspan="1" %)
285 -(((
286 -
287 -)))
288 -|(((
289 -**BEHAVIOR**
290 -)))|(((
291 -**VALUE**
292 -)))|(((
293 -**Selects (KNOWN/UNKNOWN/BOTH)**
294 -)))
295 -|(((
296 -Banner
297 -)))|(((
298 -Clicked/Viewed
299 -)))|(((
300 -BOTH
301 -)))
302 -|(((
303 -Content
304 -)))|(((
305 -Viewed
306 -)))|(((
307 -BOTH
308 -)))
309 -|(((
310 -EMAIL
311 -)))|(((
312 -Opened
313 -)))|(((
314 -KNOWN
315 -)))
316 -|(((
317 -
318 -)))|(((
319 -Clicked/Viewed
320 -)))|(((
321 -KNOWN
322 -)))
323 -|(((
324 -
325 -)))|(((
326 -Not clicked
327 -)))|(((
328 -KNOWN
329 -)))
330 -|(((
331 -Form
332 -)))|(((
333 -Completed
334 -)))|(((
335 -KNOWN
336 -)))
337 -|(((
338 -
339 -)))|(((
340 -Abandoned
341 -)))|(((
342 -BOTH
343 -)))
344 -|(((
345 -Package Status
346 -)))|(((
347 -
348 -)))|(((
349 -KNOWN
350 -)))
351 -|(((
352 -Package Transaction
353 -)))|(((
354 -
355 -)))|(((
356 -KNOWN
357 -)))
358 -|(((
359 -Source Code
360 -)))|(((
361 -Selected
362 -)))|(((
363 -KNOWN
364 -)))
365 -|(((
366 -Web
367 -)))|(((
368 -Viewed
369 -)))|(((
370 -BOTH
371 -)))
372 -|(((
373 -Product Transaction
374 -)))|(((
375 -Subscribed
376 -)))|(((
377 -KNOWN
378 -)))
379 -|(((
380 -
381 -)))|(((
382 -Currently Subscribed
383 -)))|(((
384 -KNOWN
385 -)))
386 -|(((
387 -
388 -)))|(((
389 -Not Subscribed
390 -)))|(((
391 -BOTH
392 -)))
393 -|(((
394 -
395 -)))|(((
396 -Unsubscribed
397 -)))|(((
398 -KNOWN
399 -)))
400 -|(((
401 -GEO
402 -)))|(((
403 -IS IN
404 -)))|(((
405 -BOTH
406 -)))
407 -|(((
408 -Engagement Metric
409 -)))|(((
410 -
411 -)))|(((
412 -KNOWN
413 -)))
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 -)))
210 +[[image:attach:media_1443035194695.png||align="center"]]
424 424  
212 +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.
425 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.
214 +=== Step 4 – Review and Save ===
427 427  
216 +[[image:attach:media_1446742842763.png||align="center"]]
428 428  
429 -**5. Action tab: **
218 +Review all of the information for your persona, and click "Save Persona" to save.
430 430  
431 -Any action to be associated for segment targeting is defined in this tab.
220 +If you wish to make changes, click the "Back" button to move backward through the steps.
432 432  
433 -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.
434 434  
435 - [[image:attach:image2021-10-25_16-59-19.png||width="794"]]
436 436  
437 -== ==
438 -
439 -{{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.
440 -
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.
442 -
443 -=== ===
444 -
445 -=== ===
446 -
447 -{{id name="CreateAdAction"/}}
448 -
449 -=== **ADD AN AD ACTION** ===
450 -
451 -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.
452 -
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.
454 -
455 -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.
456 -
457 -ONEcount targets ads based on identity. ONEcount is saying in effect, for this specific person (as defined by the Segment linked to this Action), show this ad. Period.
458 -
459 -The Target Domain and Section options are used to limit this behavior. So what we are saying then is that for this specific person (as defined by the Segment linked to this Action) show this ad, but ONLY on these domains and in these specific sections of the site.
460 -
461 -Why would we do that? Generally, this is limitation is used because we want to target a user with one ad campaign on one site, and a different campaign on another site.
462 -
463 -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.
464 -
465 -
466 - [[image:attach:image2021-10-25_17-16-33.png||width="794"]]
467 -
468 -
469 -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.
470 -
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 -
475 -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.
476 -
477 -* In Revive/OpenX, these variables are created under Inventory > Banner > Delivery Options > Add Delivery Limitation > Site-Variable > Add > enter Key and Value variables. These variables are of your choosing and can be text or num
478 -
479 -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.
480 -
481 -NOTE: Prioritization of banners is done in Google Ad Manager (or DFP) based on rules you configure in GAM.
482 -
483 -=== ===
484 -
485 -=== ===
486 -
487 -{{id name="CreatePopupAction"/}}
488 -
489 -=== ADD A POP-UP ACTION ===
490 -
491 -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.
492 -
493 -Choose Pop-Up from the Action Type pull-down.
494 -
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.
496 -
497 -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.
498 -
499 -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.
500 -
501 -The Target Domain and Section options are used to limit this behavior. So what we are saying then is that for this specific person (as defined by the Segment linked to this Action) show this pop-up, but ONLY on these domains and in these specific sections of the site.
502 -
503 -Why would we do that? Generally, this is limitation is used because we want to target a user with pop-up campaign on one site, and a different campaign on another site.
504 -
505 -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.
506 -
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.
508 -
509 -
510 - [[image:attach:Action-Tab.png||width="600"]]
511 -
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.
513 -
514 -[[image:attach:add-url.png||height="121"]]
515 -
516 -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.
517 -
518 -Frequency allows you determine how frequently this pop-up will appear to this user. Options include once, always (on every page load), daily (once per day), weekly, bi-weekly, monthly, or annually.
519 -
520 -Last, select the pop-up (it can be any pop-up form builder pop-up or A/B test pop-up).
521 -
522 -Review your Action details and finally click Save to save it.
523 -
524 -
525 -(% style="margin-left: 30.0px;" %)
526 -=== **ADD A SOCIAL TARGET ACTION** ===
527 -
528 -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.
529 -
530 -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.
531 -
532 -**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.
533 -
534 -[[https:~~/~~/support.google.com/adspolicy/answer/6299717>>url:https://support.google.com/adspolicy/answer/6299717||shape="rect"]]
535 -
536 -**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.
537 -
538 -[[https:~~/~~/www.linkedin.com/help/linkedin/topics/6400/6401/112188>>url:https://www.linkedin.com/help/linkedin/topics/6400/6401/112188||shape="rect"]]
539 -
540 -
541 -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.
542 -
543 -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.
544 -
545 -[[image:attach:Screen Shot 2021-11-17 at 18.36.23.png||height="250"]]
546 -
547 -
548 -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.
549 -
550 -
551 -[[image:attach:Screen Shot 2021-11-17 at 18.48.18.png||width="800"]]
552 -
553 -
554 -(% style="margin-left: 30.0px;" %)
555 -=== ===
556 -
557 -{{id name="CreateRedirectAction"/}}
558 -
559 -(% style="margin-left: 30.0px;" %)
560 -=== **ADD A REDIRECT ACTION** ===
561 -
562 -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.
563 -
564 -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.
565 -
566 -As with pop-up and ad targeting, the Target Domain and Section parameters are optional.
567 -
568 -
569 - [[image:attach:image2021-10-25_18-2-56.png||height="250"]]
570 -
571 -
572 -(% style="margin-left: 30.0px;" %)
573 -=== ===
574 -
575 -{{id name="CreateEmailAction"/}}
576 -
577 -(% style="margin-left: 30.0px;" %)
578 -=== ADD EMAIL ACTION ===
579 -
580 -(% style="margin-left: 30.0px;" %)
581 -To send a transactional e-mail to a user, choose Email from the Action Type  pull-down.
582 -
583 -
584 -(% style="margin-left: 30.0px;" %)
585 -[[image:attach:image2021-10-25_18-6-13.png||width="794"]]
586 -
587 -
588 - 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.
589 -
590 -
591 -If you wish to cancel the changes, click the "Cancel" button to go to the segment listing page.
592 -
593 -
594 -== ==
595 -
596 -== ==
597 -
598 -{{id name="CreateTarget"/}}
599 -
600 -
601 -
602 -
603 -
604 -
605 -
606 -
607 -
608 -
609 -
610 -
611 -
612 -
613 613  {{id name="End ScreenSteps Content"/}}
614 614  {{/layout-cell}}
615 615  
616 616  {{layout-cell}}
617 617  {{panel title="Search All Documentation:"}}
229 +
230 +
618 618  {{livesearch/}}
619 619  {{/panel}}
620 620  
621 621  {{panel title="Search USER OPERATIONS Documentation:"}}
235 +
236 +
622 622  {{pagetreesearch rootPage="User Operations - Managing Your Data"/}}
623 623  {{/panel}}
624 624  
625 625  {{panel title="On this page:"}}
241 +
242 +
626 626  {{toc/}}
627 627  {{/panel}}
628 628  
629 629  {{panel title="More USER OPERATIONS Documentation"}}
630 -{{expand title="Click here to expand..."}}
631 - **Add Users**
247 +{{expand}}
248 + **Add Users
249 +**
632 632  
251 +(% style="margin-left: 60.0px;" %)
633 633  
634 634  
635 635  (% style="margin-left: 60.0px;" %)
636 -[[Preparing for Data Import>>doc:Getting Started - Preparing for Data Import]]
255 +[[Preparing for Data Import>>doc:Getting Started - Preparing for Data Import (v12\.x)]]
637 637  
638 638  (% style="margin-left: 60.0px;" %)
639 -[[doc:Pre-Import Checklist]]
258 +[[Pre-Import Checklist>>doc:Pre-Import Checklist (v12\.x)]]
640 640  
260 +(% style="margin-left: 60.0px;" %)
641 641  
642 642  
643 643  (% style="margin-left: 60.0px;" %)
644 -[[How to Create an Import Mapping Template>>doc:Import - How to Create an Import Mapping Template]]
264 +[[How to Create an Import Mapping Template>>doc:Import - How to Create an Import Mapping Template (v12\.x)]]
645 645  
646 646  (% style="margin-left: 60.0px;" %)
647 -[[How to Use an Import Mapping Template>>doc:Import - How to Use an Import Mapping Template]]
267 +[[How to Use an Import Mapping Template>>doc:Import - How to Use an Import Mapping Template (v12\.x)]]
648 648  
649 649  (% style="margin-left: 60.0px;" %)
650 -[[doc:Add Audience]]
270 +[[Add Audience>>doc:Add Audience (v12\.x)]]
651 651  
652 652  (% style="margin-left: 30.0px;" %)
653 653  **Batch Operations**
654 654  
655 655  (% style="margin-left: 60.0px;" %)
656 -[[doc:Bulk Operation - How to Perform a Batch Delete]]
276 +[[Bulk Operation - How to Perform a Batch Delete>>doc:Bulk Operation - How to Perform a Batch Delete (v12\.x)]]
657 657  
658 658  (% style="margin-left: 60.0px;" %)
659 -[[doc:Bulk Operation - How to Perform a Batch Product Change]]
279 +[[Bulk Operation - How to Perform a Batch Product Change>>doc:Bulk Operation - How to Perform a Batch Product Change (v12\.x)]]
660 660  
661 661  (% style="margin-left: 60.0px;" %)
662 -[[doc:Bulk Operation - How to Perform a Batch Status Change]]
282 +[[Bulk Operation - How to Perform a Batch Status Change>>doc:Bulk Operation - How to Perform a Batch Status Change (v12\.x)]]
663 663  
664 664  (% style="margin-left: 60.0px;" %)
665 -[[Bulk Operation - How to Perform a Batch Suscribe>>doc:Bulk Operation - How to Perform a Batch Subscribe]]
285 +[[Bulk Operation - How to Perform a Batch Suscribe>>doc:Bulk Operation - How to Perform a Batch Subscribe (v12\.x)]]
666 666  
667 667  (% style="margin-left: 60.0px;" %)
668 -[[Bulk Operation - How to Perform a Batch Unsubscribe>>doc:Bulk Operation - How to Perform a Batch UnsubscribeKill]]
288 +[[Bulk Operation - How to Perform a Batch Unsubscribe>>doc:Bulk Operation - How to Perform a Batch UnsubscribeKill (v12\.x)]]
669 669  
670 670  (% style="margin-left: 60.0px;" %)
671 -[[Bulk Operation - How to Perform a Merge of Duplicate Users>>doc:Bulk Operation - How to Perform a Bulk Merge of Duplicate Users]]
291 +[[Bulk Operation - How to Perform a Merge of Duplicate Users>>doc:Bulk Operation - How to Perform a Bulk Merge of Duplicate Users (v12\.x)]]
672 672  
673 673  (% style="margin-left: 30.0px;" %)
674 674  **Target Audience Segments**
675 675  
676 676  (% style="margin-left: 60.0px;" %)
677 -(% style="color:#003366" %)
297 +(% style="color: rgb(0,51,102);" %) __
298 +__
678 678  
300 +
679 679  
680 680  
681 681  {{/expand}}
682 682  {{/panel}}
683 683  
306 +
684 684  
308 +
685 685  
310 +
686 686  
312 +
687 687  
314 +
688 688  
689 689  
690 690  {{/layout-cell}}
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 +67554
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/67554/Utilities - Target Engine (v12.x)