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
    Sisan Kumar Sahu Fivetranner

    Hi There,

    Thank you for submitting your feature request for the Dixa connector.

    We will be starting our analysis to evaluate the feasibility of building and maintaining a high-quality Fivetran connector. As we move forward, we may reach out with additional questions or clarifications to ensure the connector aligns with your requirements and expectations.

    In the meantime, could you briefly share your primary use case for this feature?

    We appreciate your feedback and continued support - it plays a key role in shaping our roadmap.

    Best regards,
    Sahu

  • Data Team User

    Hello Sahu

    To provide context on the business need for this request, exposing external_id from the Dixa End User object into the warehouse schema is essential for standard data modeling and data privacy compliance.

    Specifically, this field supports three standard workflows:

    1. Entity Resolution & Cross-Platform Reporting

      external_id serves as the primary foreign key between communication logs (calls, emails, chats) and core customer records. Relying on mutable attributes like email address or phone number creates join errors and duplicate records in downstream analytics.

    2. Data Retention & Activity Tracking

      Accurate data lifecycle management and privacy compliance (e.g., GDPR) require tracking a customer's true last interaction across all channels. Without a direct link to the primary user identifier, support activity in Dixa cannot be accurately incorporated into retention schedules.

    3. Automated Redaction & Erasure Workflows

      When customer records reach their retention limit or require erasure under data protection regulations, automated downstream workflows need a reliable identifier to locate and programmatically redact or purge corresponding records in Dixa.

    Because external_id is already a standard field in Dixa's API, syncing it downstream would allow any team using Dixa to maintain consistent identity mapping and automate compliance operations.

    Thank you