Connection details
Create the source through Connections → New connection, select the appropriate credential type offered by the form, and save. Keep account identifiers in connection settings and secrets in the credential form.
Credentials
Permissions
LinkedIn: the authorisation flow requestsr_ads and r_ads_reporting. The authorised member also needs access to the intended advertising account. The account ID in the connection selects the reporting account; it does not replace LinkedIn’s access controls.
Business Central: the connector requests an application token using https://api.businesscentral.dynamics.com/.default. An administrator must configure the Entra application’s permissions and its access inside Business Central. The selected tenant and environment must match that configuration. The token scope uses the permissions already granted to the app; it is not a promise of read-only access.
Other providers: confirm API availability, credential permissions, and reporting-account access with the provider administrator. A valid API credential may cover more data or operations than the reporting import uses. Dawn’s account and date filters are not credential restrictions.
Build the first import
Add the connection to a conversation and describe the exact reporting output:Before scheduling
Choose a refresh window that accounts for updates to recent periods. Decide how repeated runs replace or reconcile earlier records. Confirm that expired credentials and provider rate limits produce visible failures rather than unnoticed gaps.Troubleshooting
- Unauthorised: check the selected credential and whether the provider has revoked or expired it.
- Account not accessible: verify the credential’s access to the account ID, marketer ID, company, or environment.
- Totals differ: compare date boundaries, timezone, currency, reporting level, and archived records.
- No rows: test a known period with activity and inspect the selected entity or reporting level.