6 - Integrate DAD with LinkedIn Ads

These steps will enable you to configure the Daily Aggregate Database with reporting data from LinkedIn Ads. Before starting the configuration below, make sure you have reviewed all Installation & Configuration: Considerations. Also, make sure you are on version 1.45.2 or later of the Response Management package.

Note: Although LinkedIn Campaign Name is one of the fields populated by this integration, it will only be accurate if all of your LinkedIn campaigns have unique combinations of UTM Source, UTM Medium, and UTM Campaign. As described here, Digital Source Tracker's Daily Aggregate Database segments by UTM Source, UTM Medium, and UTM Campaign.

Step 1: Setup Remote Site Settings

In Salesforce, go to Setup → Remote Site Settings and make sure the “LinkedIn” remote site has the Active box checked. If it's not checked, edit the record to check it and save.

Step 2: Setup Custom OAuth Authentication

In order to authenticate with LinkedIn and use a named credential, we will need to set up the custom OAuth record in Salesforce.

1. Navigate to the custom oAuth Configuration page by typing "/apex/fcsc__FCO_VFConfigAuth” after the domain name url in Salesforce

2. Copy the “Redirect URL” at the bottom. (This URL will be added as a valid redirect URL in the LinkedIn Developer App)

** Below steps (3 & 4) needs to be done by Full Circle CSM

3. Navigate to https://www.linkedin.com/developers/apps/204678954 (Or from https://developer.linkedin.com go to My Apps → “Digital Source Tracker”) Provider Type: LinkedIn

4. Go to the “Auth” tab, and under 'OAuth 2.0 settings” the redirect URL copied in Step 2 should be added to the list of “Authorized redirect URLs for your app”

5. Navigate back to the custom OAuth Configuration Page “FCO_VFConfigAuth” in Salesforce and go to the “LinkedIn” tab.

** The step below should be done by the customer with Account Manager role in LinkedIn, who has access to view ad Account Data for LinkedIn Campaigns

6. Click the button “Start LinkedIn Authentication Flow”. Clicking the button will redirect to a LinkedIn login page, where the customer will enter their LinkedIn Credentials.

7. After signing in, you will be prompted with the following from LinkedIn, and will need to click “Allow”.

If everything went well, you should be redirected back to the custom OAuth page “FCO_VFConfigAuth” in Salesforce with the message “Authentication Complete”.

Step 3: Verify Named Credential

Navigate to Setup | Administer | Security Controls | Named Credentials.

The default Named Credential record that was shipped in the managed package is named "FCLIN_LinkedIn_Credential". If it is not there, you would need to create a new Named Credential record with following values. (* If it exists but has other values set, you will need to clear everything and set the values as below)

Name: “FCLIN_LinkedIn_Credential”
URL: https://api.linkedin.com/rest
Identity Type: Named Principal
Authentication Protocol: No Authentication
Generate Authorization Header: true / checked

Step 4: Configure FCI LinkedIn Integration

For the Daily Aggregate Database to start pulling in data for LinkedIn, we need to perform some configuration on the DST Configuration page, under the “Ad Platform Configuration” tab.

1. Navigate to Digital Source Tracker Configuration (Full Circle Configuration tab -> "Configure" under Digital Source Tracker).
2. Go to "Ad Platform Configuration tab."
3. Select "Yes" to "Would you like to Enable LinkedIn Ad Platform Integration.
4. If you are on version 1.18.2 or earlier of the Digital Source Tracker package, enter the LinkedIn API Version to use (202403). Starting with version 1.18.3 of the Digital Source Tracker package, this field is no longer configurable and the LinkedIn API Version is automatically set by the package.
5. Select one or more LinkedIn Ad Accounts to pull in data for by clicking the "Select Ad Accounts" button, and checking the Ad Accounts you wish to include.
6. Click "Save Account Selection" and click "Save" at top of page to save your settings.

**Note: Make sure the Named Credential is set up and the OAuth Authentication has been completed before fully enabling the integration