Bulk Upload Segments FAQ

Why bulk upload segments?
The Salesforce DMP offers a bulk upload feature for loading segments into Konsole. The user can bulk define segments and its rules via a CSV file, and load them into Konsole. Contact your Salesforce DMP account team for a CSV template and directions on how to bulk upload segments. Leverage bulk upload segments if you plan to build a large quantity of segments at one time.

Segments created via bulk uploads are rule based. Rules are to be defined in the CSV file you provide to Salesforce. Rules or attribute values in the CSV file must exist in the Salesforce DMP before Salesforce can create the segments. It’s important to model the bulk upload file from existing attributes. If there is an attribute missing, the entire upload will fail to process.

Note: only first-party page attributes can be used in bulk segments.

Can I edit segments created via bulk uploads in Konsole?
Yes, you can. Unlike platform segments, bulk uploaded segments are rule based. Therefore, you can edit segment rules in Konsole for bulk-uploaded segments.

Can I edit segment rules via bulk upload?
You can utilize a bulk upload for editing existing segments.This would work as follows:

  • Bulk upload document will need to include current and exact segment name
  • ALL rules need to be included, not just the new addition
  • Rules that are not included will be deleted
  • The segment is essentially deleted and re-uploaded with the new rules

There is a separate CSV you have to upload if you wish to change only the segment metadata, such as the name and category. Please see this article for more info.

Can I bulk delete segments?

Yes you can. Contact your Salesforce DMP support team with a list of the segment IDs you want to delete.

Will bulk segment uploads be reflected in the segment history?

Can I interchange enable segments to certain partners via bulk segment uploads?
You can enable bulk-uploaded segments for interchange in Konsole, but you will not be able to define that via the bulk upload CSV.

What type of segments can I load via bulk segment uploads?
Standard and Real-time segments leveraging first-party page attributes only. 

Can rules leveraging existing segments be used in bulk uploads?
No, rules in bulk segment uploads can only utilize first-party attributes.

What is the default refresh set for Bulk Segments in Konsole?

1 in 30 days

How to create Bulk Segments

To get segments created in bulk, you first need to fill out the Bulk Segment Upload Template which can be found at the bottom of this article. Below are detailed instructions on how to use the template.

Once the file is ready, please open a Support ticket, attach the file and kindly ask DMP Support to upload the file for you

Attribute Values

  • All attribute values in the spreadsheet must exist and be enabled in the Salesforce DMP.
  • If the values have not already been added to the Attribute Tree in the UI, they will need to be created beforehand.
  • Only first-party page attributes can be used in bulk segments.

Spreadsheet Format

The following describes the process for creating a CSV file to auto-generate segments from large-volume rules.

The output should be a CSV (UTF-8 encoded, no headers) file where each row represents the rule-set for one segment.

  • Column A of the each row should contain the segment name.
  • Column B should be the Type
  • Column C should be the Category
  • Column D should be the Sub-Category
  • Column E should be 1 if the segment is real-time, 0 if it is not
  • Column F should be 1 if the segment should be enabled for O&O onsite, 0 if it is not

Each subsequent column is a rule “nest”, which is a string that contains the attributes and attribute values to be used. Columns are separated by a comma (,). The connector between two nests, AND or OR also needs a column on their own.

The variable names used must be exact matches to the variable names shown in the UI.

To define a nest, use the following operators in the content:











OR between nests


AND between nests (Note that nests do not support AND NOT)


Separator for multiple attribute values for one attribute — "OR" string.


CONTAINS operator for attribute value, instead of = (IS operator)
NOTE:  values used in contains must be quoted:

NOTE: Multiple values within a single ‘contains’ statement is not supported. NOT support:





must be equal to


Example 1

The rule: City=San Francisco OR City=New York

This would translate to: City=San Francisco|City=New York

Example 2

The rule:

(Age=18-25 or 26-35) OR (Age=46-55) AND (Device=Computer)

should be set as:


Example 3

Rule with nested AND:  

Search=SF Apartment OR City=San Francisco AND State=CA AND House_Type= Flat OR Apartment AND Studio

Would be represented by:

Search=SF Apartment|City=SanFrancisco;State=CA,AND,House_Type=Flat|Apartment;Studio


Example 4

The rule:

Age=18-25 AND Device=Mobile AND NOT Device=Computer

should be set as:


The variable names must be exact matches to the displayed variable names shown in the Salesforce DMP. Please use the attribute tree is segment builder as an easy reference.

Rules for multiple segments can be combined in the same sheet. Each segment should be represented on a separate row.


Bulk Segment Template

Have more questions? Submit a request


Please sign in to leave a comment.