.png)
LinkedIn Marketing Solutions Integration Guide
Connect LinkedIn advertising, analytics, conversion, and lead-generation data with enterprise systems through versioned REST APIs, OAuth 2.0, and selected lead notifications.
LinkedIn Marketing Solutions integration options at a glance
LinkedIn Marketing Solutions is primarily integrated through versioned REST APIs secured with OAuth 2.0. These APIs support advertising accounts, campaign groups, campaigns, creatives, Ad Analytics, conversions, and selected Lead Gen Forms and Leads workflows. Reporting integrations commonly use scheduled retrieval with pagination, date windows, filters, and persisted synchronization watermarks. Selected lead-generation scenarios also support webhook-style notifications or notification subscriptions, while bulk and batch operations are available for some advertising resources. Creative workflows may use product-specific image or video asset APIs. Martini can orchestrate these calls, transform responses, expose normalized APIs, and route data to databases, CRMs, warehouses, or marketing platforms.
| Integration point | Supported by LinkedIn Marketing Solutions? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | Manage or retrieve Ad Accounts, Campaign Groups, Campaigns, Creatives, Conversions, Lead Gen resources, and advertising data through versioned APIs. | Martini can consume the LinkedIn Marketing REST APIs, map responses, apply business rules, and expose normalized APIs for downstream systems. |
| OAuth 2.0 | Yes | Authenticate applications with delegated access, approved product access, and scopes such as r_ads, rw_ads, and r_ads_reporting. | Martini can store client credentials, tokens, scopes, and version settings in protected secrets or environment configuration and use them in API workflows. |
| Reporting and analytics APIs | Yes | Retrieve Ad Analytics by account, campaign, creative, date range, dimensions, pivots, attribution settings, and measures such as impressions, clicks, spend, and conversions. | Martini can schedule incremental reporting requests, paginate results, preserve query parameters, transform data, and write it to databases or data platforms. |
| Webhooks / outbound callbacks | Limited | Selected Lead Gen Forms and lead synchronization scenarios support webhook-style notifications or notification subscriptions; there is no universal campaign event stream. | Martini can expose an API endpoint to receive supported lead notifications, validate payloads, deduplicate submissions, and invoke downstream workflows. |
| Bulk / async / batch APIs | Limited | Selected advertising resources support batch or bulk-oriented operations, with coverage and limits varying by endpoint and API version. | Martini can orchestrate eligible batch requests while retaining ordinary REST collection operations for resources without bulk coverage. |
| File / attachment APIs | Limited | Some creative workflows involve product-specific image, video, or other creative asset registration and upload operations. | Martini can coordinate asset-related API calls and subsequent Creative operations, but should not treat LinkedIn asset handling as a general file-transfer interface. |
| Database / analytics access | Limited | LinkedIn exposes advertising analytics through APIs rather than a customer-accessible database connection. | Martini can retrieve API data and persist normalized results in a supported database or warehouse for reporting and downstream use. |
| Pagination and incremental retrieval | Yes | Collection endpoints commonly use paging, while reporting integrations can use date ranges, filters, and persisted watermarks. | Martini workflows can continue across pages, limit concurrency, maintain checkpoints, and reprocess controlled rolling windows for late-arriving analytics. |
How LinkedIn Marketing Solutions exposes data and business events
LinkedIn Marketing REST APIs
LinkedIn Marketing Solutions uses versioned REST APIs as its primary integration surface for Ad Accounts, Campaign Groups, Campaigns, Creatives, Ad Analytics, Conversions, and selected lead-generation resources. Operations and fields depend on API version, product access, scopes, and Ad Account permissions.
Martini implementation pattern
Martini implementation pattern: a workflow authenticates with OAuth 2.0, calls the required LinkedIn endpoint, handles pagination and response status, maps the vendor model to a canonical structure, applies business rules, and writes or forwards the result to a target system.
Implementation sequence
LinkedIn Ad Analytics API
The Ad Analytics API provides campaign performance data using dimensions, pivots, measures, time ranges, and attribution settings. Results may change as attribution and late-arriving events are updated, so reporting integrations should preserve query context and support controlled reprocessing.
Martini implementation pattern
Martini implementation pattern: a scheduler invokes a parameterized reporting workflow, which retrieves a bounded date window, paginates through responses, normalizes measures and dimensions, loads a database or warehouse, and records the query parameters and watermark.
Implementation sequence
LinkedIn Lead Gen notifications
Selected Lead Gen Forms and lead synchronization scenarios support webhook-style notifications or notification subscriptions. This capability is limited to supported lead-generation products and is not a universal event mechanism for campaigns, creatives, or analytics.
Martini implementation pattern
Martini implementation pattern: Martini exposes an API endpoint for supported notifications, validates the request and source identifiers, retrieves current lead details when required by the supported flow, deduplicates the submission, and routes the normalized lead to a CRM or marketing platform.
Implementation sequence
LinkedIn batch and bulk operations
Selected advertising resources provide batch or bulk-oriented operations, but coverage and limits vary by endpoint and API version. Standard REST collection operations remain necessary for resources without an applicable batch capability.
Martini implementation pattern
Martini implementation pattern: Martini partitions eligible changes into bounded batches, invokes the supported operation, tracks each item or response result, retries transient failures with backoff, and falls back to ordinary REST operations where batch coverage does not apply.
Implementation sequence
Common LinkedIn Marketing Solutions integration patterns
Pattern 1: Sync LinkedIn leads to a CRM
When to use this pattern
Use this pattern when Lead Gen Form submissions must reach Salesforce, HubSpot, Marketo Engage, or Microsoft Dynamics 365 for qualification and follow-up. Availability depends on LinkedIn Lead Sync product access, permissions, and the configured notification or polling flow.
Integration direction
Example Mapping
| LinkedIn Marketing Solutions Field | Canonical Field | Target Field |
|---|---|---|
| leadId | sourceLeadId | LinkedIn Lead ID |
| firstName | firstName | FirstName |
| lastName | lastName | LastName |
| emailAddress |
Martini implementation pattern
Martini receives a supported notification or retrieves leads on a schedule, validates consent and required fields, checks the source lead identifier for prior processing, enriches the canonical lead model with campaign context, and performs an idempotent CRM create or update. Transient API failures are retried, while invalid payloads are routed for review.
Martini capabilities used
- workflows
- API consumption
- API exposure
- data mapping
- business rules
- error handling
Pattern 2: Load LinkedIn campaign analytics into a warehouse
When to use this pattern
Use this pattern to centralize Ad Analytics for cross-channel reporting, attribution, finance analysis, or Tableau dashboards. It is suitable for recurring account-level or campaign-level reporting with rolling backfills.
Integration direction
Example Mapping
| LinkedIn Marketing Solutions Field | Canonical Field | Target Field |
|---|---|---|
| campaignId | campaignId | CAMPAIGN_ID |
| impressions | impressions | IMPRESSIONS |
| clicks | clicks | CLICKS |
| costInLocalCurrency | spend | SPEND_LOCAL_CURRENCY |
Martini implementation pattern
A scheduled Martini workflow requests a bounded date range and reporting dimensions, paginates through Ad Analytics results, preserves the query parameters and API version, transforms measures into a warehouse model, and loads the data using a persisted watermark. A rolling recent window is reprocessed to accommodate attribution updates and late-arriving results.
Martini capabilities used
- scheduled workflows
- API consumption
- pagination and checkpoints
- data mapping
- database or warehouse integration
- error handling
Pattern 3: Synchronize campaigns and creatives with marketing operations
When to use this pattern
Use this pattern when a marketing operations platform or internal database needs a normalized view of Ad Accounts, Campaign Groups, Campaigns, and Creatives, including changed, paused, or newly created resources.
Integration direction
Example Mapping
| LinkedIn Marketing Solutions Field | Canonical Field | Target Field |
|---|---|---|
| account | adAccountId | LinkedIn Ad Account ID |
| campaignGroup | campaignGroupId | Campaign Group ID |
| campaign | campaignId | Campaign ID |
| status | deliveryStatus | Campaign Status |
Martini implementation pattern
Martini periodically retrieves resource collections, follows pagination, compares source identifiers and relevant fields with the prior checkpoint, applies status and ownership rules, and writes normalized objects to the target system. Version-specific fields are mapped selectively so schema additions do not break the full workflow.
Martini capabilities used
- scheduled workflows
- API consumption
- data mapping
- business rules
- state and checkpoint management
- retry handling
Pattern 4: Synchronize conversions and attribution outcomes
When to use this pattern
Use this pattern when internal conversion events must be aligned with LinkedIn Conversions resources or when advertising outcomes need to be reconciled with CRM and revenue data.
Integration direction
Example Mapping
| LinkedIn Marketing Solutions Field | Canonical Field | Target Field |
|---|---|---|
| opportunityId | sourceOpportunityId | External Conversion Reference |
| conversionType | conversionDefinition | Conversion Definition |
| convertedAt | conversionTimestamp | Conversion Time |
| revenueAmount | conversionValue | Conversion Value |
Martini implementation pattern
Martini receives or retrieves eligible internal conversion events, validates required identifiers and timestamps, maps them to the supported LinkedIn conversion model, and submits or reconciles the result through the appropriate API. The workflow stores request outcomes, prevents duplicate submissions, and retries transient failures without replaying confirmed successes.
Martini capabilities used
- API exposure
- API consumption
- data mapping
- validation
- business rules
- idempotency
- error handling
Applications commonly integrated with LinkedIn Marketing Solutions
LinkedIn Marketing Solutions data is commonly combined with CRM, marketing automation, analytics, advertising, and data-platform applications. Martini can coordinate these flows while keeping LinkedIn access, transformation rules, identifiers, and operational handling in reusable workflows.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Salesforce | Send LinkedIn Lead Gen Form submissions to Salesforce Leads or Contacts and associate advertising attribution with CRM opportunities. | LinkedIn Marketing Solutions → Martini → Salesforce | Receive or retrieve eligible LinkedIn leads, validate consent and required fields, deduplicate by the LinkedIn lead or submission identifier, map the payload to Salesforce Leads or Contacts, and record the source campaign and processing outcome. |
| HubSpot | Create or update HubSpot contacts from LinkedIn leads and combine campaign performance with marketing automation activity. | LinkedIn Marketing Solutions → Martini → HubSpot | Use a webhook-style lead notification or scheduled Lead Sync retrieval, normalize contact and campaign fields, apply upsert rules, and send reporting data through a separate workflow where required. |
| Marketo Engage | Route LinkedIn-generated leads into Marketo for qualification, nurturing, scoring, and campaign attribution. | LinkedIn Marketing Solutions → Martini → Marketo Engage | Ingest qualified LinkedIn leads, map form responses and campaign identifiers to Marketo fields, apply validation and consent rules, and retry transient delivery failures without duplicating submissions. |
| Microsoft Dynamics 365 | Deliver LinkedIn leads to Dynamics 365 Sales and align advertising responses with account, contact, and opportunity processes. | LinkedIn Marketing Solutions → Martini → Microsoft Dynamics 365 | Transform LinkedIn lead data into Dynamics 365 entities, resolve existing contacts using stable identifiers, route invalid records for review, and persist an audit result for each submission. |
| Google Ads | Consolidate LinkedIn and Google Ads performance for cross-channel reporting, attribution, and budget analysis. | LinkedIn Marketing Solutions → Martini → Google Ads | Retrieve LinkedIn Ad Analytics data on a schedule, align its dimensions and measures with a common paid-media model, and combine it with Google Ads data in a reporting store rather than assuming a direct native link. |
| Snowflake | Centralize campaign, creative, conversion, and analytics data for historical reporting and attribution analysis. | LinkedIn Marketing Solutions → Martini → Snowflake | Use incremental REST API extraction with date ranges and watermarks, preserve query parameters and source identifiers, transform results into warehouse-ready structures, and load them with controlled backfills. |
| Tableau | Present LinkedIn campaign performance alongside CRM, web, and revenue data through a curated analytical source. | LinkedIn Marketing Solutions → Martini → Tableau | Load normalized analytics data into a database or warehouse, apply consistent campaign and date dimensions, and expose the curated dataset for Tableau rather than connecting Tableau directly to each LinkedIn endpoint. |
| ServiceNow | Route marketing-generated requests or qualified leads into ServiceNow workflows where marketing operations or service processes are managed there. | LinkedIn Marketing Solutions → Martini → ServiceNow | Transform approved LinkedIn lead or operational payloads into ServiceNow records, apply business-specific routing and priority rules, and use retry and audit handling for downstream API failures. |
How to build a LinkedIn Marketing Solutions integration in Martini
Objective
Establish OAuth 2.0 access to LinkedIn Marketing Solutions using the application, product access, Ad Account permissions, scopes, and API version required for the integration.
Instructions in Martini
- Register or configure the LinkedIn application and approved Marketing API products.
- Store client credentials, tokens, scopes, and version settings in Martini secrets or protected environment configuration.
- Configure the REST API workflow without logging authorization headers or token values.
Objective
Select a scheduled workflow for reporting and synchronization or expose a Martini API for supported Lead Gen notifications.
Instructions in Martini
- Use a scheduler for campaign, creative, conversion, and analytics retrieval.
- Use an API trigger for supported LinkedIn lead notification scenarios.
- Define account, object, date-range, and watermark parameters.
Objective
Call the appropriate LinkedIn REST endpoint and handle collection pagination, reporting partitions, and product-specific resource behavior.
Instructions in Martini
- Retrieve the current Ad Account, Campaign Group, Campaign, Creative, Conversion, Lead, or analytics data.
- Continue through pages until the collection is complete.
- Use bounded date windows and incremental filters instead of repeatedly downloading full histories.
Objective
Coordinate API calls, multi-step creative or lead processing, conditional routes, and downstream delivery in a maintainable Martini workflow.
Instructions in Martini
- Separate authentication, retrieval, transformation, validation, and target writes into clear workflow stages.
- Use conditional logic for product access, object status, and response outcomes.
- Persist synchronization checkpoints and source identifiers.
Objective
Convert LinkedIn resource and reporting structures into canonical models suitable for CRMs, warehouses, marketing platforms, or internal APIs.
Instructions in Martini
- Map only required fields and preserve source identifiers.
- Normalize dates, measures, campaign relationships, and attribution context.
- Retain query parameters and relevant unknown fields where future schema changes must be investigated.
Objective
Enforce consent, account access, status, deduplication, data-quality, and reporting-window rules before writing or updating target data.
Instructions in Martini
- Validate required lead, campaign, conversion, and analytics fields.
- Use stable LinkedIn identifiers for idempotent processing.
- Route invalid records and unsupported operations to an operational exception path.
Common LinkedIn Marketing Solutions data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Ad Accounts | Identify the advertising account that owns campaigns, creatives, reporting activity, and account-level configuration. | CRM, marketing platform, database, data warehouse | Martini retrieves account data through OAuth-authorized API calls, normalizes account identifiers and permissions, and stores checkpoints or mappings. |
| Campaign Groups | Organize related campaigns and control higher-level campaign status. | CRM, marketing operations platform, database | Martini synchronizes campaign group attributes, applies status and ownership rules, and links groups to their Ad Accounts. |
| Campaigns | Represent advertising configuration including targeting, budget, bid, objective, schedule, and delivery status. | CRM, finance platform, marketing platform, data warehouse | Martini retrieves or updates supported fields, validates business constraints, maps campaign identifiers, and records API outcomes. |
| Creatives | Represent sponsored content or other advertising creative assets associated with campaigns. | Marketing platform, content workflow, database, warehouse | Martini coordinates creative retrieval and product-specific asset operations, while preserving campaign relationships and handling multi-step failures. |
| Ad Analytics | Provide reporting measures and dimensions such as impressions, clicks, spend, conversions, dates, and attribution results. | Snowflake, Tableau, database, finance platform | Martini runs parameterized, paginated reporting workflows, stores query context, transforms measures, and supports incremental loads and controlled backfills. |
| Conversions | Define conversion tracking and related advertising outcome measurement. | CRM, marketing automation, data warehouse | Martini reads or manages supported conversion resources, maps internal conversion events, applies validation, and records request outcomes. |
Authentication and security considerations
OAuth 2.0 and product access
LinkedIn Marketing Solutions uses OAuth 2.0 delegated authorization. Access depends on the application, approved Marketing API products, OAuth scopes, and the authenticated member's permissions for the relevant Ad Account.
Secrets and sensitive data
Store client credentials, access tokens, refresh behavior, scopes, and API version settings in Martini secrets or protected environment configuration. Do not embed credentials in workflows or log authorization headers.
Lead data protection
Lead Gen Forms and Leads may contain personal information. Apply appropriate retention, access control, encryption, audit logging, and regional data-handling policies when moving lead data to downstream systems.
Operational considerations for LinkedIn Marketing Solutions integrations
Versioning and permissions
Keep the LinkedIn API version configurable because paths, fields, permissions, and product access can change. Test with the exact application, Ad Account, scopes, and approval state used in production.
Pagination and rate limits
Collection responses may be paginated and LinkedIn applies usage limits. Use incremental retrieval, bounded concurrency, backoff, and persisted watermarks rather than repeatedly downloading complete account histories.
Reporting consistency
Ad Analytics results depend on date ranges, granularity, pivots, attribution settings, and measures. Persist query parameters and reprocess a controlled rolling window to accommodate late-arriving or revised attribution data.
Idempotency and schema changes
Use stable LinkedIn identifiers for duplicate prevention and target upserts. Map required fields deliberately, monitor enum and schema changes, and preserve enough source context to troubleshoot failed transformations.
Why use Martini instead of scripts or point-to-point integrations?
Reusable orchestration
Martini separates authentication, retrieval, transformation, business rules, target writes, and error handling into reusable workflows rather than scattering logic across scripts or point-to-point jobs.
Reliable synchronization
Scheduled workflows can manage pagination, incremental watermarks, rolling analytics backfills, bounded concurrency, retries, and idempotent lead processing in a consistent operational model.
Flexible integration surface
Martini can consume LinkedIn REST APIs, receive supported lead notifications through an exposed API, normalize data, and deliver it to CRMs, databases, warehouses, and marketing platforms without requiring a dedicated vendor connector.
Maintainable change management
API versions, scopes, mappings, secrets, and business rules can be configured and maintained independently, helping teams respond to LinkedIn product access changes and schema evolution without rebuilding every integration.
Frequently asked questions
LinkedIn Marketing Solutions is primarily integrated through versioned REST APIs secured with OAuth 2.0. Enterprise workflows can retrieve and manage advertising accounts, campaign groups, campaigns, creatives, conversions, analytics, and selected lead-generation resources. Supported Lead Gen scenarios may also use webhook-style notifications or notification subscriptions; campaign and reporting synchronization generally uses scheduled API retrieval.
Yes. Martini can consume LinkedIn Marketing Solutions REST APIs using OAuth 2.0, retrieve analytics and advertising resources, expose an API for supported lead notifications, transform data, and deliver it to CRMs, databases, warehouses, or marketing platforms. A native Martini connector is not documented in the supplied context.
No. A dedicated LinkedIn Marketing Solutions connector is not required. Martini can use LinkedIn's confirmed native integration mechanisms, including versioned REST APIs, OAuth 2.0, reporting APIs, selected batch operations, and supported Lead Gen notification or synchronization flows.
Lonti does not charge an additional per-connector or per-vendor fee to integrate LinkedIn Marketing Solutions. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from LinkedIn, cloud infrastructure, CRM platforms, data warehouses, or other third-party services based on their subscriptions, usage, and deployment models.
Use LinkedIn's versioned REST Marketing APIs and OAuth 2.0. Common read access includes r_ads and reporting access commonly uses r_ads_reporting; write operations may require rw_ads. Lead-generation, organization, and other product operations can require additional scopes, product approval, and Ad Account permissions.
Only selected Lead Gen Forms and lead synchronization scenarios support webhook-style notifications or notification subscriptions. LinkedIn should not be treated as providing a universal webhook stream for campaign, creative, delivery, or analytics changes; those areas generally require scheduled REST API polling.
Martini can use scheduled workflows, date ranges, filters, pagination, and persisted watermarks to retrieve data incrementally. It maps LinkedIn objects and reporting measures into canonical models, applies validation and business rules, and writes results to target APIs or databases. Analytics workflows should preserve query parameters and support rolling backfills because attribution results can change.
Martini workflows can use bounded concurrency, retry policies, backoff, pagination checkpoints, and operational exception paths for transient and permanent failures. Lead ingestion should persist a stable LinkedIn lead or submission identifier and use idempotent upserts or duplicate checks before creating downstream records. OAuth, product-access, account-permission, and schema errors should be monitored separately from throttling failures.
Related Martini documentation
Workflows
Data
Connect LinkedIn Marketing Solutions with Martini
Use Martini to build OAuth-secured LinkedIn Marketing Solutions workflows for campaign synchronization, analytics ingestion, conversion processing, and supported lead-generation notifications.