Docs: add LinkedIn Ads integration connection flow (369855)

[cursor]

JIRA

• https://vendasta.jira.com/rest/api/2/issue/369855
• Issue key: MRNA-1991

Change classification

• UI / UX change (integration setup surfaces and connection workflow)
• Configuration / system behavior (connection and settings flow)

Summary of documentation updates

• Updated existing page: docusaurus/docs/business-app/administration/business-connections-integrations.mdx
• Added a new subsection: How to Connect LinkedIn Ads
• Documented the end-to-end flow in Business App Connections:
  • Locate LinkedIn Ads integration card in Browse
  • Open integration marketing page
  • Start Connect/Add Connection flow
  • Complete auth/pre-connect steps
  • Verify connected state via Manage tab connection card
  • Open Connection Settings for configuration

Existing docs updated or new docs created

• Updated existing docs only
• No new pages created

Placement reasoning

• The existing Business Connections & Third-Party Integrations page already documents integration card, marketing page, connect flow, manage tab, and connection settings patterns.
• Adding LinkedIn Ads there keeps the content co-located with related workflows and avoids duplicating integration setup guidance.

Acceptance criteria coverage

From Jira AC/description:

1. Integration card for LinkedIn Ads → Covered in step 1 (locate LinkedIn Ads integration card in Browse)
2. Marketing page creation/use → Covered in step 1 and step 2 (open marketing page and start connection)
3. Config page → Covered in step 4 (open Connection Settings and manage configuration)
4. Connection card → Covered in step 4 (verify LinkedIn Ads connection card in Manage)

Visual inputs (Figma/images)

• No Figma links or attachments were present in the webhook payload.
• Update based on available Jira text and acceptance criteria only.

Skills used

• sprint-review skill (used for repo-compliant doc update workflow, evergreen wording, and conservative scope handling)

Assumptions / limitations

• Linked implementation PR details were not discoverable from accessible GitHub searches in this automation context, so related code author tagging could not be confidently derived.
• The linked Google Doc in Jira was not accessed from this environment.

Validation

• Ran npm run build in docusaurus/ successfully.
• Build shows pre-existing repository broken link/anchor warnings unrelated to this change.

Review tags

@ahnikakuse
@haleyserrano
@maryam6samadi