Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Please sign in to leave a comment.

Comments

2 comments

Date Votes
  • Official comment
    Syead Mujtaba Imam Rizwi Fivetranner

    Hi Jing,

    Thank you for the suggestion. We have added this to our active backlog and are reviewing what it would take to support ingestion of the OmniSubscription data model. Could you share more about which specific fields or subscription states matter most for your reporting? We will keep you updated on this thread as we make progress.

    Best,
    Syead Mujtaba Imam Rizwi

  • Jing Pang User

    Hi Syead,

    Thank you for the update. Rather than just a few specific fields, our primary need is to get the core Omni subscription data flowing in its entirety.

    Our backend has already started testing the Omnisubscription feature for our mobile subscriptions. Because our mobile subscriptions have migrated to the Omni model, we are currently unable to track them through our existing setup. If Fivetran cannot support this ingestion soon, it will lead to significant inconsistencies in our overall subscription data and reporting.

    Getting this data synced is critical for us to maintain accurate tracking for our mobile users. Let me know if you need the exact object/field names from the Chargebee documentation, but essentially we need the standard Omni subscription data to ensure our tracking remains complete.