DirectPass dataset file onboarding

10 min

directpass uses a specialized dataset onboarding and deployment workflow that allows the direct ingestion and deployment of raw device identifiers (such as device ids and ip addresses), without first resolving them to cadent's household graph directpass datasets don't include the household level information you can use directpass for the following targeting for non us regions, such as canadian segments used in ad manager passing raw identifiers directly to destination partners that have their own identity resolution systems note you must have directpass enabled for your organization to perform this type of data onboarding if interested, contact your account manager what happens when directpass is enabled? enabling this option provides the following results disables household export the standard household level export is turned off delivers raw ids the raw device ids and ip addresses from your original file are delivered directly to the destination partner provides raw counts the device id and ip reach counts shown on the deployment screen reflect the counts from your raw data, not the counts from the cadent graph allows subtype selection you can choose to deploy specific combinations of identifiers and their subtypes (for example, android devices + ipv4 only) after enabling the toggle and confirming your settings, you can deploy the audience as you normally would a tooltip over the toggle provides the following information to alert you when directpass is in use directpass deployments deliver ids to your destination without resolving to the cadent graph onboarding a directpass dataset the process for onboarding a directpass dataset is similar to creating a standard file upload or watch folder dataset you must select the correct match identifier to enable the directpass functionality to onboard a directpass dataset, complete the following steps select datasets and click new dataset at name, enter a unique name for your dataset add any relevant tags for categorization, in tags to restrict usage to specific advertisers, at usage restrictions enter advertisers that can use the dataset at ingest source, select file upload or watch folder from the match identifier drop down, select the multi key (device+ip) option to designates the dataset for the directpass workflow this option ensures that the raw ip addresses and device ids in your file are made available for the directpass deployment workflow configure the remaining settings for your file upload or watch folder dataset as you normally would (for example, pipe field separators, commas for segment separators) directpass file format requirements your data file must contain the specific columns defined here the platform will fail the onboarding process if these required fields are not included required file columns \co\ \\ \\ id the external raw e identifier this can be an ip address like 192 168 1 1 or device id like aebe52e7 03ee 455a b 3c4 e57283966239 id type the general category for the identifier ip, mobile device, ctv id subtype the specific type of the identifier the value for this column depends on the id type for mobile device android phone ios phone android tablet ios tablet other for ctv roku apple tv fire tv chromecast xbox sony samsung other, for ip v4 v6 taxonomy file requirements if your device file contains segments, ensure the taxonomy contains a mapping of the segment ids in the onboarded data file the filename should clearly identify the file as a taxonomy and not a data file we recommend a format that contains the name of the audience, the taxonomy name, and the date the file was created for example, audience name taxonomy name date csv has the minimum requirements for a taxonomy file, which consists of three columns \segment id\ \segment name\ \cpm\ segment 1 frequent paper towel users $1 75 segment 2 infrequent paper towel users $1 25 in cases of a nested hierarchy, the following is an example that includes the minimum four accepted columns se \gment id\ \parent id\ \segment name\ \cpm\ category name 1 root goods subcategory name 1 category name 1 paper towels subcategory 1 segment 1 subcategory name 1 frequent paper towel users $1 75 subcategory 2 segment 2 subcategory name 1 infrequent paper towel users $1 25 taxonomy file formatting best practices the following practices are required for the taxonomy file any segment ids are the same as the comma delimited ids from your data file only alphanumeric or underscore characters are supported in the file do not use the following characters !, @, #, $, %, &, , ^ the length of each field should not exceed 1024 characters if you have special characters in your segment name, enclose the name in double quotes using directpass datasets on the new audience page identifying directpass datasets after your file is successfully onboarded, the dataset appears in the my datasets tab on the new audience page you can identify it by the directpass tag displayed with the dataset name the match key column on the dataset list page shows device+ip audience building rules you can combine a directpass dataset with other directpass datasets if you build an audience that combines a directpass dataset with any other segment type (for example, standard household matched segments), the entire audience reverts to the standard deployment process it will only deploy using cadent matched household devices, and the directpass option will not be available when you save an audience containing only directpass eligible datasets, it automatically receives a directpass tag or icon next to the audience’s name for easy identification deploying a directpass audience the final step is to deploy your directpass audience to a destination the combination of the destination and audience must both be eligible for directpass or the directpass control will not be selectable on the deployment screen, select your desired destination and the directpass tagged audience you created select the directpass toggle example directpass dataset the following is an example of the minimum requirements for a directpass dataset file it must include an id type and id subtype \\ \\ \\ 9196549f f411 536d b818 a mobile device android phone 2600 1700 8091\ dc0 ip v4 2601 647 8500\ dc20 ctv roku note if the required fields are not included, the onboarding fails and you receive the following message match key formatting requirements were not met