Changes for page Segment Manager

Last modified by Admin User on 2025/01/24 16:21

From 5.1 to 4.1 From 12.1 to 11.1

From version 11.1

edited by Admin
on 2020/01/05 19:38

Change comment: There is no comment for this version

To version 5.1

edited by melanie@one-count_com
on 2016/12/08 11:56

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (3 modified, 0 added, 0 removed)
Objects (1 modified, 0 added, 0 removed)
- Confluence.Code.ConfluencePageClass[0]

Details

Page properties

Title

@@ -1,1 +1,1 @@
--Utilities - Target Engine
++Utilities - Target Engine  (v12.x)

Author

@@ -1,1 +1,1 @@
--XWiki.Admin
++XWiki.melanie@one-count_com

Content

@@ -4,11 +4,11 @@
  {{id name="Start ScreenSteps Content"/}}
--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.
++ 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.
  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.
--The following lesson will provide details on how to use the **Segment Manager**, **Action Manager**, and **Target Engine**.
++The following lesson will provide details on how to use the Targeting Engine / Persona Manager.
  === Please Note: ===
@@ -18,259 +18,200 @@
  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.
--=== CREATING A NEW SEGMENT ===
++=== OPENING THE TARGETING AUTOMATION & PERSONALIZATION (TAP) WINDOW ===
--From the Segment Manager menu, select Segment Manager:**
--**
++=== Select UTILITIES from the main menu. ===
--[[image:attach:segment manager menu.png||width="800"]]
++[[image:attach:media_1436816640442.png||align="center"]]
--\\
++=== Select TARGETING ENGINE from the sub-menu. ===
--You will see a list of existing segments. Click "Create Segment" in the upper right-hand corner.
++[[image:attach:media_1436816664853.png||align="center"]]
--[[image:attach:manage segments.png||height="250"]]
++This will open the Targeting Automation & Personalization (TAP) window displaying a list of existing personas, if any, as shown below.
--\\
++[[image:attach:media_1436816784643.png||align="center"]]
--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.
++Expanding the details of a persona will show you the target segment and actions for that persona. (See screenshot below.)
--[[image:attach:segment-definion.png||height="250"]]
++[[image:attach:media_1437059609834.png||align="center"]]
--\\
++Clicking on the "i" (information) icon will display a pop-up with details of the action to perform, as shown below.
--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.
++[[image:attach:media_1437064543783.png||align="center"]]
--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.
++=== CREATE A NEW PERSONA ===
--=== CREATE A DEMOGRAPHIC SEGMENT ===
++=== Click "Create Persona" button ===
--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.
++[[image:attach:media_1437064785909.png||align="center"]]
--[[image:attach:segment-demos.png||height="250"]]
++This will open the Profile window, which is Step 1 in creating the persona.
--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.
++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".
--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.
++**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.**
--In this way, you can create a demographic segment of users who are Pediatricians who live in Arizona, for example.
++=== Step 1 – Profile ===
--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.
++[[image:attach:media_1437065487760.png||align="center"]]
--\\
++Complete the Name, Description, and Effective Date Range fields for the persona, then click the "Next" button.
--[[image:attach:segment-content.png||height="250"]]
++=== Step 2 – Segment ===
--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.
++A "Segment" is a subgroup of your user universe that you wish to target with a specific action.
--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.
++You can define a target segment by User – including Product, Demographics, Source Code, Newsletter, or Web filters – or by Account.
--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.
++**Product** – Allows you to segment based on a product subscription status
++ **Demographics** – Allows you to segment based on whether a user meets or does not meet specified demographic criteria
++ **Source Code** – Allows you to segment based on assigned or not assigned Source Code
++ **Newsletter** – Allows you to segment based on whether a user has or has not opened or clicked on a specified newsletter
++ **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).
--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.
++See directions for creating a segment of all users, both known and unkown, in //**B. Segment by Account**// below.
--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).
++You may select multiple filters and multiple options within filters.
--There is a wide range of behavioral criteria that can be used for behavioral segments:
++=== A. Segment by User ===
--**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).
++[[image:attach:media_1437075145033.png||align="center"]]
--**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.
++The screenshot above is from v. 11.6. Prior versions do not have the "With"/"Without" option.
--**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.
++Notice the "AND" / "OR" logic that can be used to join different filters for the segment. Multiple selections //within// a filter use "OR" logic.
--**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.
++**To add additional criteria to a segment, click the "And" or "Or" button.**
--**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.
++In the example above, the targeted segment is all users who:
--**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.
++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;
--**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.
++**AND**
++ B. have ('With") opened the "...ain Today" newsletter;
++ **OR**
++ C. have ("With") Primary Business Category that contains "Industrial Mfg., Including Plastics & Rubber... " _OR "_High-Tech Computers/Electronics".
--**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.
++**That is, all users who fit criteria A AND fit either criteria B OR C** * Notice the separator line when AND is selected.
--**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.
++=== B. Segment by Account ===
--**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.
++[[image:attach:media_1437079883697.png||align="center"]]
--Once you have defined your First Party (demographic) and Behavioral criteria for your segment, be sure to **HIT SAVE.**
++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.
--\\
--
--(% style="margin-left: 30.0px;" %)
--=== CREATE AN ACCOUNT-BASED SEGMENT ===
--
--(% style="margin-left: 30.0px;" %)
--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.
--
--(% style="margin-left: 30.0px;" %)
  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.
--(% style="margin-left: 30.0px;" %)
  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...
--(% style="margin-left: 30.0px;" %)
  Note that only OR logic is used in Account segmenting and that you can enter multiple IP addresses and user agents in each field.
  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.
--== **CREATE AN ACTION** ==
++=== Step 3 – Action ===
--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
++"Action" is where you define the action to be taken for the identified segment, e.g. a website pop-up or ad targeting.
--\\
++Types of Actions include: Pop-Up, Redirect, Ad Target, Email
--[[image:attach:Action-manager menu.png||width="800"]]
++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).
--\\
++[[image:attach:media_1442601673145.png||align="center"]]
--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.
++Hover over an action to see details (see screenshot below).
--\\
++[[image:attach:media_1442602167866.png||align="center"]]
--[[image:attach:action-manager.png||height="250"]]
++=== A. Create Pop-Up ===
--\\
++~1. Click "New action".
++ 2. Give the action a name and description (optional).
++ 3. Click "Next".
++ 4. Complete the fields as shown below.
++ 5. Click "Next".
--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.
++[[image:attach:media_1442611132544.png||align="center"]]
--\\
++Upon clicking "Next", you'll have an opportunity to review the action and "Save" or go "Back" to make changes.
--[[image:attach:define-action.png||height="250"]]
++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.)
--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.
++Click "Next" to continue to Step 4 – Review and Save.
--=== **CREATE AN AD TARGET** ===
++[[image:attach:media_1443034475680.png||align="center"]]
--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.
++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.
--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.
++[[image:attach:media_1443033012905.png||align="center"]]
--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.
++Note that the display opt-out will appear only if checked when creating the pop-up action.
--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.
++=== B. Create Redirect ===
--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.
++~1. Click "New action".
++ 2. Give the action a name and description (optional).
++ 3. Click "Next".
++ 4. Complete the fields as shown below.
++ 5. Click "Next".
--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.
++[[image:attach:media_1442947217827.png||align="center"]]
--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.
++Upon clicking "Next", you'll have an opportunity to review the action and "Save" or go "Back" to make changes.
--[[image:attach:Define-banner-target.png||height="250"]]
++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.)
--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.
++Click "Next" to continue to Step 4 – Review and Save.
--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.
++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.
--* 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
++=== C. Create Ad Target ===
--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.
++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.
--NOTE: Prioritization of banners is done in Google Ad Manager (or DFP) based on rules you configure in GAM.
++~1. Click "New action".
++ 2. Give the action a name and description (optional).
++ 3. Click "Next".
++ 4. Complete the fields as shown below.
++ 5. Click "Next".
--=== CREATE A POP-UP TARGET ===
++[[image:attach:media_1446742365693.png||align="center"]]
--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.
--
--Choose Pop-Up from the Action pull-down at the top.
--
--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.
--
--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.
--
--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.
--
--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.
--
--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.
--
--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.
--
--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.
--
--[[image:attach:pop-up-action.png||width="800"]]
--
--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.
--
--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.
--
--Last, define the pop-up.
--
--ONEcount includes a simple pop-up builder that allows you to build a pop-up with buttons that link out to other actions like forms, web pages, etc.
--
--Simply add the header or title for your pop-up, and then the text you want to appear in the box. Check the Display Opt out box if you want the pop-up to include an option to prevent future pop-ups. Choose how many action buttons you would like on the pop-up, and define the button text and the link that the user is sent to when they click on the button.
--
--If you have pop-up code that your web team has built, you can click on the Custom HTML tab and paste your code in the box.
--
--[[image:attach:custom-popup-box.png||width="800"]]
--
--Click Next to review your Action definition, and finally Save to save it.
--
--This is an example of ONEcount's built-in pop-ups:
--
--(% style="margin-left: 30.0px;" %)
--[[image:attach:media_1443033012905.png||align="center"]]
--
--(% style="margin-left: 30.0px;" %)
--Note that the display opt-out will appear only if checked when creating the pop-up action.
--
--(% style="margin-left: 30.0px;" %)
--=== **CREATE A REDIRECT ACTION** ===
--
--Choose redirect from the list of Actions. The redirect action is very similar to the Pop-Up action, except that instead of displaying a pop-up message, ONEcount will redirect the user to a URL of your choosing.
--
--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.
--
--As with pop-up and ad targeting, the Target Domain and Section parameters are optional.
--
--\\
--
--(% style="margin-left: 60.0px;" %)
--[[image:attach:media_1442947217827.png||align="center"]]
--
--(% style="margin-left: 60.0px;" %)
  Upon clicking "Next", you'll have an opportunity to review the action and "Save" or go "Back" to make changes.
--(% style="margin-left: 60.0px;" %)
  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.)
--(% style="margin-left: 60.0px;" %)
  Click "Next" to continue to Step 4 – Review and Save.
--(% style="margin-left: 60.0px;" %)
--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.
++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.
--(% style="margin-left: 30.0px;" %)
--Click "Next" to continue to Step 4 – Review and Save.
++* 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.
--(% style="margin-left: 30.0px;" %)
++[[image:attach:media_1443036194948.png||align="center"]]
++
  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.
--(% style="margin-left: 30.0px;" %)
--=== CREATE E-MAIL ACTION ===
++=== D. Create Email ===
--(% style="margin-left: 30.0px;" %)
--To send a transactional e-mail to a user, choose Email from the Action pull-down.
++~1. Click "New action".
++ 2. Give the action a name and description (optional).
++ 3. Click "Next".
++ 4. Complete the fields as shown below.
++ 5. Click "Next".
--(% style="margin-left: 30.0px;" %)
  [[image:attach:media_1442946953775.png||align="center"]]
--(% style="margin-left: 30.0px;" %)
  Upon clicking "Next", you'll have an opportunity to review the action and "Save" or go "Back" to make changes.
--(% style="margin-left: 30.0px;" %)
  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.)
--(% style="margin-left: 30.0px;" %)
  Click "Next" to continue to Step 4 – Review and Save.
--(% style="margin-left: 30.0px;" %)
  [[image:attach:media_1443035194695.png||align="center"]]
--(% style="margin-left: 30.0px;" %)
  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.
--==== Step 4 – Review and Save ====
++=== Step 4 – Review and Save ===
  [[image:attach:media_1446742842763.png||align="center"]]
@@ -284,27 +284,25 @@
  {{/layout-cell}}
  {{layout-cell}}
--{{panel title="Search All Documentation:"}}
++**Search all Documentation:**
++
  {{livesearch/}}
--{{/panel}}
--{{panel title="Search USER OPERATIONS Documentation:"}}
++
++**Search USER OPERATIONS Documentation:**
--{{pagetreesearch rootPage="User Operations - Managing Your Data"/}}
--{{/panel}}
--{{panel title="On this page:"}}
++{{pagetreesearch rootPage="User Operations - Managing Your Data"/}}
--{{toc/}}
--{{/panel}}
++
--{{panel title="More USER OPERATIONS Documentation"}}
--{{expand}}
-- **Add Users
++{{expand title="More USER OPERATIONS Documentation"}}
++(% style="margin-left: 30.0px;" %)
++**Add Users
  **
  (% style="margin-left: 60.0px;" %)
@@ -311,43 +311,43 @@
  (% style="margin-left: 60.0px;" %)
