Re: Linkedin mapping visibility

Hasnain

A client has a handful of different countries using the same Social Media Launchpoint integration. For Linkedin specifically, field mapping linkedin custom fields to Marketo fields isn't a straight forward process.

Fields have to be mapped via the Marketo UI (Admin>>launchpoints>>linkedin lead ads service...) but as you can see from the image below, the marketing consent fields are impossible to differentiate across different countries, and you cannot change the name of the field in Linkedin.

Is there a way to effectively identify a Marketing Consent field Linkedin from one workspace and Marketing Consent field in another workspace in Linkedin when end users of both forms see the same legal verbiage?

SaurabhGoyal_GN

Hi @Hasnain,

To effectively differentiate between Marketing Consent fields across different workspaces in LinkedIn Lead Gen Ads, you can consider using custom field aliases in Marketo. While LinkedIn does not allow you to rename fields, you can create custom field aliases in Marketo to identify the consent fields separately for each workspace.

In Marketo, create unique field names for each country or workspace, then map these fields appropriately in the "Lead Ads" LaunchPoint integration. This way, even though the legal verbiage is the same across workspaces, you can track and differentiate the consent fields based on the alias used in Marketo for each workspace's respective form.

SanfordWhiteman

To effectively differentiate between Marketing Consent fields across different workspaces in LinkedIn Lead Gen Ads, you can consider using custom field aliases in Marketo. While LinkedIn does not allow you to rename fields, you can create custom field aliases in Marketo to identify the consent fields separately for each workspace.

If I’m understanding @Hasnain’s question correctly, they want to distinguish the different fields on the LinkedIn side when configuring the connector, since they have the same display name in the dropdown.

Having multiple Marketo fields doesn’t solve that because the problem is in picking the field on the left-hand side.