> For the complete documentation index, see [llms.txt](https://docs.revelator.com/pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.revelator.com/pro/getting-started/onboarding-to-revelator/digital-sales-reporting.md). # Digital Sales Reporting Ingesting your streaming data and financial reports Revelator can automate your digital sales reporting, save you both time and energy in consolidating all of your files from the DSPs. Please see [this article ](https://app.gitbook.com/@brunoguez/s/revelator-playbook/getting-started#reporting-services)to understand how to set up your DSP integrations. #### Connecting your Data Sources \- for any services that you have direct deals with, add reporting credentials to your Revelator account from \_Services>Reporting\_ If you need to import or migrate digital sales reports from non-supported DSPs into your Revelator account, please fill out the information in this [Digital Sales Reports worksheet](https://docs.google.com/spreadsheets/d/1PYVqAZb-MtS_6JysX-ICcEgjJU8VSsZjqJQkC61YNNg/edit#gid=1235388365). You can also upload digital sales reports manually if the DSP does not provide an FTP or API to automate the retrieval of the files. If you are a Merlin member, Revelator can help you connect to Merlin and automate your Digital Sales Report ingestion. Revelator supports Daily Trends for customers that have either direct/Merlin deals or are distributing through Revelator for the following DSPs * iTunes * iTunes Match * Apple Music * Spotify (Bulk API) * Deezer * Amazon * Soundcloud Speak to our Customer Success team to connect your services for Dailies and provide a list of DSPs you have direct deals with, Merlin deals, or Revelator deals. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.revelator.com/pro/getting-started/onboarding-to-revelator/digital-sales-reporting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.