Powered Lists Data

Rebekah Garner
Rebekah Garner
  • Updated

About Powered List Data

Powered Lists maps template submission data to a list. The list is then available to use in other templates. With Powered Lists, Admins can enable cleaner, more streamlined data used in a list by:

  • Avoiding manually updating list values
  • Adding field governance and restrictions to maintain accuracy of the data in lists
  • Using imported list values from other platforms (i.e., Product Name, Campaign Name, external platform IDs, etc.)
  • Automating list updates by integrating with API, AWS S3, and SFTP to the List-Powering Template with an inbound integration

Terminology

  • List-Powering Template: Fields configured to generate the data used in the powered list.
  • Template Data: All data created using the List-Powering Template.
  • Powered List: The pick list that is updated automatically from the List-Powering Template for the data.

Ideas of How to Use Powered Lists:

  • Creating GCM Campaign Name, Placement Name, Creative Name, and Ad Name with specific taxonomies, to use in the Claravine+GCM integration template (pending submissions).
  • Creating Facebook Ad Account Name, Ad Set Name, and Ad Names with specific taxonomies, to use in the Claravine+Facebook integration template (pending submissions).
  • Creating Global Campaign IDs and Names to be associated with publications or posts.
  • Creating a pattern using dynamic parameters and classifying the populated parameters from Adobe after consumer click. (i.e. em_12345:{Site ID}
  • Using a template to update a list.
  • Using File Import to update a list.
  • Using Inbound Template Configurations to drop/export data from other platforms for auto-submissions from an AWS S3 folder or SFTP to update a list.

Things to Know

  • The data from the submission will be available in the Powered List when the submission process is complete (green check mark on the Submission page), this may take a few minutes.
  • Powered List column names will default from the field names as they appear in the template.
  • The order of the template is the default order of columns in the Powered List. The Admin can reorder the List to move a column to the start. The first column must be the selector list of values.
  • You can create many Powered Lists from the List-Powering Template.
  • To edit the value in the Powered List, edit the template data view or submission. You cannot edit at the Pick List.
  • Looking at the Powered List data in the Pick List menu view, the data is not sorted by the order in which it was submitted, it is sorted by an internal Claravine ID.
  • Pro Tip: To be able to view and sort your data by the date it was created, you can add an auto-date field to your List-Powering Template that adds the date of the submission.
  • If a Powered List is edited to change the order of the columns, the Admin must remap any fields referencing the Powered List. Fields are mapped to the column number in the list and will not move/follow the updates to column ordering.
  • Deleting rows of data in the template data that populates the Powered List is not available.
  • Powered Lists can currently create drop down lists and dependent lists.
  • Once a Powered List i s created from a List-Powering template, new fields added to the template schema will be appended to the List at the end and will not follow the schema ordering.
  • Do not delete a field from a List-Powering template. Unpower the list, make changes to the template, repower the list, and save the fields mapped to the Powered List.

Creating a Drop Down Powered List

  1. Determine the List-Powering Template. All submissions (new and existing) committed using this template will populate the List.

    If the template does not exist, follow the steps in the Create a New Template Start to Finish to create the Pattern, Lists, Field Sets, and Template.

  2. Create a submission using the List-Powering Template.
    The submission must fully process before it is in the powered list. When the submission status is a green checkmark, continue to step 3.

  3. Click Settings on the Navigation menu.

  4. Click Pick Lists in the Elements Sub-Navigation menu.
    The Pick Lists page displays.


  5. Click to create a new List.
    The Edit Pick List menu displays.

  6. Enter the List Name and Description (optional) in the designated fields.
    We recommend entering a description to make it easier to determine the use of the list, noting the List-Powering Template is good practice.

  7. Select the List Type as Drop Down.


  8. Click Power With Template.

  9. Select the (list-powering) Template from the drop down menu. You can select any column of any template to power the list from.


  10. Select the Column if creating a Drop Down Powered List.

  11. Click Confirm.


    The Powered List will generate the column selected. The template that is powering this list is noted for reference.

  12. Click Save to save the List.

Creating a Dependent Powered List

  1. Determine the List-Powering Template. New submissions committed using this template will populate the List.

    If the template does not exist, follow the steps in the Create a New Template Start to Finish to create the Pattern, Lists, Field Sets, and Template.
  2. Create a submission using the List-Powering Template.
    The submission must fully process before it is in the powered list. When the submission status is a green checkmark, continue to step 3.

  3. Click Settings on the Navigation menu.

  4. Click Pick Lists in the Elements Sub-Navigation menu.
    The Pick Lists page displays.


  5. Click to create a new List.
    The Edit Pick List menu displays.

  6. Enter the List Name and Description (optional) in the designated fields.
    We recommend entering a description to make it easier to determine the use of the list, noting the List-Powering Template is recommended.

  7. Select the List Type as Dependent.


  8. Click Power With Template.

  9. Select the (list-powering) Template from the drop down menu.


  10. Click Confirm.
    The Powered List will generate the columns exactly in the order of the fields as they appear in the template.


    The template that is powering this list is noted for reference.

  11. Right-click on a column to Move Column To Start to reorder the columns.


    If this Powered List is mapping to a Field Set, confirm the ordering is in the sequential order you need with your selecting field in column 1 position.


  12. Click Save to save the List.

Using a Powered List

Map the Powered List to Fields

  1. Associate the Powered List columns to fields in a field set:
    • Map to an existing field in a field set
    • Map to a new in a field set
    • Create a new field set and map new fields to the Powered List
    • Review the Field Sets Overview Knowledge Base article for instruction about field sets and field configuration
  2. Click Field Set in the Elements Sub-Navigation menu.

  3. Open the appropriate Field Set.

  4. If the field does not exist in the field set: Click Add New Field.
    • Enter the Name (required)
    • Click mceclip0.png to Import the List to import all columns of the list.

  5. If the field does exist in the field set: Click the Field Name to edit.

  6. Description (optional). The Description shows as a tool tip in the Submission Table.

  7. Select Required Field (optional). The field will be mandatory for the user to fill in.

  8. Select the Type as List.

  9. Select the Powered Pick List Name from the drop down menu or begin typing the pick list name.

  10. Select the column to associate to this field.

  11. Click Done. Repeat for all necessary columns of the Powered List.

  12. Click Save to save the Field Set.

Add New Powered List Fields to Template

  1. If a new field is created to associate with the Powered List, follow the standard steps to add the field to the necessary templates.

    Review the Step 2 - Define and Govern in a Template Knowledge Base article for instruction about adding fields to a template.
  2. Click Templates in the Templates Sub-Navigation menu.

  3. Open the appropriate Template.

  4. Click + Select Fields.

  5. Check the box to select all the fields in the Field Set or click the drop down menu to select individual fields.

  6. Click Select Fields.

  7. Configure the template schema as needed to address the new field: reorder, visible, required, set default value as applicable.

  8. Click Save to save the template.

Example Use Case and Configuration

Global Campaign Name to Regional Campaigns

This example allows Regional offices to reference a Global Campaign Name and ID list in their regional campaigns.

List-Powering Template “Create Global Campaign ID”

Pattern = {Global Campaign Name}_AutoNumber

Global Campaign Name

Creation Date

Business Unit

Campaign Details

Powered List “Global Campaign Name and ID” is powered from Template “Create Global Campaign ID”

Global Campaign Name

Global Campaign ID (Auto#)

Creation Date

Business Unit

Campaign Details

Link the new Powered List data to the Regional External Campaigns template fields.

Update Regional External Campaigns template if new fields are added.

Template “Regional External Campaigns”

Pattern = {Global Campaign Name_Global ID}_{Country Code}_{Language}

Global Campaign Name

Global Campaign ID (automated based on Global Campaign Name selected)

Creation Date (automated based on Global Campaign Name selected)

Business Unit (automated based on Global Campaign Name selected)

Campaign Details (automated based on Global Campaign Name selected)

Region

Country

Country Code

Language

Creative Image Name

Creative Size

Vanity URL

Google Campaign Manager (GCM) Campaign Name + Integration

This example allows for the creation and standardization of GCM campaign names, and provides the ability to auto-populate the associated data in the final integration template upon sync.

List-Powering Template “Campaign Name”

Pattern = {CampaignInfo (no spaces)}_{Fiscal Year abbreviation}_{Agency (no spaces)}_{Campaign Type}_{Campaign Detail}

Campaign Info

Fiscal Year

Agency

Campaign Type

Campaign Detail

Powered List “Powered Campaign Name” is powered from Template “Campaign Name”

GCM: Campaign Name

Campaign Info

Fiscal Year

Agency

Campaign Type

Campaign Detail

Repeat for GCM Placement Name, GCM Creative Name, GCM Ad Name as needed.

Link the new Powered List data to the GCM Integration template fields.

Update the GCM Integration template if new fields are added.

Template “GCM Integration”

This template utilizes the Claravine + GCM inbound integration to bring in the GCM IDs and associated GCM Names. The Names are mapped on the template to the fields linked to the Powered Lists, using the Name to associate the classification data.

Now GCM Tracking Codes that were created using macros that were previously unspecified are fully defined and classified in Adobe.

Pattern = DFA:{Campaign ID}:{Creative ID}:{Placement ID}

GCM: Campaign Name (inbound data from GCM, referenced Powered Campaign Name)

Creation Date (automated based on GCM: Campaign Name selected)

Campaign Info (automated based on GCM: Campaign Name selected)

Fiscal Year (automated based on GCM: Campaign Name selected)

Agency (automated based on GCM: Campaign Name selected)

Campaign Type (automated based on GCM: Campaign Name selected)

Campaign Detail (automated based on GCM: Campaign Name selected)

GCM: Creative Name (inbound data from GCM, referenced Powered Creative Name)

Creative Template Name (automated based on GCM: Creative Name selected)

Creative Type (automated based on GCM: Creative Name selected)

Creative Audience (automated based on GCM: Creative Name selected)

Ad Server (automated based on GCM: Creative selected)

Ad Size (automated based on GCM: Creative Name selected)

GCM: Placement Name (inbound data from GCM, referenced Powered Placement Name)

Media Tactic (automated based on GCM: Placement Name selected)

Data Source (automated based on GCM: Placement Name selected)

Platform (automated based on GCM: Placement Name selected)

Ad Type (automated based on GCM: Placement selected)

Placement Description (automated based on GCM: Placement Name selected)

 

Learn More

Comments

0 comments

Article is closed for comments.