Open TD Console.
Navigate to Integrations Hub > Catalog
Search for and select LinkedIn. Select Create.
The following dialog opens.
Select Click here to connect to a new account. You are redirected to LinkedIn to loginlog in, if you haven't login yet, or to the consent page to grant access to Treasure Data.
You will be redirected back to TD console. Repeat the first step (Create a new connection) and choose your new OAuth connection.
Select Continue and name your new LinkedIn connection.
Configure Export Results in Your Data Connection
In this step, you create or reuse a query. In the query, you configure the data connection. Sometimes you need to define the column mapping in the query.
Type the connection name in the search box to filter.
Select your connection.
The Export Results dialog opens.
Enter your Ad Account ID.
Select New Integration and select LinkedIn from Type dropdown.
The Create Integration dialog opens.
Select the Catalog link to go to the Catalog page.
Complete the steps described previously in "Create a new connection", including the creation of an OAuth connection.
Enter the required credentials for your new LinkedIn connection.
Ad Account ID (required)
Your Ad Account ID
Contact List (Users) or Account List (Companies)
Segment Name (required)
DMP Segment name
Segment Description (optional)
DMP Segment description
DMP Segment Mode
Add or Remove. If mode = Add and Segment Name does not exist, a DMP with the provided name will be created.
Ignore Invalid Records
Option to ignore invalid rows and to continue importing others. Invalid rows are listed in the job log. If this option is not selected (by default), jobs terminate when an invalid record is encountered and uploaded data is not reverted.
The LinkedIn data connector understands and interprets only the following columns and data types. You must modify alias column names to match with the following specified columns:
Applicable for Contact List (Users)
An input request will be validated and it will fail if the following validation rules are not met:
User's emails, SHA256 hashed emails or SHA512 hashed emails. User's email will be SHA256 hashed before sending to LinkedIn.
|google_aid||string||optional||A plain text string with a maximum length of 32 characters and all in lower case. For example, cdda802e-fb9c-47ad-0794d394c912....|
|apple_idfa||string||optional||A plain text string with a maximum length of 32 characters and all upper case. For example, EA7583CD-A667-48BC-B806-42ECB2B48606....|
|first_name||string||optional||A plain text string with max length 35 characters representing the first name of the contact to match e.g. Mike|
|last_name||string||optional||A plain text string with max length 35 characters representing the last name of the contact to match e.g. Smith|
|company||string||optional||A plain text string with max length 50 characters representing the company name of the contact to match e.g. Microsoft Corporation|
|title||string||optional||A plain text string with max length 50 characters representing the title name of the contact to match e.g. Software Engineer|
|country||string||optional||ISO standardized two letter country code e.g. US|
Applicable for Account List (Companies). At least one of these columns is required.
A string representing the company name of this company.
The company website domain.
The company email domain (sometimes different from the website domain).
Example Queries to Populate LinkedIn Data
The following example query uploads all emails to the existing DMP Segment specified by Segment Name if if DMP Segment Mode is specified as Add. Or a new DMP Segment with the specified name will be created before uploading hashed emails.
SELECT user_email AS email, google_aid, first_name, last_name FROM my_table;
The following example query uploads Account List to specified DMP Segment if DMP Segment Mode is specified as Add
You can use Scheduled Jobs with Result Export to periodically write the output result to a target destination that you specify.