Skip to content

Conversation

@devwithkn
Copy link

What

How

Add below skan-specific metrics to ads_reports_daily stream (for tiktok_metrics:

  • skan_result
  • skan_cost_per_result
  • skan_conversion
  • skan_cost_per_conversion
  • skan_click_time_conversion
  • skan_click_time_cost_per_conversion
  • skan_click_time_conversion_rate
  • skan_app_install
  • skan_registration
  • skan_complete_tutorial
  • skan_purchase
  • skan_cost_per_purchase
  • skan_purchase_rate
  • skan_total_purchase
  • skan_cost_per_total_purchase
  • skan_total_purchase_value
  • skan_total_repetitive_active_pay_roas

Review guide

User Impact

  • More columns for the users.

Can this PR be safely reverted and rolled back?

  • YES 💚
  • NO ❌

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@github-actions
Copy link
Contributor

github-actions bot commented Nov 4, 2025

👋 Welcome to Airbyte!

Thank you for your contribution from devwithkn/airbyte! We're excited to have you in the Airbyte community.

Helpful Resources

PR Slash Commands

As needed or by request, Airbyte Maintainers can execute the following slash commands on your PR:

  • /format-fix - Fixes most formatting issues.
  • /bump-version - Bumps connector versions.
  • /run-connector-tests - Runs connector tests.
  • /run-cat-tests - Runs CAT tests.
  • /build-connector-images - Builds and publishes a pre-release docker image for the modified connector(s).

If you have any questions, feel free to ask in the PR comments or join our Slack community.

Tips for Working with CI

  1. Pre-Release Checks. Please pay attention to these, as they contain standard checks on the metadata.yaml file, docs requirements, etc. If you need help resolving a pre-release check, please ask a maintainer.
    • Note: If you are creating a new connector, please be sure to replace the default logo.svg file with a suitable icon.
  2. Connector CI Tests. Some failures here may be expected if your tests require credentials. Please review these results to ensure (1) unit tests are passing, if applicable, and (2) integration tests pass to the degree possible and expected.
  3. (Optional.) BYO Connector Credentials for tests in your fork. You can optionally set up your fork with BYO credentials for your connector. This can significantly speed up your review, ensuring your changes are fully tested before the maintainers begin their review.

📝 Edit this welcome message.

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

Projects

Development

Successfully merging this pull request may close these issues.

3 participants