Connect DataAnalytics & Marketing
LinkedIn Ads
LinkedIn Ads is in Preview in the connection wizard: it is built on LinkedIn Ads’s documented API and has not yet been proven against a live account, so check the imported tables before relying on them. Sign in with your own LinkedIn app (Advertising API product, Development tier) — it reads every ad account you administer.
-
In DataSquares, open Data Sources and choose Connect Source. The Connect a data source page opens.
-
Pick LinkedIn Ads on that page (search or browse by category).
-
Fill in the connection details below, then test the connection and save.
Connection details
Section titled “Connection details”| Field | What to enter |
|---|---|
| Ad account ID | Campaign Manager → the account’s number (in the account list or the address bar). e.g. 512345678 |
| Client ID | Your app at linkedin.com/developers → Auth. The app needs the Advertising API product. |
| Client secret | The same app’s Primary Client Secret. Add DataSquares’ redirect URL under Authorized redirect URLs. Stored encrypted and never shown again. |
Test Connection reads one page of records with these values; nothing is saved until you import.
Signing in
Section titled “Signing in”Instead of pasting a key, choose Sign in with LinkedIn in the form: you approve access on LinkedIn Ads’s own page and come back to the wizard signed in, then pick the tables. DataSquares keeps the sign-in encrypted and renews it before every refresh; if LinkedIn Ads stops accepting it, the refresh says so — sign in again.
The sign-in uses an OAuth client you create in LinkedIn Ads (a confidential one). Enter
its identifier and secret in the form, and allow the redirect URL the form shows —
on DataSquares Cloud that is https://api.datasquares.ai/api/oauth/callback.
Tables
Section titled “Tables”Pick the tables to import — each one becomes a table in the source:
| Table | What it holds |
|---|---|
campaign_groups |
Campaign groups |
campaigns |
Campaigns |
campaign_analytics_daily |
Campaign results by day (12 months) — re-read in full on every refresh |
Each analytics row has its date, the campaign’s URN in pivot and its id in
pivot_id — the id to join to campaigns.
Every table is read through all of its pages, nested fields become parent.child
columns, and the whole set is imported at once: the import’s row and size limits
count the picked tables together, and if they pass one, nothing is imported and
the message says which table and which limit. Refresh the source on a schedule,
or by hand, to re-read every table; a table that comes back empty is refused
rather than emptied unless you allow it. Nothing is ever written to LinkedIn Ads.
The requests follow LinkedIn Ads’s API reference.
Creating the LinkedIn app
Section titled “Creating the LinkedIn app”LinkedIn Ads signs in through an app you own, so the access stays in your company’s hands.
-
At developer.linkedin.com, create an app linked to your company’s LinkedIn Page and request the Advertising API product.
-
On the app’s Auth tab, add the redirect URL the form shows — on DataSquares Cloud,
https://api.datasquares.ai/api/oauth/callback. Copy the Client ID and Primary Client Secret into the form. -
Ad account ID is the number in Campaign Manager’s address (
…/campaignmanager/accounts/<id>/…). -
Choose Sign in with LinkedIn. The person signing in needs a role on the ad account; the access is read-only (
r_ads,r_ads_reporting).
Related
Section titled “Related”- Connector catalog — everything DataSquares connects to.
- Quickstart — from connection to shared dashboard.