> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zeotap.com/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQs for Real-Time Audience Creation

## General Questions

<AccordionGroup>
  <Accordion title="What is the difference between Batch Audience and Real-Time Audience?">
    Batch Audience processes data in batches and applies criteria to past and future events, while Real-Time Audience streams data instantly and applies criteria only to future events.
  </Accordion>

  <Accordion title="Can I edit an Audience after activation?">
    Yes, you can edit a Real-Time Audience after activation.
  </Accordion>

  <Accordion title="How does data availability on the end platform depend on data volume and pipeline sequence?">
    The time it takes for data to appear on the destination platform depends on the aggregation of data volume and the processing sequence in the data pipeline.
  </Accordion>
</AccordionGroup>

## Batch Audience vs. Real-Time Audience

<AccordionGroup>
  <Accordion title="Does Real-Time Audience support deleting users?">
    No, user deletion is only available for Batch Audiences when the "Delete customers in this Audience" checkbox is selected.
  </Accordion>

  <Accordion title="Can I check estimated audience size before activation?">
    Yes, but only for Batch Audience creation. Real-Time Audience does not support checking estimates.
  </Accordion>

  <Accordion title="Can I enable membership for my Audience?">
    Membership is available for Batch Audiences but not for Real-Time Audiences.
  </Accordion>

  <Accordion title="Can I switch an Audience from Batch to Real-Time after creation?">
    No, once an Audience is created as Batch or Real-Time, it cannot be switched to the other type. You must create a new Audience.
  </Accordion>
</AccordionGroup>

## Journeys & Workflow Management

<AccordionGroup>
  <Accordion title="What is the purpose of Journeys?">
    Journeys help orchestrate workflows by setting entry conditions, delays, multi-branch splits, and other logic to manage user interactions.
  </Accordion>

  <Accordion title="Can I track user counts at each stage in Journeys?">
    Yes, Journeys display the count of qualified users/events/IDs at each node in the workflow.
  </Accordion>

  <Accordion title="Can I re-trigger a Journey for the same user?">
    Yes, you can set a reentry condition to re-trigger the workflow.
  </Accordion>

  <Accordion title="Can I edit a Journey after publishing?">
    Yes, you can edit a Journey at any time after it is published.
  </Accordion>

  <Accordion title="Why is my audience size smaller than expected?">
    The audience size depends on applied filters, available data, and ID resolution logic. Ensure that your conditions capture the expected users.
  </Accordion>

  <Accordion title="How can I troubleshoot an Audience not activating on a destination?">
    Verify that the destination supports the Audience type, check mapping configurations, and confirm that there are qualifying users.
  </Accordion>

  <Accordion title="What should I do if my Real-Time Audience does not update as expected?">
    Check if the data pipeline is processing new events, and confirm that future events match the defined conditions.
  </Accordion>
</AccordionGroup>

## Activation & Destinations

<AccordionGroup>
  <Accordion title="Which destinations support Real-Time Audiences?">
    Real-Time Audiences can be activated on destinations that support real-time data transfers. Refer to the supported destinations list in the platform.
  </Accordion>

  <Accordion title="Can I activate a Batch Audience immediately?">
    Yes, you can choose "Activate Now" to send the data immediately, or "Activate Later" to delay activation.
  </Accordion>

  <Accordion title="What happens if I save an Audience as a draft?">
    The Audience is stored with all attributes, tags, and configurations intact. You can revisit and modify it before activation.
  </Accordion>
</AccordionGroup>

## Data Processing & Troubleshooting

<AccordionGroup>
  <Accordion title="Why is my audience size smaller than expected?">
    The audience size depends on applied filters, available data, and ID resolution logic. Ensure that your conditions capture the expected users.
  </Accordion>

  <Accordion title="How can I troubleshoot an Audience not activating on a destination?">
    Verify that the destination supports the Audience type, check mapping configurations, and confirm that there are qualifying users.
  </Accordion>
</AccordionGroup>