--[[Preparing for Data Import>>doc:Getting Started - Preparing for Data Import]]
++[[Preparing for Data Import>>doc:Getting Started - Preparing for Data Import (v12\.x)]]
  (% style="margin-left: 60.0px;" %)
--[[doc:Pre-Import Checklist]]
++[[Pre-Import Checklist>>doc:Pre-Import Checklist (v12\.x)]]
  (% style="margin-left: 60.0px;" %)
++[[How to Import a File>>doc:Import - How to Import a File (v12\.x)]]
--
  (% style="margin-left: 60.0px;" %)
--[[How to Create an Import Mapping Template>>doc:Import - How to Create an Import Mapping Template]]
++[[How to Create an Import Mapping Template>>doc:Import - How to Create an Import Mapping Template (v12\.x)]]
  (% style="margin-left: 60.0px;" %)
--[[How to Use an Import Mapping Template>>doc:Import - How to Use an Import Mapping Template]]
++[[How to Use an Import Mapping Template>>doc:Import - How to Use an Import Mapping Template (v12\.x)]]
  (% style="margin-left: 60.0px;" %)
--[[doc:Add Audience]]
++[[Add Audience>>doc:Add Audience (v12\.x)]]
  (% style="margin-left: 30.0px;" %)
  **Batch Operations**
  (% style="margin-left: 60.0px;" %)
--[[doc:Bulk Operation - How to Perform a Batch Delete]]
++[[Bulk Operation - How to Perform a Batch Delete>>doc:Bulk Operation - How to Perform a Batch Delete (v12\.x)]]
  (% style="margin-left: 60.0px;" %)
--[[doc:Bulk Operation - How to Perform a Batch Product Change]]
++[[Bulk Operation - How to Perform a Batch Product Change>>doc:Bulk Operation - How to Perform a Batch Product Change (v12\.x)]]
  (% style="margin-left: 60.0px;" %)
--[[doc:Bulk Operation - How to Perform a Batch Status Change]]
++[[Bulk Operation - How to Perform a Batch Status Change>>doc:Bulk Operation - How to Perform a Batch Status Change (v12\.x)]]
  (% style="margin-left: 60.0px;" %)
--[[Bulk Operation - How to Perform a Batch Suscribe>>doc:Bulk Operation - How to Perform a Batch Subscribe]]
++[[Bulk Operation - How to Perform a Batch Suscribe>>doc:Bulk Operation - How to Perform a Batch Subscribe (v12\.x)]]
  (% style="margin-left: 60.0px;" %)
--[[Bulk Operation - How to Perform a Batch Unsubscribe>>doc:Bulk Operation  - How to Perform a Batch UnsubscribeKill]]
++[[Bulk Operation - How to Perform a Batch Unsubscribe>>doc:Bulk Operation  - How to Perform a Batch UnsubscribeKill (v12\.x)]]
  (% style="margin-left: 60.0px;" %)
--[[Bulk Operation - How to Perform a Merge of Duplicate Users>>doc:Bulk Operation - How to Perform a Bulk Merge of Duplicate Users]]
++[[Bulk Operation - How to Perform a Merge of Duplicate Users>>doc:Bulk Operation - How to Perform a Bulk Merge of Duplicate Users (v12\.x)]]
  (% style="margin-left: 30.0px;" %)
  **Target Audience Segments**
@@ -356,23 +356,10 @@
  (% style="color: rgb(0,51,102);" %) __
  __
--\\
++
--\\
++
  {{/expand}}
--{{/panel}}
--
--\\
--
--\\
--
--\\
--
--\\
--
--\\
--
--\\
  {{/layout-cell}}
  {{/layout-section}}
  {{/layout}}

Confluence.Code.ConfluencePageClass[0]

id

@@ -1,1 +1,1 @@
--23331698
++67552

url

@@ -1,1 +1,1 @@
--https://info.onecount.net//wiki/spaces/OD/pages/23331698/Utilities - Target Engine
++https://info.onecount.net//wiki/spaces/OD/pages/67552/Utilities - Target Engine  (v12.x)