Skip to main content

Bring deal data into your reporting

Use information from MyCRM to build reports that answer your business’s questions. A connection to your reporting tool can reduce manual exports and give your team a clearer view of the deals your application is permitted to access.

What this could look like​

You want a dashboard showing how many deals are at each stage of your pipeline. Your integration reads the relevant deal information from MyCRM, translates the status values into agreed labels and refreshes the dashboard on a schedule.

The report shows when its last update succeeded, so the team knows how current the figures are.

Start with the question, then choose the data​

  • What decision will this report support? Define the measures and filters before collecting information.
  • Which deals belong in it? Decide if the whole business, specific advisers or some other context determines what to include. Compare reports using the same population of records.
  • What does each status mean? Your organisation’s labels and MyCRM’s system statuses may describe different things. Agree the meaning of each reporting category.
  • How fresh does it need to be? A daily operational report and a frequently updated dashboard have different requirements.
  • Who owns the result? Choose someone to check missing records, unexpected totals and failed updates.

Information visible through sharing in the MyCRM application may not be available to your integration. Confirm this early so a difference in totals does not become a surprise after the report is built.

Implementation notes for your technical team

A deal connects to contacts, participants, notes, structures and securities. Some values are relationships to reference data rather than display text on the deal. Preserve identifiers and distinguish organisation-specific statuses from system statuses.

  • Prefer scheduled incremental synchronisation over repeatedly downloading all records.
  • Select the smallest set of fields and relationships needed for the report.
  • Follow rate-limit headers and spread requests over time.
  • Prefer identifier-based traversal to increasingly deep numbered pages where the resource supports it.
  • Record the last successful synchronisation and make it visible in the report.

Start with Search deals and the deals data guide. For a change-driven feed, arrange webhook access and confirm event coverage during onboarding.