How to connect LinkedIn to Roivenue, what the default setup downloads, and how the figures are put together.
LinkedIn Ads. The Roivenue connector downloads daily impressions, clicks, cost and website conversions for each campaign.
Setting up the connector
Add a LinkedIn connector in Roivenue and choose Connect to LinkedIn. Roivenue sends you to LinkedIn to sign in and approve access. There are no keys to copy.
Setup options
AdCampaign REGEX filter
everything
Limits the connector to campaigns matching a pattern.
Web source and Web medium
blank
The UTM source and medium that LinkedIn traffic should be recognised as.
What the default setup downloads
Two jobs. One brings impressions, clicks, cost and conversions per campaign and day, and a second downloads the feed behind synthetic impressions.
Where the values land
campaign.name
adCampaign
impressions
impressions
clicks
clicks
costInLocalCurrency
cost
externalWebsiteConversions
conversions
conversionValueInLocalCurrency
conversionValue
Conversions are LinkedIn's external website conversions, meaning actions that happened on your site. Lead gen form submissions, which never leave LinkedIn, are not included. If you run lead gen campaigns, expect the conversion count here to be lower than LinkedIn Campaign Manager shows.
Cost arrives in the account's local currency.
The jobs reprocess the last three days on every run.
Available columns
The table above is what the recommended template downloads. Every column this connector can bring back is listed on LinkedIn - Supported Columns.
Adding one means editing the connector in the Advanced Editor, which stops that connector receiving template updates.
Synthetic impressions
Alongside the daily figures, this connector downloads a conversion feed that Roivenue uses to build synthetic impressions.
Ad platforms report conversions that Roivenue never saw as a web session, because of ad blockers, cross-device journeys or conversions uploaded from a CRM. Left alone those orders look like they came from nowhere, and paid media gets undercounted. The synthetic impression stands in for the missing visit so path analysis and attribution see a complete journey.
There is nothing to configure. It comes with the connector, and it is why the setup creates more than one job.
How far back the data goes
The connector will request up to three years of history. How much arrives depends on what the platform holds for the account.
Troubleshooting
Was this helpful?