Run campaigns with custom audiences, retargeting, and lookalikes in LinkedIn
Deliver even more relevant ads by combining data from various sources within your data warehouse to build custom audiences for LinkedIn Ads. By keeping your custom audiences updated automatically, you can avoid showing irrelevant ads.
|Sync Type||Description||Supported Sync Modes|
|Audiences||Create new audience to sync users or companies||Upsert|
For more information about sync modes, refer to the sync modes docs.
Go to the Destinations overview page and click the Add destination button. Select LinkedIn Ads and click Continue. You can then authenticate Hightouch to LinkedIn Ads using OAuth.
For the Authentication method, select Log in to LinkedIn Ads and log into your LinkedIn Ads account.
Once successful, you will be redirected back to Hightouch to enter a descriptive name for your destination and complete setup.
Once you've set up your LinkedIn Ads destination and have a model to pull data from, you can set up your sync configuration to begin syncing data. Go to the Syncs overview page and click the Add sync button to begin. Then, select the relevant model and the LinkedIn Ads destination you want to sync to.
To get started, select an ad account to sync your data to, then select which audience object you want to sync data to: Company or User.
Hightouch supports automatically creating a new audience for your sync. You can specify a custom name for this audience, or Hightouch will use the name of the model.
This integration supports Upsert mode. New users will be inserted into the LinkedIn audience. Users that are removed from the model will be removed from the audience.
LinkedIn allows mapping to various user and company identifiers, such as email, IDFA, company domain, etc. LinkedIn requires the email for users to be hashed using SHA256 or SHA512, which we take care of automatically on the backend.
You can enable PII hashing if you want Hightouch to automatically detect, normalize, and hash fields that require it. For example, if you map to a
Email (SHA256) field and the model column with the email data is unhashed, Hightouch hashes the value for you.
By default, Hightouch automatically detects if the following fields require hashing:
- Email (SHA256)
- Email (SHA512)
If you encounter an error or question not listed below and need assistance, don't hesitate to . We're here to help.
You may receive a
400 - type=MISSING_REQUIRED_FIELD because the sync is sending a required field
You can resolve this error by either:
- Removing rows containing
nullvalues from your model's query results
- Replacing any
nullvalues in your model's query results with another value
- Using the advanced mapper to ignore any
Hightouch provides complete visibility into the API calls made during each of your sync runs. We recommend reading our article on debugging tips and tricks to learn more.
Hightouch can alert you of sync issues via Slack, PagerDuty, SMS, or email. For details, please visit our article on alerting.