Piano segments

Creating and exporting segments into Piano

The Piano technical documentation explains how the segment data from digitalAudience can be exported into Piano segments. For this data export to work, we need to setup the cookie sync between the client’s Piano instance and dAid within client’s web domains. The sync script will be used for this purpose. In this case, the ‘partner’ and 'parcid' parameters should be filled in in each page load.

‘partner’ = the ‘PO_xxxxxxxx’ Piano client id, produced by dA, should be used,

‘parcid’ = the Piano cookie id

populate parcid parameter with var ppoid = cX.getCxenseUserId();

Create a segment group in Piano to place the segments digitalAudience will provide.

Piano guidelines for data import

In short, Piano picks up the data export every day from our S3 bucket and maps the segment data we produce into its audiences.

Here is the section that explains the generic segment import into Piano;

Audience Overview

This section is used to let Piano know where to pick up our data exports daily and how to map our data files into Piano segments.

The important steps to be implemented;

Create file import connection

File import connection

This section explains how to setup an S3 connection, which will be used for the data exports later on. We need to create an S3 bucket for the client and create a specific folder for our data files. Necessary info from our side;

Access key: xxxxx

Secret key: xxxxx

Region: eu-central-1

Bucket name: da-production-transfer-CLIENTNAME

Prefix: 'exports/piano/'

Create data file imports

Data import setup

This section explains how to setup 2 flows; one for importing segment taxonomy (aka. External segments), the second for segment data (aka. Segment audiences).

• External segments

This setup is used to retrieve the segment taxonomy provided by dA to Piano. Here are the required settings for external segments;

• Import folder structure configuration (result will be similar to mapping/taxonomy.csv)

  • Folder: yes

  • Folder name type: Name

  • Folder name: mapping

• Import file structure configuration

  • File type: csv

  • File compression: No

  • File name type: Name

  • File name: taxonomy

• Segment audiences

This setup is used to retrieve the segment membership, adding Piano profiles to segments, provided by dA to Piano. dA will create a folder per day with data files in them, for that specific day. Here are the required settings for external segments;

• Import folder structure configuration (result will be similar to segments-20250314/segments.tsv.gz)

  • Folder: yes

  • Folder name type: Name structure

    • Static: segments

    • Delimiter: '-' (minus)

    • Date time > Year > yyyy

    • Date time > Month > MM

    • Date time > Day > dd

• Import file structure configuration

  • File type: TSV

  • File compression: Yes

  • File name type: Name

  • File name: segments

Data mapping configuration

Data mapping configuration

This section explains how to let Piano understand how the data is formatted within the files dA uploads.

• External segments

File Header: Yes

Column delimiter: <Comma>

Source segment ID: Column 1

Segment name: Column 2

Description: Column 3

Usage: Full

Segment group: Select the segment group created for dA segments, otherwise they will be created as ‘Ungrouped’

Here is a sample file Piano will receive;

204B

taxonomy sample.csv

• Segment audiences

File header: Yes

File includes segment IDs: Yes

Column delimiter: <Tab>

Segment ID: Column 2 | Many values | <Comma>

User ID: Column 1 | Single value

User ID type: cx

Here is a sample file Piano will receive;

76B

segments sample.tsv

File post processing configuration

Select ‘Move to the folder’ option.

Piano will create a ‘processed’ folder under the ‘segments’ folder and place the processed segments files in it.

Import frequency

Import frequency: Daily

Start import after: 4:00 UTC +1:00

Activate

Turn connection: On