A brief summary of your issue.

Category the issue falls in.

The environment of your Indicative instance.

The Organization name of your instance.

The method used to login.

Your organization’s plan type.

The special permissions in the contract.

The name of your project.

The type of data.

The keys of the events or properties.

The type of data from the CSV export.

The URL of the query.

The tool and logic Indicative is being compared against. Include the SQL and/or a screenshot if applicable.

The Data Source Name can be found in Settings -> Data Sources.

Browser

Indicative dedupes data so deletions are only required if the event data is changing.

The starting date for the data replay and/or data deletion.

The ending date for the data replay and/or data deletion.

Please enter the details of your issue or question and our support staff will be right with you.

The Issue's Severity, please review the guidelines alongside each SEV value in the dropdown.

Add file or drop files here

    mParticle Support Form

    Tell us what is happening and our support team will route the request.

    Click here for classic support portal

    1. Account context

    Enter the customer context manually. Email address, pod, organization, account, and workspace are required.

    Manual entry

    2. Where is the issue?

    Adaptive path
    Other / I am not sure may increase time to resolve. Support can still help, but choosing an unsure path usually means we need to ask more follow-up questions before we can solve it. Filling in the closest IDs, timestamps, and screenshots now helps reduce back-and-forth.

    4. Additional context

    Optional notes that did not fit the targeted questions.

    Please don't attach PII

    Optional
    Zendesk attachment control will appear here on the support site.
    Zendesk limit: 50 MB per file. Combined attachments must be 50 MB or less.

    5. Severity

    Required impact level using Support severity definitions.

    Required
    Ready to send? Missing details are allowed, but the form will show what support is likely to ask next.

    A few details may speed this up

      Ticket submitted

      Our TSE team has received your request and will review it shortly.

      Are you sure this is SEV1?

      SEV1 is for critical outage situations where mParticle data collection services and data reporting services are completely down, there is critical business impact, and no workaround is available.

      If the service is degraded, delayed, partially working, or this is a question, choose SEV2-SEV4 so Support has the right urgency and context.