Skip to main content

Plan a Data Studio reporting connection review

Data Studio, formerly Looker Studio, is Google’s reporting tool. Ordering.co lists its integration as Coming soon. Use this guide to scope a reporting workflow outside the Dashboard. Google Data Studio overview · Ordering.co integration status

Keep Ordering.co report views separate​

Choose the native source that matches the question and the level of detail you need.

  • Business reports · Download CSV from supported cards such as Orders, Sales and order status. Each file contains that card’s returned rows.
  • Enterprise reports · Export individual report results where the selected card offers CSV.
  • Payment reports · The general report offers CSV by payment method and billing period. Payment history uses PDF.
  • Export orders · Use the Orders list export when you need order-level rows.

Separate Google's CSV upload from a direct connection​

If Google’s CSV upload is available in your Data Studio account, start with a sample file your team is authorized to share. Check the header names, field order, and UTF-8 encoding against Google’s format. Compare row counts and totals with the source after importing. Uploads append rows, so check for overlapping periods or repeated records before adding more files. Google CSV upload requirements

Treat a manual upload as a snapshot. If you need automatic refresh, confirm the data source, connector or pipeline, permissions and refresh schedule with the team that will maintain it. Available connectors · Community connectors

Prepare a project scope discussion​

If your team wants to discuss future reporting options, identify:

  • The Ordering.co project and the business or other data scope involved.
  • The report family or Enterprise report card relevant to the question.
  • The fields, date period, timezone, and intended reporting audience.
  • Whether a manual file or an automatically refreshed data source would meet the intended use.

These are scoping questions, not confirmed integration requirements or a commitment to provide a connection. Do not include passwords, API keys, access tokens, or other credentials in a shared request. Report files can include sensitive commercial, payment-related, operational, or customer information; follow your project's authorization and data-handling process.

Request a Data Studio reporting scope discussion

Back to the Data Studio integration details