2. Taxonomy Definition

The client must send to Retargetly support a list of segments that will be received for the users. The taxonomy should be in TSV or CSV format. Afterwards Retargetly will return the same list but attaching the corresponding Segment IDs (segmentId) within the DMP platform.

This IDs can also be obtained from the DMP platform, logging in with the provided user and password.

If partner has its own segment ids and wishes to use them when ingesting data files, they should be included on the taxonomy definition file (partnerSegmentId field) and notify Retargetly's support, in order to set the needed segment mapping.

If Retargetly's segment ids will be used for data ingestion, then partnerSegmetnId parameter is not needed. The required fields are:

  • name (mandatory) {Segment name}. Only include the last and main name of the segment, without segment full path. Example: Rock.
  • fullname (mandatory) {Segment full name}. It should be the segment full path, including all segment parent hiearchy, splitting each level with ">" character. For example: Entertainment > Music > Rock.
  • buyable [0/1] (obligatorio) {Segment buyable yes/no}. It indicates whether the segment should be available to purchase on Retargetly's different marketplaces.
  • CPM [number] (mandatory if buyable = 1) {Segment license price}. Its the price in US dolars for the segment to be purchased on the marketplaces (DSPs).
  • partnerSegmentId [a-z0-9] (optional) {Partner's own segment identifier}. Only include this field if partner segment ids will be used on data files.
  • description (optional) {Short description of the segment}.

If buyable = 1 is specified (this means segment will be created and licensed into the different marketplaces), Retargetly's support should be notified what kind of licenses the partner wishes to use: Private or Public. If Private, then segments will be licensed to specific platforms accounts provided for the Partner. Otherwise, if Public licenses are needed, the segments will be avaible to purchase as Branded Data inside Retargetly's standard taxonomy on the different marketplaces avaiable.

How did we do?

1. User Cookie Sync Process

3. Data file Ingestion

Contact