Skip to content

docs(meta-ads): add doc for meta ads integration - #16

Open
madhukaraman wants to merge 1 commit into
mainfrom
docs/add-docs-for-meta-ad-integration
Open

docs(meta-ads): add doc for meta ads integration#16
madhukaraman wants to merge 1 commit into
mainfrom
docs/add-docs-for-meta-ad-integration

Conversation

@madhukaraman

@madhukaraman madhukaraman commented Aug 4, 2025

Copy link
Copy Markdown
Contributor

Summary by CodeRabbit

  • Documentation
    • Added a comprehensive guide for integrating Meta Ads with the platform, including step-by-step instructions, screenshots, troubleshooting tips, and support contact details.
    • Updated the documentation navigation to include the new Meta Ads integration guide under Ad Network Integration.

@coderabbitai

coderabbitai Bot commented Aug 4, 2025

Copy link
Copy Markdown

Walkthrough

A new documentation page for integrating Meta Ads via Linkrunner was added, detailing setup steps, troubleshooting, and support information. The documentation navigation configuration was also updated to include this new Meta Ads guide under the "Ad Network Integration" section.

Changes

Cohort / File(s) Change Summary
Meta Ads Integration Documentation
ad-networks/meta-ads.mdx
Added a comprehensive guide for integrating Meta Ads with Linkrunner, including setup steps, screenshots, troubleshooting, and support details.
Documentation Navigation Update
docs.json
Updated navigation to include the new Meta Ads documentation under "Ad Network Integration".

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

In docs a new path now appears,
Meta Ads joins with cheers!
Step-by-step, the guide is clear,
Troubleshooting tips are near.
With Linkrunner’s dashboard in view,
Campaign data shines anew—
🐇 Hopping forward, docs in queue!

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch docs/add-docs-for-meta-ad-integration

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
ad-networks/meta-ads.mdx (2)

9-10: Minor grammar issue in the overview sentence.

"track the insights your app campaigns" is missing a preposition. Consider tightening the wording:

-Meta Ads integration with Linkrunner enables you to track the insights your app campaigns.
+Meta Ads integration with Linkrunner enables you to track insights from your app campaigns.

22-45: Give each screenshot a unique, descriptive alt-text for accessibility.

All four images share the same generic alt-text (“Linkrunner Meta Ads Integration Dashboard”). Screen-reader users can’t tell the difference. Provide context-specific descriptions:

-![Linkrunner Meta Ads Integration Dashboard](/images/meta_ads/clicks/Linkrunner_Meta_AD_Account_Integration_Not_Connected.png)
+![Meta Ads settings page before connection](/images/meta_ads/clicks/Linkrunner_Meta_AD_Account_Integration_Not_Connected.png)

...

-![Linkrunner Meta Ads Integration Dashboard](/images/meta_ads/clicks/Meta_Account_Connection.png)
+![Meta authentication success modal](/images/meta_ads/clicks/Meta_Account_Connection.png)

Repeat for the remaining screenshots.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 567afe8 and 250ad3c.

⛔ Files ignored due to path filters (4)
  • images/meta_ads/clicks/Connected_Meta_Accounts.png is excluded by !**/*.png
  • images/meta_ads/clicks/Linkrunner_Meta_AD_Account_Integration_Not_Connected.png is excluded by !**/*.png
  • images/meta_ads/clicks/Meta_Account_Connection.png is excluded by !**/*.png
  • images/meta_ads/clicks/Meta_Account_Import.png is excluded by !**/*.png
📒 Files selected for processing (2)
  • ad-networks/meta-ads.mdx (1 hunks)
  • docs.json (1 hunks)
🔇 Additional comments (2)
docs.json (1)

67-69: Navigation entry looks good – verify slug/file match.

"ad-networks/meta-ads" correctly matches the new file path (ad-networks/meta-ads.mdx). No structural or JSON-formatting issues spotted.

ad-networks/meta-ads.mdx (1)

63-70: Confirm custom MDX components are available site-wide.

<Note> and <Tip> rely on globally registered MDX components. If they aren’t already exported by your docs tooling, this page will fail to render.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant